> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/governance/users-roles-and-permissions.md).

# Users, Roles & Permissions

Tailor platform access and governance to your organization's specific needs with **Advanced User Management.**

This comprehensive guide covers the configuration of core access and identity features, ensuring security and customization across your deployment:

* **Custom Roles (RBAC)**: Define and implement **Custom Role-Based Access Control** to establish precise, granular permissions for every user role within your organization.
* **Collaborator Management**: Take full control of who sees what. Our updated management tools allow you to see exactly who has access to your applications and revoke or upgrade permissions in a single click.
* **Identity Integration (SSO)**: Integrate seamlessly with your existing identity providers (IDPs) for secure **Single Sign-On (SSO),** simplifying user access while maintaining corporate security policies.
* **Platform Branding**: Manage the platform's visual identity, including **white-labeling** and applying custom brand assets.

By mastering this section, you ensure every user, from business analyst to developer, has the precise level of access required to perform their tasks while the platform's look and feel aligns perfectly with your corporate guidelines.

### Custom role-based access control

Enterprise Administrators can create custom roles for strict security and governance requirements.

#### Granular permission control

Standard SaaS deployments use predefined roles, including Admin, Developer, and Business User. Enterprise deployments support custom roles with granular control over actions and resources.

#### Create a custom role

1. Go to **Enterprise Features** in the main navigation.
2. Select **RBAC/Role Management**.
3. Select **Create Role**. Give the role a clear, unique name.

   For example: `Compliance Reviewer` or `Workflow Architect`.

<div data-with-frame="true"><figure><img src="/files/HkujvFUnQUBvDX1BBtoI" alt=""><figcaption><p><br><mark style="color:green;"><strong>Create Role</strong></mark></p></figcaption></figure></div>

4. Select the permissions that the role needs. Permissions can control specific actions and resources.

   Examples include deleting agents, accessing production deployment settings, and viewing monitoring dashboards.

<div data-with-frame="true"><figure><img src="/files/1WPaZpYaBPWNjoI4BSC5" alt=""><figcaption><p><br><mark style="color:green;"><strong>Permission Selection Checklist</strong></mark></p></figcaption></figure></div>

5. Select **Create Role**. You can view, manage, or delete the role from the Role Management list.

<div data-with-frame="true"><figure><img src="/files/DZwn73c9mDRqzcD1J9KV" alt="" width="360"><figcaption><p><br><mark style="color:green;"><strong>Create Role - Assign Permission</strong></mark></p></figcaption></figure></div>

6. Go to **User Management** or **Invite Users**. Assign the custom role to individual users.

<div data-with-frame="true"><figure><img src="/files/fry1aiq3lLdK39r16c44" alt="" width="306"><figcaption><p><br><mark style="color:green;"><strong>Create User - Assign Role</strong></mark></p></figcaption></figure></div>

## Related

* [Control Center](/start-here/control-center.md) — manage account-wide governance and administration.
* [Account Settings](/governance/account-settings.md) — manage users, teams, roles, and API keys.
* [Branding](/governance/custom-brand-configuration.md) — configure your platform's visual identity.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/governance/users-roles-and-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.