> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/vendor-platform/settings/roles-permissions-user-labels.md).

# Roles/Permissions/User Labels

You can set custom permissions for platform users.

{% hint style="info" %}
Admin users have all permissions by default.
{% endhint %}

The options available are:

* `Product` Read/Manage/None
* `Orders` Read/Manage/None
* `Licenses` Read/Manage/None
* `Customers` Read/Manage/None
* `Analytics` Read/None
* `Settings` Read/Manage/None
* `Billing` Read/Manage/None
* `Platform users` Read/Manage/None

{% hint style="info" %}

* **Read access** to Settings allows a user to **view API keys**.
* **Write access** to Settings allows a user to **create webhooks**.
  {% endhint %}

## Creating a Permissions Template

Creating a permissions template allows you to easily set permissions for a new or existing user or group of users.

{% stepper %}
{% step %}

### Start

Navigate to "Settings" > "Permissions".
{% endstep %}

{% step %}

### Add new template

Click "Add new permissions template".

![Add New Permissions Template Button](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/EVtle9YIeCfxzaHvsUPY/yGCHUh5JLLgDzLyyZu_4C_image.png)
{% endstep %}

{% step %}

### Configure template

Give your new permissions template a name and set the access level you wish to grant to any user that you apply this template to, then click confirm when you're done.

![Setting New Permissions](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/TYPlXHCWYQ6XxNCTVLDD/HWmkyjT2C4LQzDpVGBNhw_image.png)
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Modifying a permissions template will not affect permissions of any given user.
{% endhint %}

## Setting Permissions for a New User

When adding a new user to the vendor platform, you can either assign them "Admin" privileges, or you can set permissions from any template already created in the account.

{% stepper %}
{% step %}

### Open user creation

Navigate to "Settings" > "Users" > "Add new User".

![Add New Platform Users](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/UO1a5ZQu7aO2tOT5npdx/6bPOGZu8etTtWHBb02TyF_image.png)
{% endstep %}

{% step %}

### Set permissions

In the add-user popup you will have the options to set permissions or assign a permissions template.

![Setting User Permissions](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/hb9bueM9tCZwmodXzHcv/_s551rVuzbkrWShXJt8YF_image.png)
{% endstep %}
{% endstepper %}

## Applying Permissions to an Existing Platform User

### For an Individual Platform User

Navigate to the platform user detail view. From this screen, you can:

* Toggle whether this user is an administrator for the account
* Edit individual permission settings (if they are not admin)
* Apply permissions from an existing template (if they are not admin)

![Editing Permissions for Existing User](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/U0n7cURggEFBBJePC8Yq/Jp1_ym9gn21ic1BYZ5Xxz_image.png)

### Apply Permissions Template to a Group of Platform Users

You can apply a permissions template to all platform users that have a certain label.

![Assign Permissions Temlate to User Label](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/85YanMPqvsPE6PzFl0nI/4l8CpbGFl%20luxHttJbTm1_image.png)


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.licensespring.com/vendor-platform/settings/roles-permissions-user-labels.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.