Account Roles and Permissions

When using Iterable to create campaigns, you'll likely collaborate with multiple people. Each of these people may need access to a specific set of Iterable's resources and capabilities, based on their responsibilities. Use custom roles, org permissions, and org admins to help your team work safely, effectively, and with appropriate access permissions.

# Table of contents

# Custom roles and their permissions

Custom roles are bundles of permissions that give team members access to the Iterable features and resources they need to efficiently do their jobs. They're defined for an organization and used as necessary across all its projects. Every custom role has a combination of the permissions described (by group) below.

# Permissions

Custom roles can include permissions taken from the following buckets:

# Channel configuration

These permissions determine whether or not members can view or configure message channels and types, senders, DNS setup, ESP accounts, mail domains, mobile apps or web push settings:

• View: Allows members to view the pages where these items are configured
• Setup & Manage: Allows members to configure these items

# Snippets

These permissions determine whether or not a member can modify an Iterable project's snippets:

• Create & Manage: Allows members to create, update and delete snippets

# Segmentation & Lists

These permissions determine whether or not a member can create, update or delete static and dynamic lists:

• Create & Manage: Allows members to create, update and delete static and dynamic lists

# Project Configuration

These permissions determine whether or not a member can configure project settings, third-party integrations, Facebook integration, API keys, system webhooks and journey webhooks:

• Project Settings: Allows members to access and make changes to an Iterable project's Settings > Project Settings screen

• Data Feeds, Third-Party Integrations, API Keys and Webhooks: Allows members to configure third-party integrations, Facebook integration, API keys, system webhooks and journey webhooks (all found on the Integrations menu)

# Catalogs

These permissions determine whether or not a member can view or manage catalogs or collections:

• View: Allows members to view the Content > Catalogs screen and the contents of catalogs
• Create & Manage: Allows members to create, update and delete catalogs

# Reports

These permissions determine whether or not a member can view or manage reports:

• View: Allows members to view the Insights > Reports screen
• Create & Manage: Allows members to create, update and delete reports

# Journeys, Campaigns & Experiments

These permissions determine how members can work with journeys, campaigns, and experiments:

• View: Allows members to access view journeys, campaigns and experiments
• Draft: Allows members to draft or clone campaigns (but not schedule them)
• Activate & Manage: Allows members to activate journeys, campaigns and experiments

# User Profiles & Data

These permissions determine whether or not a member can view, create, update or delete users (contacts):

• View: Allows members to view the contents of a project's user profiles
• Create & Manage Contacts: Allows members to create and delete users (contacts).

# Base Templates

These permissions allow users to create, update and delete base templates (which can be selected as the starting point for a new campaign).

• Create & Manage: Allows members to create, update and delete base templates

# Example custom role

Consider a hypothetical custom role that grants members the ability to create and send campaigns with pre-existing base templates and contact lists, but not view the users on those lists or their Iterable user profiles. This custom role should have the folowing permissions:

• Reports > Create & Manage, for creating and viewing reports for their campaigns.
• Workflows, Campaigns & Experiments > Activate & Manage (which automatically includes View and Draft), for creating and managing campaigns.

All other permissions can be left off of this custom role.

# Default custom roles

By default, an Iterable organization has the following custom roles, which you can modify as needed:

	Reader	Contributor	Publisher	Admin	Super Admin	Account Manager
Channel Configuration > View				X	X	X
Channel Configuration > Set Up & Manage				X	X	X
Snippets > Create & Manage		X	X	X	X	X
Segmentation & Lists > Create & Manage		X	X	X	X	X
Project Configuration > Project Settings (Labels, Custom Events, etc.)				X	X	X
Project Configuration > Data Feeds, Third-Party Integrations, API Keys and Webhooks				X	X	X
Catalogs > View	X	X	X	X	X	X
Catalogs > Create & Manage		X	X	X	X	X
Reports > View		X	X	X	X	X
Reports > Create & Manage		X	X	X	X	X
Workflows, Campaigns & Experiments > View	X	X	X	X	X	X
Workflows, Campaigns & Experiments > Draft		X	X	X	X	X
Workflows, Campaigns & Experiments > Activate & Manage			X	X	X	X
User Profiles & Data > View				X	X	X
User Profiles & Data > Create & Manage Contacts		X	X	X	X	X
Base Templates > Create & Manage		X	X	X	X	X

# Org permissions

Org permissions allow team members to manage various aspects of an Iterable organization. These permissions are granted outside the scope of any custom roles and are managed on a member-by-member basis. Iterable provides the following org permissions:

• Manage Billing: Allows the member to view usage data and update payment information for an Iterable organization

• Create Projects: Allows the member to create new projects in an Iterable organization

• Manage Members: Allows the member to create new organization members, edit their account details, send password reset emails, disable two-factor authentication, and modify project membership and roles (for projects on which the permission holder is also a member). This permission does not allow holders to assign/revoke org permissions, assign/revoke org admin status or remove organization members.

• Manage Roles: Allows the member to create custom roles and modify their included permissions

# Org admins

Org admins are the most privileged members in your Iterable organization. These members:

• Have all org permissions.
• Can assign and revoke org permissions.
• Can assign and revoke org admin status.
• Can remove users from an organization.
• Automatically receive all permissions on every project in your organization (current and future).

# Further reading

• Creating and Updating Custom Roles
• Creating and Managing Member Accounts