This article describes the [permissions](/docs/settings/identity-access-management/permissions) needed to use the [Decision Hub](/docs/analytics).

To set the permissions, you need to create a user role or edit an existing one and open the Permissions matrix. In the matrix, the permissions are collected into groups. Some of these groups can be expanded to set more granular permissions.


<div class="admonition admonition-note"><div class="admonition-icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2.5"><path stroke-linecap="round" stroke-linejoin="round" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z" /></svg></div><div class="admonition-body"><div class="admonition-content">

To create a [local analysis](/docs/analytics/inline-analytics), you only need the permissions for the parent analysis that includes the local analysis.

</div></div></div>


## How to read this list

In this article, each heading describes an action. The permissions for that action are described in the form of breadcrumbs.

**For example**, if the required permissions are:
- **Profiles** > **Client list**: `read`
- **Search engine**: `create`, `edit`

The permission matrix needs to look like this:
<figure><img src="/api/docs/image/8aa18695b9ddf90415ab9b9c2fdf6e90734cca60/docs/settings/_gfx/permissions-example.png" class="large" alt="Permission matrix in Synerise Settings showing Profiles with read access on Client list and Search engine with create and edit permissions"><figcaption>Permission example, see description above figure.</figcaption></figure>

The `read` permission is not explicitly listed when any higher permission is required - the portal enables it automatically.

## I want to...

### access the Decision Hub

You need any `read` permission from the **Analytics** category.

### work with dashboards
**Analytics** (all):  
- `read` - to see dashboards
- `create` - to create dashboards
- `edit` - to update dashboards
- `delete` - to delete dashboards

### view analyses

**Analytics** > **_analysis type_**: `read`

### edit analyses

**Analytics** > **_analysis type_**: `edit`

### create analyses

**Analytics** > **_analysis type_**: `create` 


<div class="admonition admonition-note"><div class="admonition-icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2.5"><path stroke-linecap="round" stroke-linejoin="round" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z" /></svg></div><div class="admonition-body"><div class="admonition-content">

When creating analyses, you can view the list of profile attribute names (without values) through the attribute selector. This does not require **Assets** > **Attributes**: `read` permission. This behavior is intentional: it allows you to build analyses and configure conditions without requiring separate attribute management access.

</div></div></div>


### duplicate analyses

**Analytics** > **_analysis type_**: `create`

### delete analyses
**Analytics** > **_analysis type_**: `delete`
  
### preview results

- **Analytics** > **_analysis type_**: `read`
- To select a profile context for preview:
  - **Profiles**: `read` - to search or select from the list of all profiles
  - **Analytics** > **Segmentations**: `read` - to select a profile from a segmentation

### clone an analysis to another workspace

In the source and target workspace, you need:
- **Cloning**: `create` 
- `create` and `edit` permissions for the cloned analysis type and all nested objects that will also be cloned in the process.

To learn more about cloning, see [Cloning objects to other workspaces](/docs/settings/workspace/cloning-objects).

### share segmentation results and access synchronization logs

- **Analytics > Segmentations**: `read`, `execute`, `create`, `edit`
- **Assets > Membership attribute sync**: `read`, `execute`, `create`, `edit`