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.

🚧

Important

If your organization migrated to Opti ID, you must manage users in Opti ID. See
Manage roles and permissions in Opti ID and other user management options in the Opti ID Admin Center.

Collaborators

Collaborators are users who

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

People who maintain Optimizely code in a codebase but never log in or use credentials within Optimizely are not considered collaborators.

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

    In the primary (production) environment, Editors can only create rules before the ruleset is published. After publishing, Editors cannot modify the ruleset.

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

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

Permissions with metrics hub

👍

Beta

Metrics hub is in beta. Contact your Customer Success Manager or Optimizely Support for information.

Metrics hub lets you create and manage reusable metrics across multiple experiments and projects. It improves consistency and reduces configuration time by centralizing metric configuration. Metrics hub introduces new permissions that control who can create, edit, archive, and use project-level and cross-project metrics.

• One-time metrics – Created directly in an experiment and not reusable.
• Project metrics – Reusable within a single project.
• Cross-project metrics – Reusable across multiple projects in your account.

The following table outlines the available permissions for collaborators in Feature Experimentation:

📘

Note

The cross-project metric option only displays if you have the proper permissions.

Update a collaborator's permissions

1. Go to Settings > Collaborators.

2. Click on a collaborator.

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

   

Remove collaborators

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.