> ## Documentation Index
> Fetch the complete documentation index at: https://docs.codecobra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams

> Organize members into teams with specific permissions for projects.

Teams let you group organization members and control what they can do within specific projects. This is how you manage who can merge code, create projects, and access specific work.

## Create a team

<Steps>
  <Step title="Open your organization">
    Navigate to the organization page from the sidebar.
  </Step>

  <Step title="Go to the Teams section">
    Scroll to or click on the **Teams** area.
  </Step>

  <Step title="Create a new team">
    Click **Create Team** and give it a descriptive name (e.g., "Developers", "Project Leads", "QA Team").
  </Step>
</Steps>

## Team permissions

Each team has four permission toggles that control what its members can do:

| Permission                   | What it controls                                                                  | Default |
| ---------------------------- | --------------------------------------------------------------------------------- | ------- |
| **Merge to staging**         | Team members can merge task branches to staging branches for testing              | Off     |
| **Merge to production**      | Team members can merge staging branches to production for deployment              | Off     |
| **Create projects**          | Team members can create new projects within the organization                      | Off     |
| **Auto-add to new projects** | The team is automatically assigned to any new project created in the organization | Off     |

### Example team configurations

Here are some common team setups:

| Team name         | Staging | Production | Create projects | Auto-add |
| ----------------- | ------- | ---------- | --------------- | -------- |
| **Developers**    | Yes     | No         | No              | Yes      |
| **Project leads** | Yes     | Yes        | Yes             | Yes      |
| **Stakeholders**  | No      | No         | No              | Yes      |
| **Contractors**   | Yes     | No         | No              | No       |

<Tip>Start with broad teams and refine as needed. A "Developers" team with staging access and a "Leads" team with production access covers most use cases. You can always create more specific teams later.</Tip>

## Assign members to teams

To add organization members to a team:

1. Open the team
2. Click **Add Member**
3. Select members from the organization

A person can belong to **multiple teams**. Their effective permissions are the combination of all their team permissions. For example, if someone is on a "Developers" team (staging only) and a "Leads" team (staging + production), they can merge to both staging and production.

## Assign projects to teams

Teams control which projects **Members** can see. (Owners and admins always see everything.)

1. Open the team
2. Go to the **Projects** section
3. Assign or unassign projects

When a project is assigned to a team, all members of that team can see and work on that project. If a member isn't on any team that has access to a project, they won't see it.

<Info>Organization owners and admins can always see all projects, regardless of team assignments. Team-based project visibility only applies to users with the **Member** role.</Info>

## Set a default team

If you enable the **Auto-add to new projects** permission on a team, that team will automatically be assigned to any new project created in the organization. This is useful for teams that should always have access to everything — like a project leads team.

## Delete a team

To delete a team:

1. Open the team settings
2. Click **Delete Team**
3. Confirm the deletion

Members will lose the permissions that team granted, but they remain in the organization and keep permissions from any other teams they belong to.

<Warning>Deleting a team is immediate. Members of that team may lose access to projects and merge permissions. Check what other teams members belong to before deleting.</Warning>

## How permissions work together

Here's a complete picture of how roles, teams, and permissions interact:

1. **Role** determines baseline access (Owner/Admin see everything; Member access is team-dependent)
2. **Team membership** determines which projects a Member can see
3. **Team permissions** determine what actions a Member can take (merge, create projects)
4. **Multiple teams** combine — a member gets the union of all their teams' permissions

<Tip>If a member can't see a project or can't find the merge button, check their team assignments. They might need to be added to a team that has access to that project or has the appropriate merge permission enabled.</Tip>