> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/getting-started/account-settings/client-features.md).

# Client Features

#### Descr**iption**

Client Features enable advanced capabilities for your users, such as open signups, Dolby Atmos support, and marketplace access.

**Steps**

1. Navigate to **Account > Client Features**.
2. Enable or disable features based on your requirements:
   * **Open Signups:** Allow new users to create accounts directly, but ensure your team has enough resources to manage content quality.
   * **Marketplace:** Enable access to curated deals and resources.
   * **Dolby Atmos:** Activate upload and distribution of Dolby Atmos audio. Configure pricing and track limits as needed.
3. For Dolby Atmos configuration:
   * Click **Enable** and specify track limits and client access.
   * Choose from shared limits, per-client limits, or no limit.
   * Click **Save** when done.
4. Monitor feature status to ensure correct settings are applied.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revelator.com/pro/getting-started/account-settings/client-features.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.