Collaborators

Invite collaborators to your Optimizely Feature Experimentation project to let your team manage flags and experiments. After adding your teammates as collaborators, you can give them Granular roles and permissions to set fine-grained access controls for the entities in your project.

📘

Note

If your organization migrated to Opti ID, you must manage users in Opti ID. See the
Opti ID user documentation.

Collaborators

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 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.

Invite collaborators

1. Go to Settings > Collaborators.
2. Click Invite a Collaborator.
3. 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.
4. (Optional) Click the Plus to add additional collaborators.

Permissions

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. When 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.

    📘

    Note

    For the Editor role, you can only create rules in the primary environment before this environment's ruleset is published. Once it is published, you can no longer do so as an editor.

  • See Manage environments for information.
• Publisher – Can launch flag rules in production (primary) environments.
• Project Owner and Administrator – Full permissions and can manage account settings.

📘

Note

To let users create multiple experiments per flag, you must grant the collaborator the flags_multiple_experiments permission. Multiple experiments per flag are only available for select plans.

* 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. You should use the Editor role to restrict access to production environments while allowing full access to development or staging environments.

Update a collaborator's permissions

To update a collaborator's role:

1. Go to Settings > Collaborators.

2. Click on a collaborator.

3. Select the new role from the Role drop-down list.

   

Remove collaborators

To remove a collaborator:

1. Go to Settings > Collaborators.
2. Click on a collaborator.
3. Click Remove From Project or Remove From Account in the collaborator details
   1. Remove From Project – Removes the collaborator from the selected project.
   2. Remove From Account – Removes the collaborator's access to all projects.

Set granular roles

After adding collaborators to your project, use Granular roles and permissions to set access control to the environments and flags in your project.