> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/account-and-billing/roles-and-permissions.md).
# Roles & Permissions
In LeadBoxer, we have implemented a robust roles and permissions system to help you manage user access and control within your organisation. This guide will provide an overview of the four fixed roles available - Owner, Admin, Super User, and User - as well as instructions on creating custom roles and customising permissions.
## Fixed Roles:
### Owner:
* The Owner role is the highest level of access and has full control over the entire organisation's settings, data, and user management.
* Only one user can be assigned the Owner role, and this user is typically the individual who initially created the organisation's account.
* The Owner can add, modify, or remove users, assign roles, customise permissions, and manage billing information.
### Admin:
* The Admin role is designed for users who require significant control and management capabilities within the organisation.
* Admins can add, modify, or remove users, assign roles, customise permissions, and access most settings.
* However, they do not have the same level of access as the Owner and cannot modify billing information.
### Super User:
* The Super User role is suitable for users who need access to advanced features and data but do not require administrative privileges.
* Super Users can perform most actions within the application, such as creating and managing users and add or manage datasets.
* However, they cannot add or remove users, assign roles, or modify permissions.
### User:
* The User role is the most basic level of access and is intended for individuals who primarily consume content and use the application's features without requiring administrative or advanced capabilities.
* Users can view, interact with, and contribute to the application's content based on their assigned permissions.
* They cannot modify global settings, manage users, datasets, automations, etc. For a complete overview see the permissions table below.
## Custom Roles and Permissions:
* In addition to the fixed roles, LeadBoxer allows you to create custom roles and tailor permissions according to your organisation's specific needs.
* To create a custom role, navigate to the "Roles & Permissions" section in the application's settings.
* Click on "Add New Role" and provide a name and description for the role.
* After creating the custom role, you can customise the permissions by enabling or disabling specific actions or access rights.
* You can assign the custom role to individual users from the Users overview page as needed.
## How to set a Role for a User:
* To manage roles and permissions for users, navigate to the "User settings" page
* Find the user you wish to modify, and click the options icon to assign or change their role.
* If you have created custom roles, those will also be available for selection.
* Make sure to review and update permissions regularly to ensure users have the appropriate level of access based on their responsibilities.
{% hint style="info" %}
Effectively managing roles and permissions in LeadBoxer allows you to maintain control, security, and productivity within your organisation. By utilising fixed roles and customising permissions, you can tailor user access to match specific job requirements. If you have any further questions or require assistance, please don't hesitate to contact our support team.
{% endhint %}
---
# 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://help.leadboxer.com/leadboxer/account-and-billing/roles-and-permissions.md?ask=&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.
.png?alt=media)