This release introduces Custom Roles, which allow Iterable organizations to define groups of permissions that grant access to Iterable features and resources based on a team member's needs. These roles are defined for an organization and reused as necessary across all its projects, making it possible to efficiently assign roles to multiple team members who perform similar functions—no matter which projects they're working on.
Historically, Iterable provided pre-defined roles, each of which included a specific set of permissions.
By contrast, Custom Roles enable organizations to create permission bundles tailored to the specific needs of their team members. Every custom role can include permissions related to channel configuration, snippets, segmentation and lists, project configuration, catalogs, reports, workflows/campaigns/experiments, user profiles and base templates.
Members receive custom roles on a project-by-project basis.
Org permissions and org admins
Individual team members can also have org permissions. Granted outside the scope of any custom role, these permissions control whether or not a member can manage billing, create projects, manage team members or manage roles.
Org admin members are the most privileged members in an Iterable organization. They have all org permissions, belong to all projects and have all possible permissions on each of those projects.
Migrating to custom roles
Iterable has migrated all organizations to Custom Roles. To do this, a new custom role was created for each previously existing, predefined role, and these new roles were assigned to members as applicable.
To learn more about Custom Roles, read:
- Account Roles and Permissions
- Creating and Updating Custom Roles
- Creating and Managing Member Accounts
If you have any questions about Custom Roles, please contact your Iterable customer success manager.