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

# Teams

> Manage team members, roles, and security settings in Corridor.

A Team in Corridor represents an organization or group of users collaborating on projects. Teams are the core organizational unit—each team has its own projects, security policies, guardrails, and billing. Users can belong to multiple teams.

## Creating a team

1. Go to [app.corridor.dev](https://app.corridor.dev)
2. Click your avatar → **Create Team**
3. Enter a team name
4. Click **Create**

You become the owner of the new team.

## Team roles

| Role | Permissions |
| - | - |
| **Owner** | Full access—manage members, billing, integrations, and all team settings |
| **Admin** | Manage projects, guardrails, findings, and PR reviews. Cannot manage members or billing |
| **Standard User** | Use the Corridor IDE extension and Corridor Agent Steering, plus `askQuestion` / `getChatHistory` on their own chats. Cannot alter configurations or view team data |
| **Viewer** (beta, Enterprise) | Read-only access to projects, findings, and guardrails, plus the read-only MCP tools. Can run security-review chats with `askQuestion` and read back their own chats. Cannot change anything, view team dashboards, or read other members' chats |

### Role capabilities

| Action | Owner | Admin | Viewer | Standard User |
| - | :-: | :-: | :-: | :-: |
| Use IDE extension | ✓ | ✓ | | ✓ |
| Use Corridor Agent Steering | ✓ | ✓ | ✓ | ✓ |
| View team projects and findings | ✓ | ✓ | ✓ | |
| Read findings and guardrails through MCP tools | ✓ | ✓ | ✓ | |
| Ask questions in their own chats (`askQuestion` / `getChatHistory`) | ✓ | ✓ | ✓ | ✓ |
| Create & manage projects | ✓ | ✓ | | |
| Create & edit guardrails | ✓ | ✓ | | |
| Respond to findings | ✓ | ✓ | | |
| Manage integrations, packs & compliance policies | ✓ | | | |
| Invite & remove members | ✓ | | | |
| Manage billing | ✓ | | | |
| Delete team | ✓ | | | |

> [!NOTE]
>
> **Viewer** is in private beta for Enterprise teams. Ask your Corridor contact to enable it; it then appears in the
> role picker.

## Managing members

### Inviting members

1. Go to **Team Settings → Members**
2. Click **Invite Member**
3. Enter their email address
4. Select a role (Owner, Admin, or Standard User)
5. Click **Send Invite**

They'll receive an email invitation to join your team. See [Inviting Teammates](https://docs.corridor.dev/onboarding/adding-team-members.md) for the full onboarding process.

### Changing roles

1. Go to **Team Settings → Members**
2. Find the member
3. Click the role dropdown
4. Select the new role

### Removing members

1. Go to **Team Settings → Members**
2. Find the member
3. Click **Remove**
4. Confirm the action

> [!NOTE]
>
> Removing a member doesn't delete their Corridor account—they just lose access to your team.

## Shared guardrails and context

Teams can centrally manage security rules:

* Guardrails (including custom guardrails) can be applied across all team projects
* This ensures consistency—all developers on the team are held to the same security standards
* An admin can set a custom guardrail once (e.g., "disallow eval usage") and it will apply to all projects and be enforced for all team members

## Team visibility

Team plans provide full visibility into AI coding activity across the team. The dashboard shows aggregated data:

* How many suggestions were blocked
* How many PR issues each project has
* Patterns to identify (e.g., "Project X has a lot of API key exposure attempts")

Security engineers can use this to address trends via training or new guardrails.

## Collaboration

Within Corridor, team members can collaborate on addressing findings:

* If Corridor flags a vulnerability, a security engineer can use the Corridor UI or Chat feature to discuss it
* A developer can mark it as resolved once fixed
* The team context ensures everyone stays on the same page regarding security status

## Team settings

### General

* **Team name**: Display name for your team
* **Team URL**: Custom URL slug

### Guardrails

Configure which guardrails are active for your team:

* Enable/disable standard guardrails
* Create custom guardrails (Team and Enterprise)
* Upload documents for guardrail generation (Team and Enterprise)

### MCP Compliance

Set policies for which AI tools and MCP servers are allowed:

* **Allowlist**: Only permit specified MCP servers
* **Blocklist**: Block specific MCP servers
* **Disabled**: No restrictions

See [MCP Compliance](https://docs.corridor.dev/features/mcp-compliance.md) for details.

### Integrations

Connect external services:

* **GitHub**: Enable PR reviews and repository sync

## Subscription tiers

| Tier | Price | Projects | PR Reviews | Key Features |
| - | - | - | - | - |
| **Pro** | \$20/month | 5 | 100/month | PR reviews, Corridor Agent Steering, IDE extension |
| **Team** | \$40/dev/month | 20 | 100/dev/month | Custom guardrails, team visibility |
| **Enterprise** | Contact Sales | Unlimited | Unlimited | Chats, SSO, single-tenant |

### Managing subscription

1. Go to **Team Settings → Billing**
2. View current plan and usage
3. Click **Change Plan** to upgrade or downgrade

See [Billing](https://docs.corridor.dev/administration/billing.md) for details.

## Team analytics

View aggregate metrics across your team:

* **PR reviews**: How many PRs reviewed, findings discovered
* **Guardrail invocations**: Usage of real-time security analysis
* **Finding trends**: Open vs. closed findings over time
* **Remediation metrics**: Mean time to resolve issues

Access from **Team Settings → Analytics** or the Analytics tab.

## Transferring ownership

Transfer team ownership to another member:

1. Ensure the new owner has an admin role
2. Go to **Team Settings → General**
3. Click **Transfer Ownership**
4. Select the new owner
5. Confirm the transfer

> [!WARNING]
>
> This action cannot be undone. The new owner gains full control of the team.

## Deleting a team

> [!WARNING]
>
> Deleting a team permanently removes all projects, findings, and data.

1. Go to **Team Settings → General**
2. Scroll to **Danger Zone**
3. Click **Delete Team**
4. Type the team name to confirm
5. Click **Delete**

> [!NOTE]
>
> Only Team and Enterprise tiers support multiple users. If you are on an Individual plan, you won't see team management
> features.

## Next steps

> **[Projects](https://docs.corridor.dev/dashboard/projects)**
>
> Create and manage projects

> **[Billing](https://docs.corridor.dev/administration/billing.md)**
>
> Manage your subscription


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.