> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/editable/admin-portal-and-editable-console/admin-portal/user-management/user-roles-and-permissions.md).

# User Roles and Permissions

The table below lists the default user roles available in the EDITable console, along with their associated permissions.

<table><thead><tr><th width="263">Roles</th><th>Associated Permissions</th></tr></thead><tbody><tr><td>Admin</td><td>Complete control within the product with no restrictions.</td></tr><tr><td>EDITable Admin</td><td>Access to all EDITable settings and writeback.</td></tr><tr><td>EDITable Input Users</td><td>Access to add comments and execute writeback.</td></tr><tr><td>EDITable Database Admin</td><td>Access the writeback configurations in the admin connection portal and create/alter tables.</td></tr><tr><td>EDITable Approvals Users</td><td>Access to review requests and take actions, execute writeback, add comments, and access audits.</td></tr></tbody></table>

Let's look at the permissions in detail for each profile.

## 1. Admin

Admins have complete control within the product with no restrictions. They have full access to all report-level features and can manage their associated settings, such as data input, writeback, approvals, audits, etc. This also includes settings related to connected planning, such as Infobridge settings, forecasts, snapshots, scenarios, etc.

They have access to the Admin Portal, where they can add or remove users, manage their roles and policies, create and define custom roles and policies, and manage general settings, writeback settings, and available assets.

## 2. EDITable Admin

EDITable admins have access to all EDITable settings and execute writeback. Their permissions are as follows:

#### Writeback

* Execute writeback

#### Comments

* Add and manage comments
* Configure comment permissions and settings

#### Editable

* All EDITable settings

#### Audit

* Audit

## 3. EDITable Input Users

EDITable input users can add comments and execute writeback. They have the following permissions:

#### Writeback

* Execute writeback

#### Comments

* Add and manage comments
* Configure comment permissions and settings

#### Audit

* Audit

## 4. EDITable Database Admin

EDITABLE Database admins have access to change the writeback configurations and settings in the admin connection portal, as well as create or alter tables. This includes the following:

#### Writeback

* Manage writeback configurations
* Create source table
* Alter source table

## 5. EDITable Approvals Users

Approval users can approve requests, execute writebacks, add comments, and access audits. Their permissions include the following:

#### Writeback

* Execute writeback

#### Comments

* Add and manage comments
* Configure comment permissions and settings

#### Editable

* Approval Users

#### Audit

* Audit

In addition to these default roles, workspace admins can create custom roles and configure their policies on a granular level, ensuring enhanced data governance and security.


---

# 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:

```
GET https://docs.inforiver.com/editable/admin-portal-and-editable-console/admin-portal/user-management/user-roles-and-permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
