Invite collaborators to your project to allow your team to manage feature flags, run experiments, roll features out, and roll them back.

1. Navigate to Settings > Collaborators.
2. Select Add a Collaborator.
3. Enter the email addresses of your collaborators, and select their permission levels. You can also invite collaborators to multiple projects at once.

Permissions

Here's the matrix of permissions for each collaborator type. Each role includes the permissions for the one before it. To summarize:

• Viewers have read-only access and cannot modify features or experiments.
• Editors and Restricted Editors can set up features and experiments in restricted environments, like local or staging environments, but can't launch features or experiments non-restricted environments like production (you can customize this with restricted environments). If a feature test is running in a restricted environment, an Editor can change only the traffic allocation or whether a feature is enabled or disabled.
• Publishers and Restricted Publishers can launch features and experiments in production.
• Administrators have full permissions to manage account settings and access to all Projects

Restricted Editors and Restricted Publishers have distinct permissions from Editors and Publishers within Web Projects. Within Full Stack Projects. We recommend using Editor and Publisher in Full Stack projects.

*** In restricted environments, Editors and Restricted Editors can create features and experiments, but can't launch, pause, or change traffic allocation. In non-restricted environments, those Editors and Restricted Editors have full access all aspects of features and experiments. We recommend using the Editor role to restrict access to production environments, while allowing full access in local or staging environments.