> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/features/users-management/common-permissions/settings-permissions-how-to-assign-and-use.md).

# Settings Permissions: How to Assign and Use

Settings permissions allow team members to view or manage the configuration options under **Billing** and **Users** within Mercuri CX. By assigning these permissions, you can control who can access sensitive account settings, manage billing details, or modify user-related information.

***

### Steps to Assign Settings Permission:

1. **Navigate to Settings** from the left sidebar.
2. Click on **Teams**.
3. Select **Add User** or choose an existing user to configure permissions.
4. Click on **Configure Permissions**.
5. In the permissions window, go to the **Common Permissions** tab.
6. Locate the **Settings** section.
7. Enable or disable specific permissions under **Billing** and **Users** based on the level of access you want to provide.

***

### Permission Types

<figure><img src="/files/7UpuHjdk7q6w9XY5v0bW" alt="" width="563"><figcaption></figcaption></figure>

Settings permissions are divided into two main categories: **Billing** and **Users**, each with “View” and “Manage” access types.

#### 1. **Billing Permissions**

**a. View Billing Logs**

Allows team members to view and track billing-related logs, such as transaction history or plan usage.

* **Example:** The finance team needs visibility into billing details for monthly reconciliation, but should not modify payment methods. Assigning *View Billing Logs* ensures transparency without modification rights.

**b. Manage Billing**

Grants team members full control over billing operations, including updating payment methods, changing plans, or managing invoices.

* **Example:** The account administrator is responsible for updating subscription plans and payment details. Granting *Manage Billing* lets them perform these actions securely.

***

#### 2. **User Permissions**

**a. View Users**

Allows team members to see the list of users, their assigned roles, and permissions without the ability to modify them.

* **Example:** A team supervisor wants to review user access levels across the platform, but should not edit them. Assigning *View Users* ensures read-only access.

**b. Manage Users**

Grants team members the ability to add, remove, or edit user details and configure their permissions.

* **Example:** An admin needs to onboard new team members and update existing user roles. Granting *Manage Users* gives them full control over user management.