Permissions for Using Iterable

Iterable provides a flexible system for managing roles and permissions for members in your organization. This system allows you to control what each member can do in Iterable, and to ensure that each member has the access they need to do their job effectively.

In this guide, you can find a reference for all of the permissions available in Iterable and what they allow members to do.

# In this article

# Org role

An org role is an overall assignment of whether a member is considered an account administrator for the organization. Org roles include:

• Org admin (also called administrator, admin, or org administrator)
• Member

# Org administrators

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 add and remove users from an organization.
• Automatically receive all permissions on every project in your organization (current and future).

# Members

Members are the standard role for users in your Iterable organization. These members:

• May be assigned one or more org permission (but these are not required).
• Must be assigned to at least one project before you can send them an invitation to join Iterable.
• Must be assigned a role for each project they're a member of.

# Org permissions

Org permissions allow members to manage various aspects of an Iterable organization. These permissions are independent of project assignments and roles.

Iterable provides the following org permissions:

• Manage Billing – Allows the member to view usage data and update payment information for an Iterable organization in the Settings > Usage and Billing screen.

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

• Manage Members – Allows the member to:

  • Access the Organization Members screen, where they can:

    • View a listing of all members
    • Add new members to the organization
    • View a member's account details and make the following actions:
      • Edit a member's account details
      • Send invitations for new accounts to join Iterable
      • Reset passwords
      • View a list of all projects in the member account details page
      • Assign or remove projects for a member (but not their own)
      • Change a member's role on a project (but not their own)

  • Access the Authentication screen to use the SAML JSON Builder, which is necessary for setting up roles and permissions for SAML SSO.

  • This permission doesn't allow a member to:

    • Change org permissions for a member
    • Create org admins
    • Remove members from the organization
    • Change an organization's authentication settings

• Manage Roles – Allows the member to create roles and modify role permissions.

# Role permissions

Roles can include permissions taken from the following groups:

# Project

# General 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:

• Manage Settings – Allows members to access and make changes to an Iterable project's Settings > Project Settings screen and the Settings > Data Schema Management page.

  More specifically, it allows users to:

  • View and update project settings.
  • Create, rename, and delete labels.
  • View and update field and event management settings.
  • View and create custom events and custom event fields.
  • View and update user profile fields.
  • View list and journey references (such as in the Settings > Data Schema Management page).

  Note that this permission doesn't allow members to assign new members to a project. Instead, use the org permission Manage Members.

• Manage Integrations – Allows members to configure third-party integrations, including Smart Ingest, Facebook integration, API keys, system webhooks, and journey webhooks (all found on the Integrations menu).

# Channels

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

• View – Allows members to view channel and embedded message placement configuration pages. It can be useful to view these settings when working with campaigns.

• Setup and Manage – Allows members to create and configure channels, to create and manage embedded message placements.

# Messaging

# Journeys, Campaigns, and Experiments

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

• View – Allows members to view journeys, campaigns, and experiments.

• Draft – Allows members to draft or copy journeys, campaigns, and experiments (but not launch or schedule them).

• Manage and Publish Journeys – Allows members to manage and activate journeys.

• Manage and Launch Campaigns – Allows members to send, schedule, activate, and manage campaigns and experiments. When you select this permission, you must also select one or more message mediums:

  • Email
  • SMS
  • In-app
  • Push
  • Web push
  • Embedded

  Project members can manage and publish campaigns and experiments only for the message mediums included in their project role.

  If a member doesn't have permission to launch campaigns for a given message medium, that action will be disabled in Iterable's UI.

# Content

# Templates

These permissions allow users to create, update, and delete templates.

• Create and Manage – Allows members to create, update, and delete templates on the Content > Templates page.

# Snippets

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

• Create and Manage – Allows members to create, update, and delete snippets.

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

• Create and Manage – Allows members to create, update, and delete catalogs and collections.

# Audience

# Segmentation and Lists

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

• Create and Manage – Allows members to create, update, and delete static and dynamic lists.

# User profiles and data

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

• View – Allows members to view the contents of a project's user profiles.

• Create and Manage Users – Allows members to create, update, and delete users.

# Insights

# Predictive goals

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

• View – Allows members to view the contents of a Predictive Goal.

• Create and Manage – Allows members to create and delete Predictive Goals.

# Reports

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

• View – Allows members to view the Insights > Reports screen, and to view Messaging Insights.

• Create and Manage – Allows members to create, update and delete reports, and to save views in Messaging Insights.

# Role permission inheritance

Some role permissions are interdependent. When you select a permission, Iterable automatically selects other permissions that are required for the selected permission to work correctly. When this happens, the related permissions are pre-selected, greyed out, and uneditable.

Example: If you select the Create and Manage Catalogs permission, then View Catalogs is also selected. This is because a member must first be able to view catalogs before they can create and manage them.

# Want to learn more?

For more information about some of the topics in this article, check out these resources. Iterable Academy is open to everyone — you don't need to be an Iterable customer!

Iterable Academy

• Account Roles & Permissions

Support docs

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