# Access type overview

[Roles](/organization-and-account-settings/users-and-roles/create-new-role.md) in your organization are primarily defined by the access types configured for them which dictate the level of access that role has per feature within you Didomi account. In this article, we will cover:

* [Access types](#access-types)
* [Access types per feature](#access-types-per-feature)
* [Admin role](#admin-role)

{% hint style="info" %}
We encourage your organization to consider how individual users and teams within your organization will utilize the Didomi platform before assigning access types to different roles.
{% endhint %}

***

### Access types

There are three possible access types that can be granted for a feature. 

{% hint style="info" %}
Not every feature will include all three access types. Please refer to [Access types per feature](#access-types-per-feature) for more information.
{% endhint %}

<table data-full-width="false"><thead><tr><th width="216.2666015625">Access Type</th><th>Description</th></tr></thead><tbody><tr><td>No Access</td><td>The role has no access to the feature. The feature's components will be hidden from any user assigned to the role.</td></tr><tr><td>Viewer</td><td>The role can navigate to the feature and view most of the components associated with the feature. The role will be unable to create, edit, or otherwise manage components in the feature. </td></tr><tr><td>Editor</td><td>The role can create, edit, and/or delete components in the feature.</td></tr></tbody></table>

### Access types per feature

Review the table before to see the available access types on a per feature basis:

<table><thead><tr><th width="258.86669921875">Feature</th><th data-type="checkbox">No Access</th><th data-type="checkbox">Viewer</th><th data-type="checkbox">Editor</th></tr></thead><tbody><tr><td>Organization Settings</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Users &#x26; Roles</td><td>true</td><td>true</td><td>false</td></tr><tr><td>Data Manager</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Consent Notices</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Analytics</td><td>true</td><td>true</td><td>false</td></tr><tr><td>Notice Versions</td><td>true</td><td>true</td><td>false</td></tr><tr><td>Consent Proof Reports</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Compliance Report</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Domains</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Branding</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Widgets</td><td>true</td><td>true</td><td>true</td></tr></tbody></table>

### Admin role

Every Didomi account comes pre-populated with an Admin role that can not be edited nor deleted. In addition to having editor access to all features in your Didomi account, the Admin role also allows an assigned user to:

* Invite, edit, and delete users
* Create, edit, and delete roles
* Granted automatic editor access to new features released by Didomi
* Granted automatic editor access to new premium features by Didomi (if organization subscribes to premium feature)


---

# Agent Instructions: 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.didomi.io/organization-and-account-settings/users-and-roles/access-type-overview.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.