---
title: Configure teams in Feature Experimentation
slug: feature-experimentation/docs/configure-teams-in-feature-experimentation
docTags: 
createdAt: 2026-08-05T20:39:59.000Z
---

- Optimizely Feature Experimentation

Create teams to manage granular permissions for entities in bulk, streamlining updates. Grouping collaborators into a team automatically applies assigned permissions to all members, simplifying onboarding and adjustments.

You can use teams across your Optimizely Feature Experimentation projects. However, to gain access, you must first add a collaborator to a project and assign them a project role. See [Collaborators](docId\:bNAxj4srKHVczBp27i1DH) or [Manage users](docId\:afJzJCmm5TkQ4CDpUlXQh) if your organization uses Opti ID.

## Create a team

:::hint{type="warning"}
**Important**

Only account Administrators can create and manage teams.
:::

1. Go to **Account Settings > Teams**.
2. Click **Add Team**. 

   ![9a674169397c1f4c08150f76bab6cc62dcc3cd1fa7e74bcbba91055e1f7470c7-image.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/R9icQ5LZ3VgT4Txork38D-20260720-145757.png)
3. On the **New Team** page, enter a **Name**.
4. (Optional) Enter a **Description**.
5. In the **Search for users to add to this team** field, type the name or email address of the collaborator you want to add. The results are automatically displayed.

:::hint{type="info"}
**Note**

The UI uses the term **user** in fields and labels. This documentation refers to these individuals as **collaborators**.
:::

6. Click the collaborator from the drop-down list to add them to your **Add users** list. 

   ![db01fa7a75138aa03610ca8df23e87f75e30e14c582e139053b5eb43b721bc20-image.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/cCWm6WO5mawgpHAfEaDg2-20260720-145757.png)
7. (Optional) In the **Add users** list, click **More options (...) > Remove** to delete the collaborator. You can re-add them by following steps five and six.
8. Click **Save**.

## Edit a team

1. Go to **Account Settings > Teams**.
2. Click the team's name you want to edit. 

   ![f8f35b64e5444255036842acf91d080b260158cef809bc33d300a00fd865d90d-image.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/edoER7Gcqok6CCYVXjG-o-20260720-145757.png)

Alternatively, click **More options (...) > Edit team**. 

![83abf23514b7879df55a399a8d8ebc7aa439e0cae12073bf96858fce54c6ae26-image.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/T0nEmONiAxK-fpN3yiDA9-20260720-145757.png)

You can update the **Name** or **Description**. You can also [add collaborators](docId\:RUb7wMNJQpJrnULmlclph) or [remove collaborators](docId\:RUb7wMNJQpJrnULmlclph).

### Add collaborator

:::hint{type="info"}
**Note**

You can [remove collaborators](docId\:RUb7wMNJQpJrnULmlclph) at the same time as you add collaborators.
:::

1. In the **Search for users to add to this team** field, type the name or email address of the collaborator you want to add. The results are automatically displayed.
2. Click on the collaborator from the drop-down list to add them to your **Add users** list.
3. (Optional) Repeat steps one and two to add more collaborators.
4. Click **Save**.

### Remove collaborator

:::hint{type="info"}
**Note**

You can [add collaborators](docId\:RUb7wMNJQpJrnULmlclph) at the same time as you remove collaborators.
:::

1. For the collaborator you want to remove, click **More options (...) > Remove**. This deactivates (grays out) the collaborator. 

   ![468973df6ce4e1ad7a955da75a9c0f5ea9d374c311c11b02ab22e857ac01189d-image.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/_yvuvS-d3ZL0YZZz_uBBd-20260720-145757.png)
2. Repeat to remove additional collaborators.
3. Click **Save**.

## Configure granular permissions for a team

Granular permissions assigned to a team are cumulative with the permissions assigned to individual collaborators. For example, if a collaborator is a **Viewer** for a flag but is part of a team that is an **Editor** for the same flag, that collaborator has **Editor** access. A collaborator can belong to multiple teams. A collaborator has the highest role assigned to them, whether individually or through a team.

To assign granular permissions, see the following:

- [Interactions between environment and flag roles](docId\:AzOxmAb1cxMjH_S5Tbgyj).
  - [Manage environment roles](docId\:a8Lou8ccOZnqTR863LJGo).
  - [Manage flag roles](docId\:F8tdFPnxECabBXsQkBqDt).
- [Manage audience roles](docId\:aG4JyFgVeCLJsPnBhfUTX).

### Flag creation behavior for collaborators in a team

When a collaborator in a team creates a flag or an audience, Feature Experimentation automatically assigns them the **Admin** role for that flag or audience using granular permissions. This ensures the collaborator can immediately manage access and share it with others.

To create a flag or audience, a collaborator must have **Editor** or **Admin** access in at least one environment, either directly or through their team. For example, if a collaborator has the **Viewer** project role but is part of a team with **Editor** access to an environment, they can create flags and audiences.

:::hint{type="info"}
**Note**

If your project does not use granular permissions, team members must have the **Editor** or **Admin** project role to create flags or audiences.
:::