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

# Role Manager

***

## Introduction

The role manager extends Patchworks' existing user permission system by allowing enterprise customers to define their own roles from scratch. Rather than being limited to predefined roles, administrators can combine view and edit permissions across different areas of the platform to create roles tailored to their team structure.

Custom roles can be assigned to individual users, removed from users, and for multi-company profiles - made available to sub-customers.

{% hint style="info" %}
The role manager is an **enterprise-tier feature**. It is accessible to users with administrator-level permissions on qualifying subscription plans.
{% endhint %}

### Accessing the role manager

The role manager is found in the Patchworks settings area.

Settings › Role manager

<figure><img src="/files/zi5nIyGBxcgjLqCanRUc" alt=""><figcaption></figcaption></figure>

### Creating a custom role

1. Navigate to **Settings › Role manager** and click **Create role**.

<figure><img src="/files/qEWWjGP46mQBha8Adrzn" alt=""><figcaption></figcaption></figure>

2. Enter a **role name** and an optional **description** to help administrators identify the role's purpose.

<figure><img src="/files/5MmPFbqDHJ0hugCHIHeM" alt=""><figcaption></figcaption></figure>

3. Use the permission toggles to assign a combination of **view** and **edit** permissions across platform areas - for example, audit log access, flow management, and shape manipulation.

<figure><img src="/files/RTzPQjBbNOdPbcl1isrl" alt=""><figcaption></figcaption></figure>

4. Save the role. It will now appear in the role list and be available for assignment.

<figure><img src="/files/gL9FSRbueP4piREYqlgz" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Permissions are **derived** - some edit permissions implicitly require the corresponding view permission to be active. Review combined permissions carefully before assigning a role to users.
{% endhint %}

### Assigning a role to a user

1. Within the role manager, switch to users tab
2. Use the **Assign Role** control to selected users
3. The role is applied immediately - no save step is required.

<figure><img src="/files/tKDjc9ZoIz8KyvbBeBSm" alt=""><figcaption></figcaption></figure>

### Removing a role from a user

From the same role detail view, locate the user in the assigned users list and simply click **X** to remove.&#x20;

### Sub-customer availability

For companies managing multi-company profiles, custom roles can optionally be made available to sub-customers. This allows a consistent permission structure to be propagated across your managed accounts.


---

# 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://doc.wearepatchworks.com/product-documentation/users-roles-and-permissions/role-manager.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.
