Roles are groups of permissions specific to an Iterable organization, tailored to the various types of contributors who will access its projects.
These roles impact how team members can work with an Iterable project's message channels, snippets, segmentation and lists, configuration, catalogs, reports, journeys/campaigns/experiments, user profiles and base templates.
Keep reading to learn how to create a new custom role.
NOTE
For an overview of roles and the permissions they can contain, including default roles, read Permissions for Using Iterable.
In this article
IMPORTANT
Remember to save your work! Changes are not auto-saved when creating or changing a role.
If you leave the page without clicking Save Role, you'll need to start over.
If you seen a Role Permissions Could Not Be Saved error, try again.
Viewing and creating custom roles
Members with the Manage Roles org permission can view, create, and edit roles.
To view all existing roles, and go to Settings > Roles.
To see the selected permissions for an existing role, hover over the count in the Permissions column.
To create a new role:
Click New Role.
Provide a name for the new role.
(Optional) To start with an existing permission set, choose from the dropdown underneath Copy Permissions From...
Click Create Role
-
Select permissions as necessary.
Click Save role.
Updating roles
Any member with the Manage Roles org permission can edit the name of an existing role and its assigned permissions.
IMPORTANT
When you modify a custom role, users who already have that role receive its updated set of permissions.
To edit a role:
Go to Settings > Roles.
Click the name of the role you wish to change.
To edit the role's name, click the pencil icon next to it and enter the new name.
To update permissions, check and uncheck permissions as needed.
Click Save Role to complete your changes.
It isn't currently possible to delete custom roles. However, they can be renamed, modified, and reused.
Permission inheritance
When selecting permissions, you may notice that some of them are pre-selected, grey, and uneditable. Permissions in this state are automatically included by another, higher-order permission that you've also selected.
Example: If you select the Create and Manage Catalogs permission, then View Catalogs will also be selected. This is because a member must first be able to view catalogs before they can create and manage them.
Example custom role: Email marketer
Consider a hypothetical custom role for an email marketer. These users would need a role that grants members the ability to create and send email campaigns from pre-existing templates and contact lists, but not view the users on those lists or their Iterable user profiles, nor send from any other message medium. Members with this role also need to access reports to review campaign results. This custom role should have the following permissions:
-
Create and Manage Reports, for creating and viewing reports
for their campaigns. - Manage and Launch Campaigns for Email (which automatically includes View and Draft), for creating and managing email campaigns.
All other permissions can be left off of this custom role.
Default roles
By default, an Iterable organization has the following roles by default, which you can modify as needed:
Reader | Contributor | Publisher | Admin | Super Admin | Account Manager | |
---|---|---|---|---|---|---|
Project | ||||||
Manage Settings | X | X | X | |||
Manage Integrations | X | X | X | |||
View Channels | X | X | X | X | X | |
Setup and Manage Channels | X | X | X | |||
Messaging | ||||||
View Journeys, Campaigns, and Experiments | X | X | X | X | X | X |
Draft Journeys, Campaigns, and Experiments | X | X | X | X | X | |
Manage and Publish Journeys | X | X | X | X | ||
Manage and Launch Campaigns (all message mediums) | X | X | X | X | X | |
Content | ||||||
Create and Manage Templates | X | X | X | X | X | |
Create and Manage Snippets | X | X | X | X | X | |
View Catalogs | X | X | X | X | X | X |
Create and Manage Catalogs | X | X | X | X | X | |
Audience | ||||||
Setup and Manage Segmentation and Lists | X | X | X | X | X | |
View User Profiles and Data | X | X | X | |||
Create and Manage User Profiles and Data | X | X | X | X | X | |
Insights | ||||||
View Predictive Goals | X | X | X | X | X | X |
Create and Manage Predictive Goals | X | X | X | X | X | |
View Reports | X | X | X | X | X | |
Create and Manage Reports | X | X | X | X | X |
Assigning roles to members
Each member of an Iterable organization must have at least one project + role assigned to them. Roles are assigned on a per-project basis, and a member can have different roles for different projects.
To learn how to assign projects and roles to team members, grant org permissions, and org admin status, read Creating and Managing Member Accounts.