> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/device-inventory/security-and-access/inventory-rbac.md).

# Role-based Access Control

## RBAC in OneSite Device Inventory

OneSite Device Inventory has built-in roles you can use to provide permissions to your inventory solution. For more information on the RBAC capabilities of the OneSite Platform see [RBAC](https://github.com/AdaptivaDocs/docs/blob/main/platform/user-guide/rbac.md)

RBAC allows you to:

* Assign permissions to specific job functions like operations
* Maintain data protection and regulatory compliance
* Protect sensitive data with the principle of least privilege
* Create branch office administrators for specific business units

## Explore the security roles

1. Log in to the Adaptiva Admin Portal.
2. Click the **gear icon > Settings > Security > Roles**.
3. On the Roles page, select the **Device Inventory** folder.

### Built-in roles for Device Inventory

There are 4 built-in roles for OneSite Device Inventory. These roles cover the most common use cases, though custom roles can be added as needed. These roles will be automatically created when you add a OneSite Device Inventory license.

You will need to configure these roles with membership before using them.

* **Device Inventory Super Admin**: This role gives users full permission to OneSite Device Inventory. This role is typically your IT solutions administrator.
* **Device Inventory Administrator**: This role is focused on the operation of the device inventory solution. For example, the administrator can create strategies to collect device inventory data and use dashboards to view that data. Administrators have the following permissions:
  * View schedules
  * View, create, and edit inventory categories
  * View, create, and edit inventory strategies
* **Device Inventory Super Viewer**: This role is focused on organization level auditing of device inventory data. For example, the super viewer can view all device inventory data in the organization, but cannot create a strategy to collect inventory data. Super Viewers have the following permissions:
  * View sensor data
  * View inventory categories
  * View inventory strategies
* **Device Inventory Viewer**: This role is focused on device inventory data. For example, the viewer can view all device inventory data in the North America group.
  * View inventory categories
  * View inventory strategies

## View a role and assign members to it

You can view the permissions and membership of a role in the role details.

1. Select a Device Inventory role to open the properties page. You can view the role assignments and permissions detail for the role.
2. Under Direct Administrators, click **Browse** and select a user to associate with this role and click **OK**.
3. Click **Save**.


---

# 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.adaptiva.com/device-inventory/security-and-access/inventory-rbac.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.