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

# Create Your Own Permission Roles

> Build your own permission roles from the Roles screen, next to the standard shared roles.

Create, edit and delete permission roles of your own. Only your property sees them.

<video autoPlay muted playsInline controls className="w-full rounded-md" src="https://mintcdn.com/kwentra/B6ZLne_BvFxLcGWY/images/settings/general-settings/create-your-own-permission-roles/manage-user-roles-walkthrough.mp4?fit=max&auto=format&n=B6ZLne_BvFxLcGWY&q=85&s=2aab9c3d619b482cfa623f6d6193b8b7" data-path="images/settings/general-settings/create-your-own-permission-roles/manage-user-roles-walkthrough.mp4" />

### **Business Value**

* Build roles that match how your property works.
* Stop waiting on Kwentra to create a role for you.
* Keep your roles private. No other hotel sees them.
* Copy an existing role instead of starting from nothing.
* Give a role to one property or to every property you manage.

### **Use Cases**

* Hotel administrator creates a "Weekend Front Desk" role with fewer permissions.
* Group administrator builds one role and uses it in every property they manage.
* Administrator copies the Receptionist role, drops two permissions and saves it under a new name.

### **How It Works**

| **Where:** Settings → System Users → Roles |
| - |

Before, only the Kwentra team could build a role. You can now build your own. The standard roles do not change.

The Roles screen lists your property's own roles first, then the standard shared roles.

#### **Creating a role**

1. Create a new role and give it a name.
2. Choose the role's **scope**:
   * **This property only** — the role exists in this property.
   * **All properties I manage in this company** — the role is available in every property you manage there.
3. Pick the permissions. They are grouped by module: General, Front office, Accounting, Point of sale, Online booking and more. Each group has **Select all** and **None**. There is also a search box.
4. Save.

Role names must be unique in your property. Capital letters and extra spaces do not make a name different. "Weekend Staff" and "weekend staff " collide. A custom role also cannot take the name of a standard role.

From a role's edit screen you can assign people to the role and remove them again.

#### **Starting from a copy**

You can start from a copy of any role, standard or custom. Its permissions come ready-selected. Adjust them from there.

The copy brings only the permissions **you hold yourself**. Extras are left out, and you are told how many were skipped. The role you copied is never changed.

#### **What a custom role cannot grant**

A custom role can never give more power than you hold. These are not offered in the picker. They are blocked if they arrive another way:

* **Any permission you do not hold yourself.**
* **User, role and permission management rights.**
* **System-internal areas:** authentication, sessions, integration plumbing and feature flags.
* **Destructive delete rights**, apart from a small reviewed set.

A role can only be given to users inside the properties the role covers.

| **Note:** You cannot lock yourself out. The system does not let you remove your own access to user and role management. This holds when you edit your own roles, and when you take those rights out of a role you hold. |
| - |

#### **Standard roles**

The standard roles stay global, shared and read-only. They are tagged **Standard** in the list. You cannot edit or delete them.

#### **Who can manage roles**

Only users whose role carries the role-management rights can create, edit or delete custom roles. The **Administrator** role has them by default.


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