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

# Teams

> Manage teams, roles, and member access permissions in Blitzy

Blitzy uses role-based access control to manage team collaboration, permissions, and project sharing. The system includes three primary roles - Super Admin, Admin, and Member - each with distinct capabilities designed for enterprise environments.

<Note>
  **Jump to:** [Roles](#roles) | [Permissions](#permissions) | [Project Sharing](#project-sharing)
</Note>

## Roles

<Tabs>
  <Tab title="Super Admin">
    The highest level of administrative access within the organization.

    * **Full team visibility** - See and manage all teams across the enterprise
    * **Team lifecycle** - Create, modify, and delete teams
    * **Member management** - Add or remove members from any team
    * **Connection overrides** - Override individual user connections and settings
    * **Integration sharing** - Share integrations (GitHub, Azure DevOps, GitLab) organization-wide

    <Warning>
      At least one Super Admin must exist at all times. The first user added to a Blitzy enterprise account automatically becomes the Super Admin. If a Super Admin leaves the organization, they must transfer the role to another user first.
    </Warning>
  </Tab>

  <Tab title="Admin">
    Team-level administrative access within assigned teams.

    * **Member management** - Add or remove members within assigned teams
    * **Team settings** - Manage team-specific settings and configurations
    * **Integration sharing** - Share integrations with team members
    * **Project access** - Full project access within their team's scope
  </Tab>

  <Tab title="Member">
    Standard user role with project collaboration capabilities.

    * **Project participation** - Full access to team project features
    * **Project sharing** - Share projects with their teams
    * **Code generation** - Trigger code generation and other project actions
    * **Team settings** - Read-only view
  </Tab>
</Tabs>

<Tip>
  Maintain at least two Super Admins for redundancy. Assign Admin roles to department leads so they can manage their own teams.
</Tip>

## Permissions

| Operation              | Super Admin       | Admin               | Member            |
| ---------------------- | ----------------- | ------------------- | ----------------- |
| **Create** team        | Yes               | No                  | No                |
| **View** teams         | All teams         | Assigned teams only | Member teams only |
| **Manage** members     | All teams         | Assigned teams only | No                |
| **Delete** team        | Yes               | No                  | No                |
| **Share** projects     | Yes               | Yes                 | Yes               |
| **Share** integrations | Organization-wide | Team-level only     | No                |
| **Team settings**      | Full control      | Full control        | Read-only         |

## Project Sharing

All roles can share projects with teams. When a project is shared, all team members gain access. Manage project sharing through **Project Settings**.

<Warning>
  Project sharing is a **permanent, one-way operation**. Once shared with a team, a project becomes a team project and cannot be converted back. Test with non-critical projects first.
</Warning>

## Related Guides

<CardGroup cols={2}>
  <Card title="SSO Configuration" icon="key" href="/administration/sso">
    Enterprise Single Sign-On setup
  </Card>

  <Card title="Environments" icon="server" href="/administration/environments">
    Role-based access to environment configuration
  </Card>

  <Card title="Managing Integrations" icon="gear" href="/integrations/managing">
    Team-level integration configuration
  </Card>

  <Card title="Project Sharing" icon="share" href="/project-lifecycle/sharing">
    Project ownership transfer and sharing
  </Card>
</CardGroup>