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

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.

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

### see, create, and edit communication templates
- **Templates**: `create`, `edit`
- **Communications** > **_communication type_**: `create`, `edit`

### delete templates
**Templates**: `delete`

### see and create campaign directories
**Communications** > **_communication type_**: `create`, `edit`

### delete campaign directories
**Communications** > **_communication type_**: `delete`

### see and create campaign tags
**Assets** > **Tags**: `read`

This includes seeing the tags assigned to a campaign.

### see the communication calendar
**Settings** > **Calendar**: `read`

### work with: Email, SMS, Web Push, Mobile Push, Dynamic Content, In-App Messages or Landing Pages

#### see the campaigns
- **Communications** > **_campaign type_**: `read`

#### see campaign statistics
**Analytics** (all): `read`

#### create, edit or edit a campaign
- **Communications** > **_campaign type_**: `create`, `edit`
- **Settings** > **Global Control Group**: `read`
- **Templates**: `execute`, `create`, `edit`
- **Email only**: 
    - **Settings** > **Integrations**: `read`
    - To add attachments: **File explorer**: `create`
    - To see if a test recipient is an existing profile: **Profiles** > **Client details**: `read`
- To use an existing segmentation as the audience: **Analytics** > **Segmentations**: `read`
- To define a new audience: **Analytics** > **Segmentations**, **Expressions**, **Aggregates**: `read`
- To see suggestions in audience filter values: **Profiles** > **Client list**: `read`


<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 defining audience conditions, if you have `create` access to any campaign type, 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 audiences and configure conditions without requiring separate attribute management access.

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


#### duplicate or move a campaign
- **Communications** > **_campaign type_**: `create`, `edit`
- **Settings** > **Global Control Group**: `read`
- **Templates**: `execute`, `create`, `edit`

#### preview a Landing Page 
**Communications** > **Landing Page**: `create`, `edit`

#### launch, pause, or stop a campaign
**Communications** > **_campaign type_**: `execute`

#### delete a campaign
**Communications** > **_campaign type_**: `delete`

#### clone a campaign

In the source and target workspace, you need:
- **Cloning**: `create` 
- `create` and `edit` permissions for the cloned campaign 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).

### work with Screen Views

#### see Screen Views
- **Assets** > **Documents**: `read`
- **Communications** (any): `read` -  required to see Experience Hub

#### create and update Screen Views
- **Assets** > **Documents**: `create`, `edit`
- To use audiences other than ALL: **Analytics** > **Segmentations**, **Expressions**, **Aggregates**: `read`

#### activate, pause, and finish Screen Views
**Assets** > **Documents**: `create`, `edit`

#### duplicate and move Screen Views
**Assets** > **Documents**: `create`, `edit`

#### delete screen views
**Assets** > **Documents**: `delete`