> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/enhanced-account-settings.md).
# Enhanced Account Settings
We've made it easier for brokerages to manage their universal settings in one centralized place. Now, admins can configure global settings and customize options for regions, offices, teams & agents.
## **What’s Changing?**
* A new **Brokerage Setup** section in **Account Settings**
* Improved control over **branding, logos, colors, and fonts**
* Ability to define **bathroom count options** for property templates
* A more intuitive, structured layout for easier navigation
## **Key Features**
* **Brokerage Info** – Set your official brokerage details
* **Logos** – Upload and manage wide and square logos for branding
* **Colors & Fonts** – Customize themes, colors, and fonts to match your brand
* **Bathroom Count** – Standardize property templates with detailed bathroom options
## What's Next?
Admins can access the new [**Account Settings**](https://app.rechat.com/dashboard/accounts/settings) section by navigating to **Account Settings** > **Settings**. Check out our [**FULL GUIDE**](/appendix/brokerage-set-up/account-settings.md) for detailed instructions!
---
# 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://help.rechat.com/whats-new/enhanced-account-settings.md?ask=&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.
