> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/~/revisions/VogQMoqSfAjFiPWKwr6n/blynk.console/settings/access.md).

# Roles and Permissions

Access and permissions management for different user roles

Free and Plus plans have a locked set of permissions for each role, meaning the default permissions by role cannot be changed. PRO and Business plans have permissions that may be edited by role.

## Editing Roles and Permissions

![](https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MBFTVMf7L6S67HOuqVC%2F-MTKX6U4jHerpHXDty8J%2F-MTK_bGzpCLPihptmml-%2FRoles_and_Perms.gif?alt=media\&token=618be4e5-57c5-4c10-9992-77aaaa1366d0)

Blynk has 3 default roles that can have different sets of permissions:

* **Admin** – is intended to have the highest level of permissions
* **Staff** – we recommend to set up and use this role for internal company functions and client support
* **Users** – is intended to have the most limited set of permissions, mostly focused on managing their own devices

### Actions

* **Collapse/Expand all** in Actions block – applies eponymous actions to expandable permissions list
* **+ / -** buttons – click to expand/collapse specific permission sections
* **Enable/Disable** switches – use the switches to grant/prohibit certain access level and permissions to specific users types. Note that some permissions are dependent on other permissions

### The Full List of Permissions

#### Permissions Control

* View roles and permissions
* Create new roles
* Edit roles
* Delete roles

#### Users

* View users
* Invite new users
* Edit users
* Delete users
* Change user passwords
* Force Logout
* View user actions log
* Transfer users
* Download users list
* Suspend users

#### Devices

> Own Devices

* View devices (currently it's under "Provision new devices")
* Delete device data
* Download reports
* View timeline

> Organization Devices

* View devices (currently it's under "Add new devices from web")
* Add new devices from using web app
* Delete data from devices
* Download reports
* Access service tab

> Auth Tokens

* Edit auth tokens

> Transfers

* Transfer devices

#### Blynk.Air: Firmware Over-The-Air Updates

* Get access
* Create new firmware shipments
* Stop/pause shipments

#### Templates

* View templates (currently it's under "Add new template")

#### Organizations

* Access organization settings
* Switch to sub-organizations
* Transfer organizations

> Owned Locations

* View locations
* Create new locations
* Edit locations
* Delete locations
* Assign users to locations

> Organization's Locations

* View locations
* Create new locations
* Edit locations
* Delete locations
* Assign users to locations

> Automations

* View automations
* Create automations
* Edit automations
* Delete automations
* Execute automations

> Developer API

* View OAuth token settings
* Create OAuth tokens
* Edit OAuth tokens
* Delete OAuth tokens

> **Analytics**

* View analytics

> **Rule Engine (under development)**

* View rule groups
* Create rule groups
* Edit rule groups
* Delete rule groups


---

# 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.blynk.io/en/~/revisions/VogQMoqSfAjFiPWKwr6n/blynk.console/settings/access.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.