Teams

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
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 capabilities

​

Managing members

​

Inviting members

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

They’ll receive an email invitation to join your team. See Inviting Teammates 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

​

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 for details.

​

Integrations

Connect external services:

• GitHub: Enable PR reviews and repository sync

​

Subscription tiers

​

Managing subscription

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

See Billing 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

​

Deleting a team

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

​

Next steps