> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/documentation/settings/users/users-and-licences.md).

# Users and licences

## Users

In the Paradime platform, the mechanism for controlling and managing access to your account involves the use of licenses. This approach ensures a structured and secure way to allocate user permissions and roles.

To accommodate various levels of access and responsibility, Paradime offers three distinct types of licences:

* **Active seats** — These can develop code using the Paradime Code IDE, manage and run production schedules using Bolt and access other Paradime features.
* **Read-Only seats** — These have read-only access to the platform and can view Catalog, Lineage and Production schedules logs.
* **Management seats\*** — Can manage users, groups, and licenses, among other permissions at the account level or workspace level.

{% hint style="info" %}
**\*Management seats** are available only on the [Security Pack](/app-help/documentation/settings/users/role-based-access-control.md).
{% endhint %}

## Licences

In Paradime, we have a set of roles available depending on the selected tier. **We only charge for Active Seats**, in other words - for users with write access to the Paradime Development Environment and/or Production Environment.

Business users have only read-only access and you can have unlimited business users signed up to the Paradime platform. These do not count towards the active usage seats.

Management seats are available only on[ ](/app-help/documentation/settings/users/role-based-access-control.md)[Paradime Security Pack](/app-help/documentation/settings/users/role-based-access-control.md) and do not count towards the active usage seats.

Refer to [Paradime Pricing Plans ](https://www.paradime.io/pricing)for more information about licenses available within each plan.

| Role type                      | Active seats | Read-Only | Management |
| ------------------------------ | ------------ | --------- | ---------- |
| **Admin**                      | ✅            |           |            |
| **Workspace Admin\***          | ✅            |           |            |
| **Developer**                  | ✅            |           |            |
| **Analyst\***                  | ✅            |           |            |
| **Business**                   |              | ✅         |            |
| **Workspace Settings Admin\*** |              |           | ✅          |
| **Security Admin\***           |              |           | ✅          |
| **Billing Admin\***            |              |           | ✅          |

{% hint style="info" %}
**Role Types with marked with (\*)** are available only on the[ ](/app-help/documentation/settings/users/role-based-access-control.md)[Paradime Security Pack](/app-help/documentation/settings/users/role-based-access-control.md).
{% endhint %}

### Related Articles

For details on the default roles and permissions associated with the standard Paradime Tiers, click the following link:

{% content-ref url="/pages/9j60mdMNjus5Pw0Rmvve" %}
[Default Roles and Permissions](/app-help/documentation/settings/users/roles-and-permissions.md)
{% endcontent-ref %}

For details on Paradime role-based access control feature included with theParadime Security Pack, click the following link:

{% content-ref url="/pages/7U88VCYAyTKmdJXQcU5I" %}
[Role-based access control](/app-help/documentation/settings/users/role-based-access-control.md)
{% endcontent-ref %}


---

# 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://docs.paradime.io/app-help/documentation/settings/users/users-and-licences.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.