In Iterable, managing members and their permissions is crucial for controlling your account security and ensuring that everyone has appropriate levels of access. Depending on their job roles and responsibilities, your team members may need to use different features and data within Iterable.
This article provides an overview of how permissions work in Iterable, and explains the key terms you should know when setting up and managing members in your account.
In this article
Terms you should know
Here are some key terms to understand while setting up and managing members in Iterable.
Member
Users of Iterable who have been granted access to the platform. Members only have access to the settings and features that they've been granted permission to use, through a combination of organization permissions, project assignments, and roles.
Org admin
Also called an "administrator", "org administrator", or "admin". These members have universal access to Iterable features and organization settings and are automatically assigned all role permissions for all current and future projects. Every Iterable organization must have at least one org admin. Org admins can't have custom permissions. Instead, create a member and grant organization permissions as necessary.
Org permission
Org permissions define what a member can do to manage an Iterable organization and its members. Org admins are automatically assigned all org permissions, and these cannot be revoked. Members can have full, partial, or no org permissions.
These permissions are optional and aren't required for a member to use Iterable.
To view a complete list of org permissions and what they allow members to do, read Permissions for Using Iterable.
Org role
A member's overall assignment as an org admin or as a regular member.
Organization
Also called "org" or sometimes "account". An organization is the top-level account in Iterable that contains all projects, members, and settings.
Project
A container for campaigns, journeys, data, templates, lists, user profiles, and other Iterable resources. Data contained in a project is isolated from other projects, and members can only access the data in the projects they're assigned to.
Role
Roles are bundles of permissions that define what a member can do within a project. Members can have different roles for different projects.
A new Iterable organization comes with preset default roles, so you can quickly get started. However, you can also create custom roles for your members as needed.
Roles are managed centrally at the organization level. When you make changes to a role's permissions, all members assigned to that role are automatically updated to reflect the new permissions.
To learn more, read Creating and Managing Custom Roles.
Role permissions
Granular permissions that define what a member can do within a project. These permissions are bundled into roles, which are then assigned to members. To view a complete list of role permissions and what they allow members to do, read Permissions for Using Iterable.
Understanding how permissions work in Iterable
Each member in Iterable has an org role, one or more project assignments with a specified role, and may also have org permissions. These permission controls work together to ensure that everyone can access the parts of Iterable they need.
When you join Iterable as a new organization, your account starts with a set of predefined roles that you assign to members permissions on projects. You can customize these roles to fit your organization's needs, or create your own custom roles.
To learn more, read Creating and Managing Custom Roles.
When you create a new member in Iterable, assign them to at least one project and give them a role for that project.
Every time you assign a project to one of your team members, you must also give them a role for that project. A member's role can be different for each assigned project.
You can manage project assignments for each member independently within Iterable. However, if you're using SSO for authorization, you must update project and role assignment settings in your IdP.
Org admins are automatically assigned to all projects, including existing projects and those created in the future. They also have all role permissions for all existing and future projects in the organization, so you don't need to assign projects or roles to them.
Want to learn more?
For more information about some of the topics in this article, check out this Iterable Academy course. Iterable Academy is open to everyone — you don't need to be an Iterable customer!
Iterable Academy
Support docs