# Roles & permissions The **Roles & permissions** page allows workspace owners and administrators to manage member access and define permission levels across all CX Genie modules.\ This section helps ensure that every team member has the appropriate access rights according to their role and responsibilities.

## How to Access To manage members and permissions: 1. Go to **Settings** in the left navigation menu. 2. Select **Members & Permissions**. The page displays all users currently added to the workspace, along with their assigned roles, teams, and bots. *** ## Member List Overview Each row in the member list represents a workspace member and includes the following information: * **Name** – Displays the member’s name. * **Role** – Shows the permission level assigned to the member. * **Number of Teams** – Indicates how many teams the member belongs to. * **Teams** – Lists the specific teams the member is part of. * **Bot** – Displays the bot(s) that the member is assigned to. * **Added Date** – Shows the date the member was added to the workspace. * **Action** – Remove a member from the workspace by clicking the delete icon. Additional controls: * **Search box** – Search for a member by name or email. * **Add Member** – Invite a new member to the workspace using their email address. ## Default Roles and Permissions There are five default permission levels in CX Genie. Each role defines how much access a user has within the workspace. ### 1. Owner * Holds the **highest level of access** in the workspace. * Can edit roles, remove members, manage permissions, and transfer ownership. * Has full access to all CX Genie modules and settings.

### 2. Admin * Has **broad administrative privileges**, second only to the Owner. * Can edit permissions, remove members, and grant access to other modules. * Restricted from accessing the **Marketplace** and **Subscription** modules by default.

### 3. Senior member * Has **partial access** to system modules. * Cannot access the **Bot**, **Form Builder**, **Marketplace**, and **Subscription** modules. * Typically used for experienced team members who manage tickets or workflows but not configuration.

### 4. Member * Has **limited access** to core operational modules. * Can access **Help Desk** and **Settings (view only)**. * Suitable for general support agents.

### 5. Bot member * The **most restricted role**, designed for users who handle specific bots. * Can access **Help Desk**, **Ticket**, and **Settings (view only)**. * When converting an existing user to a **Bot Member**, a panel appears to select which bot the member belongs to.

When you switch a member from Admin/Senior member/Member to Bot member level, a new panel will pop up to determine which Bot member will belong to.

## Customizing Permissions While CX Genie provides default permission levels, each role can be **customized** to fit your organization’s needs.\ Administrators can modify which modules or features are accessible for each role type. **Example:**\ An agency may grant additional analytics access to the “Senior Member” role or restrict “Admin” permissions to certain business units. ## Notes Before Using * The default roles (Admin, Senior Member, Member, Bot Member) come with pre-defined access scopes. * These permissions can be adjusted at any time for more granular control. * CX Genie recommends customizing roles to reflect your organization’s structure and security requirements, especially for agencies or multi-client setups. ### Video instruction: {% embed url="" %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documents.cxgenie.ai/settings/roles-and-permissions.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.