Creating custom roles and permissions

Leanplum comes out of the box with a set of predefined Roles. These include Viewer, Analyst, Marketer, Member, and Admin. Additionally, you can define any number of custom Roles, each with a combination of Permission Levels across the Dashboard Spaces.

For example, QA Testers could have Publish access to Messages, but Read-only access to Variables and UI Editor. Similarly, Product Managers could have Manage access to Variables, but Read-only access to Messages.

Available Permissions

There are five distinct permission levels, spanning from No Access to Read-only to full Manage access. We provide the ability to choose a different permission level for each of the dashboard spaces below.

  • No Access. This is only applicable to Analytics where end users can't view any analytics
  • Read. This is the lowest setting and gives read-only access.
  • Draft. The account is permitted to make changes on the dashboard, but cannot publish them. In general, this privilege gives the account the ability to make changes that are readily reversible and do not impact end users.
  • Publish. The account is permitted to publish changes that impact end users.
  • Manage. The account has full access to that Capability.

When creating or editing a custom role, you can choose one of these permissions for each of the following seven dashboard spaces:

  1. Messages
  2. Variables
  3. UI Editor
  4. Users
  5. Analytics
  6. App Settings
  7. Team

Create a New Role

You can name the roles however you like, and define an unlimited number of different roles. To do so:

  1. Navigate to the Team page
  2. Click Edit Roles at the bottom of team members list
  3. Click Add a New Role
  4. Adjust the permission settings for each of the seven Dashboard Spaces.
  5. Give your role a name.

Note: you must be a Team Admin in order to edit roles.

Example

As an example, let's create a new Role with a set of permissions for a Product Manager. Since a typical Product Manager won't need to send messages or add new members to the team, we'll give them Read permissions for messages and team, but Publish and Manage permissions for the rest.

Here's how that would look. 

 

Once you have created the custom roles to best fit your organization, you can then assign the role to new or existing team members.

Frequently Asked Questions

Q: What about A/B Tests? That section is not on the list of Spaces above.

  • In general, you have the ability to A/B test any elements where you have permission to Draft or Publish.
  • To draft an A/B test, you need at least Draft permission on Messages, Variables, or UI Editor.
    • With Message permission, you can draft A/B tests that modify messages.
    • With Variables permission, you can draft A/B tests that modify app variables.
    • With UI Editor permission, you can draft A/B tests that modify UI interfaces.
  • To publish an A/B test, you need at least Publish permission on Messages, Variables, or UI Editor.
    • With Message permission, you can publish A/B tests that modify messages.
    • With Variables permission, you can publish A/B tests that modify app variables.
    • With UI Editor permission, you can publish A/B tests that modify UI interfaces.

Was this article helpful?
Have more questions? Submit a request