Invite collaborators to your Optimizely Feature Experimentation project to let your team manage flags and experiments. The number of collaborators is limited to your Optimizely Feature Experimentation plan. View the plans & pricing page on Optimizely.com for more information and current collaborator limits.
Collaborators are users that:
- Log into the Optimizely application.
- Utilizes an Optimizely Feature Experimentation API where authentication is required.
- Somehow interact with an Optimizely interface, either by logging in or through an API.
On the other hand, there may be additional people involved in a project who are not considered collaborators in Optimizely Feature Experimentation. For example, a developer who maintains Optimizely code in their code base and does not use any Optimizely Feature Experimentation credentials is not considered a collaborator.
- Go to Settings > Collaborators.
- Click Invite a Collaborator.
- Enter the email addresses of your collaborator, select their permission levels, and select the language. You can also invite collaborators to multiple projects at once.
- (Optional) Click the Plus button to add additional collaborators.
Each role includes the permissions for the one before it.
- Viewer – Read-only access and cannot modify flags or rules.
- Editor –
- Non-production environments (like Development or Staging) – Can manage flags and rules.
- Production environments (Primary environment) – Can manage flags and rules, but cannot launch flags. Once the flag is turned on by a Publisher or higher, an Editor can not turn the flag off, pause a rule, adjust traffic, change the variations, add or remove metrics, or change audiences.
See Manage environments for more information.
- Publisher – Can launch flag rules in production (primary) environments.
- Project Owner and Administrator – Full permissions and can manage account settings.
|Experiments (create, edit, start, pause, archive)||No||Yes *||Yes||Yes||Yes|
|Variations (create, edit, re-allocate traffic, pause, delete)||No||Yes *||Yes||Yes||Yes|
|Flags (create, edit, archive)||No||Yes *||Yes||Yes||Yes|
|Variable keys (create, edit, delete)||No||Yes *||Yes||Yes||Yes|
|Traffic allocation (edit)||No||Yes *||Yes||Yes||Yes|
|Events (create, edit, archive)||No||Yes *||Yes||Yes||Yes|
|Audiences (create, edit, archive)||No||Yes||Yes||Yes||Yes|
|Add specific users (add users, edit, delete)||No||Yes *||Yes||Yes||Yes|
|Attributes (create, edit, archive)||No||Yes||Yes||Yes||Yes|
|Collaborators (invite, edit, delete)||No||No||No||Yes||Yes|
|Environments (create, edit, archive)||No||No||No||Yes||Yes|
|Webhooks (create, delete)||No||No||No||Yes||Yes|
|Integrations (create, edit, delete)||No||No||No||Yes||Yes|
|Mutual exclusion groups (create, edit, delete)||No||Yes||Yes||Yes||Yes|
*** In production environments, Editors can create flags and rules but cannot launch a flag, pause a rule, adjust traffic, change the variations, add or remove metrics, or change audiences.
In non-production environments, Editors have full access to all aspects of flags and rules. Optimizely recommends using the Editor role to restrict access to production environments while allowing full access in development or staging environments.
To update a collaborator's role:
Go to Settings > Collaborators.
Click on a collaborator.
Select the new role from the Role drop-down menu.
To remove a collaborator:
- Go to Settings > Collaborators.
- Click on a collaborator.
- Click Remove From Project or Remove From Account in the collaborator details
- Remove From Project – Removes the collaborator from the selected project.
- Remove From Account – Removes the collaborator's access to all projects.
Updated 17 days ago