> For the complete documentation index, see [llms.txt](https://docs.quickreply.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quickreply.ai/product-modules/settings/security/role-based-access.md). # Role Based Access Role Based Access lets Owners and Admins control which features and views Members can access in the QuickReply.ai dashboard. Access can be configured at the module level and, where available, for individual features within a module. This is different from assigning a role to a teammate. A teammate's role determines whether they are an Owner, Admin, or Member. Role Based Access determines what an Admin or Member can access within QuickReply.ai. ### Why Use Role-Based Access? Businesses often manage teams with different responsibilities, such as support agents, team leads, campaign managers, and analysts. Without granular access control, members may see sensitive conversations, analytics, reports, or integrations they should not handle. Role-Based Access helps you: * Protect sensitive information by limiting visibility. * Speed up onboarding with pre-configured permissions. * Improve accountability by restricting access to specific features. * Reduce accidental changes by limiting high-risk actions * Reduce dependency on support/tech teams for permission adjustments. {% tabs %} {% tab title="Video Tutorial" %} {% embed url="" %} {% endtab %} {% tab title="Step By Step Instructions" %} ### How Role Based Access works The Role Based Access page lists the modules and features available in the dashboard, with separate access controls for Admin and Member. ![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2F7gmBh5Bfz7zI6qzk1QAu%2Funknown.png?alt=media\&token=2cdf8f6b-1de9-46ae-9794-7ea6f5c9a75c) Enable a permission to give the role access to that feature, or disable it to remove access. Some modules can be expanded to configure more specific permissions. For example, Conversations includes individual permissions such as: * All Chats * My Chats * Unassigned Chats * Starred * Channels * Prospects, etc.. This allows access to be configured for specific parts of a module instead of giving the user access to everything within it. ### Parent and child permissions Permissions follow a parent–child structure: * Parent permission — represents the main module. * Child permission — represents a specific view or feature within that module. For example, Conversations is the parent, while All Chats, My Chats, and Unassigned Chats are child permissions.\
![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2FIGGryYBrZc07HPRp081N%2Funknown.png?alt=media\&token=daf75d71-f123-4026-8886-70a2aa29ece2)
Enabling a child permission also enables its parent module. This allows access to be configured at a more granular level instead of granting access to the entire module. ### Admin and Member access Role Based Access uses separate permissions for Admin and Member roles. Admin Admins can configure the permissions available to Admin and Member roles. However, some settings remain Owner-only and cannot be granted through Role Based Access. For example, Support Team Access under Settings → Security is available only to the Owner. ![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2FvXfY211wgYaAeK2BkPdu%2Funknown.png?alt=media\&token=a6da618e-0bed-446d-860b-01ccf65ad5f7) \ (Owner)
![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2F2TaevXzN3RrEfKicVjxx%2Funknown.png?alt=media\&token=1c234419-917f-4aab-802f-d8ad2d052048) (Admin) Member Members cannot access Role Based Access settings or modify their own permissions. A Member's available modules, views, and features depend on the permissions configured for the Member role. For example, removing All Chats from the Member permissions removes the All Chats view from the Member's Conversations section.\
![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2FJgQCQnKj0m8dtqb0HCrn%2Funknown.png?alt=media\&token=fd5074ba-799c-43b4-bff2-673aa3fb999b) ### Updating permissions 1. Go to Settings → Security → Role Based Access. 2. Select or clear the required permissions for Admin or Member. 3. Click Save Changes.\ ![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2F1ehzz5Iea0emo5bhchyW%2Funknown.png?alt=media\&token=6052ff28-e04f-4521-8c57-85b67eb303df) 4. Refresh the affected user's dashboard. The updated permissions are reflected in the user's available menus and views after the refresh. Note: Permission changes do not require the user to be reassigned a role. The existing Admin or Member role remains unchanged.
{% endtab %} {% endtabs %} **Available permissions** Role Based Access can be configured across modules such as: * Conversations * Live View * Prospects * Team * Analytics * Campaigns * Broadcast * Journeys * AI Builder * Data Sources * Integrations The specific child permissions available depend on the module.\ \ FAQs Q: Can Owner access be restricted?\ A: No. Owners always have full access to the account and cannot be restricted through Role Based Access. Q: Can an Admin manage Member permissions?\ A: Yes. Admins can configure the permissions available to Members. Owner-only settings cannot be granted to an Admin. Q: Can I give a Member access to only part of a module?\ A: Yes. Where granular permissions are available, expand the module and enable only the required views or features. Q: I changed a permission, but the user can still see the feature. Why?\ A: The affected user needs to refresh their QuickReply.ai dashboard after the changes are saved. Q: Why isn't Owner available as a configurable role?\ A: Owner access is fixed and provides full access to the account, so only Admin and Member permissions can be configured through Role Based Access.