Permissions

Groups make it easy to create a collection of users with shared permissions. In Split, you can enable permissions by environment, split, segment, or metric, limiting the actions that non-editors can take.

Environment-level

Administrators can control who can edit and configure splits and segments across an environment using environment-level permissioning. You can set the change permissions for an environment to limit categories of actions to administrators, individual users, or groups.

Use permissions to:

• Limit access to production environments: For example, for security compliance or per company requirements, you can limit edit access in production to an authorized group of individuals.
• Limit access by teams: For example, for improved usability, you can limit edit access for different teams that only need access to certain environments.

Setting Environment-level Change Permissions

An environment has three settings that can be set:

• Anyone can edit
• Restrict who can edit
• Require approvals for changes

Anyone can edit

By default, all environments are set to allow anyone to edit. When this setting is selected for an environment. Any user will be able to make changes to splits and segments in this environment. Users can also set per split and segment change permissions in this environment.

Restrict who can edit

After selecting "Restrict who can edit", you can select any groups or users to be editors for splits and segments in this environment.

In an environment where change permissions are set to "Restrict who can edit", only those added as editors can do the following:

• Add a split to the environment.
• Edit an existing split definition (including kill/restore functionality).
• Delete a split.
• Add a segment to the environment.
• Edit an existing segment.
• Delete a segment.
• Add additional editors.

Editors can still add more editors to individual splits and segments in this environment.

Require approvals for changes

After selecting "Require approvals for changes", you will have the option to select:

• Let submitters choose their approver(s) - If this is selected, all changes to splits and segments in this environment will require a submitter to select at least one other user besides themselves to review and approve a change before it can go live.
• Restrict who can approve - After selecting "Restrict who can approva", you can select any groups users, or api keys to be approvers for splits and segments in this environment. Similar to the previous option, all changes to splits and segments in this environment will require approval, but they will all be submitted to the group you select here.

Note: For either option, you will also have the capability to check "Allow kills without approval" - If this is selected, users will be allowed to kill a split without submitting for approval. This can be useful if you want most of your changes to get a least two pairs of eyes on them but want to let teammates quickly move customers to a safe state without asking another person in case of an emergency.

Split/segment/metric-level permissions

If a particular environment has change permissions set to "Anyone can edit", any user can set individual change permissions for a split, segment, or metric.

Set split/segment/metric-level change permissions

Set up split/segment/metric-level change permissions in a few steps:

1. Go to the split, segment, or metric.
2. Select the environment that you want to enable permissions in.
3. Select the Editing dropdown and click the radio button for "Restrict who can edit".
4. Select additional users or groups as editors.
5. Click Apply.

When setting change permissions for a particular split or segment in an environment, the owners and the user making the change are automatically added as editors, along with the organization's administrators.