> 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/appendix/brokerage-set-up/admin-roles-and-permissions.md). # Admin Roles and Permissions This guide explains how roles work, how to create and edit them, and how administrative access relates to your brokerage's organizational structure. Rechat allows brokerages to customize roles and permissions to control which features and tools their members can access. Administrators can create custom roles, name them according to their brokerage's needs, and select the permissions associated with each role. This flexibility makes it possible to provide agents, assistants, marketing staff, and administrators with access appropriate to their responsibilities. ### Understanding Roles and Permissions A **Role** is a named collection of permissions that determines which features a member can access in Rechat.

For example, your brokerage might have roles for: * **Agent:** Members who need access to their everyday real estate tools. * **Assistant:** Support staff who assist agents with transactions, marketing, or other responsibilities. * **Marketing Admin:** Brokerage staff who manage marketing resources. * **Admin:** Members responsible for administrative and account management functions. These are examples of role names. Your brokerage can customize its roles and the permissions associated with them. **Important:** A role's name does not determine its capabilities. The permissions selected for that role determine which features its members can access. #### Roles vs. Account Access Rechat uses both account membership and roles to manage access. * **Account Membership:** Determines which account a person belongs to, such as the Root Brand, an Office, a Team, or a Personal account. * **Role Permissions:** Determine which Rechat features are available to that member within their assigned account. For example, an administrator assigned to an Office may have administrative permissions within that Office, while a member assigned to a Personal account may have access to the features enabled for that account. ### Creating a Custom Role Administrators can create roles tailored to their brokerage's needs.

#### How to Create a New Role 1. Open **Accounts** in Rechat. 2. Select the account where you want to manage roles. 3. Open the **Members** tab. 4. Click **Edit Roles** to open the role management window. 5. Click **Add New Role**. 6. Enter a descriptive name for the role. 7. Select the checkboxes for the features and permissions you want the role to include. 8. Click **Save**. Your new role will be available for assignment to members. **Best Practice:** Give roles clear, descriptive names that reflect their purpose, such as Transaction Coordinator, Marketing Assistant, or Office Administrator. ### Understanding Available Permissions The **Edit Roles** window displays a permission matrix. Each row represents a role, while each column represents a Rechat feature or permission. * **Checked:** The permission is enabled for that role. * **Unchecked:** The permission is not enabled for that role. Administrators can customize the permissions associated with each role by selecting or deselecting the corresponding checkboxes. #### Permission Categories Depending on your brokerage's configuration, available permissions may include:


Permission	General Purpose
Deals	Access to transaction-related functionality
Back Office	Access to Back Office functionality
Admin	Administrative and account management capabilities
Marketing Admin	Marketing administration capabilities
Marketing	Access to marketing tools
Adoption	Access to adoption-related functionality (Admin Only)
CRM	Access to People and CRM functionality
Agent Network	Access to Agent Network features
Websites	Access to supported website features
Beta Features	Access to designated beta functionality
Saved Searches	Access to Saved Search functionality

{% hint style="info" %} Available permissions may change as Rechat introduces new features or updates existing ones. {% endhint %} #### How to Enable or Disable a Permission 1. Open the **Edit Roles** window. 2. Locate the role you want to modify. 3. Find the corresponding permission column. 4. Check the box to enable access or uncheck it to remove access. 5. Click **Save**. {% hint style="warning" %} **Important:** Before changing an existing role, consider which members are assigned to it. Role permissions should be managed carefully because they control access to Rechat functionality. {% endhint %} ### Editing or Deleting Existing Roles #### How to Edit a Role You can modify an existing role's name and permissions. 1. Open **Accounts** and navigate to the relevant account. 2. Open **Members** and select **Edit Roles**. 3. Locate the role you want to modify. 4. Update the role name or adjust its permission checkboxes. 5. Click **Save**. #### How to Delete a Role The role management window includes a delete icon beside each role. 1. Open **Edit Roles**. 2. Locate the role you want to delete. 3. Click the **trash icon** beside the role. 4. Review any confirmation presented. 5. Save your changes as required. **Important:** Before deleting a role, review whether members currently use it and whether they need another role assigned. Do not delete a role without understanding how the change could affect access. ### Assigning Roles to Members Once roles are configured, they can be assigned to members of your brokerage. #### How to Assign or Change a Member's Roles

1. Open **Accounts**. 2. Select the Office, Team, Personal account, or other account containing the member. 3. Open the **Members** tab. 4. Locate the member. 5. Click the role selector beside their name. 6. Select or deselect the appropriate roles. Members can have more than one role assigned to them. For example, a member might have both an **Agent** role and a **Marketing Admin** role, depending on their responsibilities. {% hint style="info" icon="head-side-brain" %} **Best Practice:** Review all roles assigned to a member when evaluating their access. A member with multiple roles may receive permissions from more than one role. {% endhint %} ### Understanding Administrative Access Levels In addition to configuring permissions, brokerages should consider where administrators are assigned within their organizational hierarchy.


Administrative Level	Scope
Root Brand Admin	Brokerage-wide administrative scope
Regional Admin	Assigned region and its organizational structure
Office Admin	Assigned office or offices
Team Admin	Assigned team or teams

#### Root Brand Admin Root Brand Admins operate at the highest level of the brokerage hierarchy. Depending on their configured permissions, they may manage brokerage-wide accounts, members, marketing resources, and administrative settings. #### Regional Admin Regional Admins are associated with a designated region and its organizational structure. Their responsibilities may include managing regional accounts, members, and resources, subject to their assigned permissions. #### Office Admin Office Admins manage designated offices and their associated members. Their responsibilities may include office-level roster management, administrative settings, and marketing resources. #### Team Admin Team Admins manage designated teams. Their responsibilities may include team membership, assigned roles, and team-specific resources. **Important:** These descriptions refer to administrative scope within the brokerage hierarchy. Actual capabilities depend on the permissions configured for the assigned role. ### Admin vs. Marketing Admin Some brokerages may choose to assign **Marketing Admin** access instead of the full **Admin** role. While both are Admin-level roles, their capabilities differ: | Capability | Admin | Marketing Admin | | ----------------------------------- | :---: | :-------------: | | Access to Account Settings | ✅ | ❌ | | Create/Edit Users | ✅ | ❌ | | Assign Roles & Permissions | ✅ | ❌ | | Access to Studio (Marketing Center) | ✅ | ✅ | | Impersonation (Full-Service Mode) | ✅ | ✅ | | Access to Members (Beta) | ✅ | ✅ | | Access to People Center | ❌ | ❌ | {% hint style="info" %} Marketing Admins are ideal for brokerage staff who manage agent marketing but don't need full platform administration or access to agent contacts. {% endhint %} ### Best Practices for Managing Roles * **Use descriptive role names:** Make it easy to understand each role's intended purpose. * **Grant only necessary permissions:** Avoid providing administrative or CRM access to members who do not need it. * **Review roles before making changes:** Consider which members may be affected by changes to an existing role. * **Check multiple role assignments:** A member may have access through more than one assigned role. * **Review permissions periodically:** As team responsibilities change, confirm that roles still reflect each member's needs. * **Consider account placement:** Administrative permissions should be assigned at the appropriate level of your brokerage hierarchy. ### Common Questions **Can my brokerage create custom roles?** Yes. Administrators can create roles with custom names and select the permissions associated with each role. **Can I change the permissions of an existing role?** Yes. Open **Edit Roles**, locate the role, adjust its permission checkboxes, and save your changes. **Can a member have more than one role?** Yes. Members can have multiple roles assigned to them. **Does naming a role "Admin" automatically give it full administrative access?** No. A role's capabilities depend on its selected permissions, not simply its name. **How can I see what a role allows someone to access?** Open **Edit Roles** and review the checked permission boxes for that role. ### Related Articles * [**Managing Your Rechat Roster**](/appendix/brokerage-set-up/managing-your-rechat-roster.md) — Create accounts, add members, assign roles, and manage member access. * [**Managing Your Brokerage Settings**](/appendix/brokerage-set-up/account-settings.md) — Configure account information and branding across your organization. --- # 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/appendix/brokerage-set-up/admin-roles-and-permissions.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.