> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwoty.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Permissions reference

> Every permission a Qwoty role can grant: objects, project access level, settings, and apps.

A role is a set of permissions in three areas: **Objects**, **Settings**, and **Apps**. This page lists every permission you can set when you create or edit a role in **Settings › Role › Role**. To create a role, see [Manage roles](https://docs.qwoty.io/user-guide/settings/users/manage-roles.md).

## Objects

"Actions you can perform on objects family." For each object family, you check **Read**, **Write**, and **Delete**.

| Objects family | Object concerned | Read | Write | Delete |
| - | - | :-: | :-: | :-: |
| **Project** | Quote, contract and order | ✓ | ✓ | ✓ |
| **Products & Pricing** | Catalogs, products, price grid | ✓ | ✓ | ✓ |
| **Customers** | Customers | ✓ | ✓ | ✓ |
| **Workflow** | Approval, workflow, and configurator | ✓ | ✓ | ✓ |
| **Content** | Contract models, media, content | ✓ | ✓ | ✓ |
| **Templates** | Project templates | ✓ | ✓ | ✓ |

### Project Access Level

The **Project Access Level** limits which projects a user can access, on top of the Project permissions:

| Level | The user can access |
| - | - |
| **Own** | Only their own projects |
| **Team** | The projects of their teams |
| **Workspace** | All projects of the workspace |

## Settings

"Manage general application-level actions." Each settings zone has one **Authorize** checkbox. It controls access to the matching section of the settings menu.

| Setting | Description | Settings menu section |
| - | - | - |
| **Workspace** | Set global workspace preferences | Workspace |
| **User & Teams** | Add or remove users and define teams | Users & Team |
| **Roles** | Define user roles and access levels | Role |
| **Data** | Edit CPQ data structure and fields | Data |
| **Developers** | Manage integrations, API keys, and webhooks | Developer |
| **Organization** | Manage multi-tenant org and billing | Organisation |

## Apps

Each app-level action has one **Authorize** checkbox.

| Action | Description |
| - | - |
| **Import CSV** | Allow importing data from CSV files |
| **Export CSV** | Allow exporting data to CSV files |
| **Overpass sales Restriction** | Allow to overpass restrictions such as approval or discount. For example, it shows **Approve without validation** on a quote that needs approval. |

## Licence of a role

Qwoty calculates the licence of a role from its permissions:

* `core` if the role can write projects,
* `support` if the role can only read projects but can write other objects.

When you invite a user, the **Role** list only shows the roles that match the selected **Licence**. Each licence uses a seat of the matching type. See [Subscription and seats](https://docs.qwoty.io/user-guide/settings/organisation/subscription-and-seats.md).

## System roles

The system roles `admin`, `manager`, `view_only`, and `sale` show a **System** badge and are read-only: "This role is a default system role and cannot be modified." Open one with **View** to see its permissions.

> [!NOTE]
>
> You can't create a custom role with the same permissions as `view_only`. Change at least one permission.

## Related resources

> **[Manage roles](https://docs.qwoty.io/user-guide/settings/users/manage-roles.md)**
>
> Create, edit, and delete roles.

> **[Manage users](https://docs.qwoty.io/user-guide/settings/users/manage-users.md)**
>
> Assign a licence, a role, and teams to users.

> **[Manage teams](https://docs.qwoty.io/user-guide/settings/users/manage-teams.md)**
>
> Teams used by the Team access level.

> **[API permissions](https://docs.qwoty.io/developers/core-concepts/permissions.md)**
>
> How the role of an API token applies to API calls.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.