Organizations and Teams
This document explains how organizations and teams work in Codity and how to manage access across multiple organizations.
Organizations in Codity
An organization in Codity corresponds to:
- GitHub: GitHub organizations
- GitLab: GitLab groups (or personal projects)
- Azure DevOps: Azure DevOps organizations
Organization Structure
GitHub
Organization
└── Repository
└── Pull Requests
- Organizations contain repositories
- You can be a member of multiple organizations
- Each organization can have different permissions
GitLab
Group (Organization)
└── Project
└── Repository
└── Merge Requests
- Groups contain projects
- Projects contain repositories
- You can be a member of multiple groups
- Personal projects are treated as a separate "organization"
Azure DevOps
Organization
└── Project
└── Repository
└── Pull Requests
- Organizations contain projects
- Projects contain repositories
- You can be a member of multiple organizations
- Each organization requires separate authentication
Switching Between Organizations
In the Codity dashboard, you can:
- Select organization: Use the organization dropdown to switch
- View organization repositories: See all repositories in the selected organization
- View organization metrics: See aggregated metrics for the organization
- Manage organization settings: Configure organization-level settings
Multi-Organization Access
How It Works
- Separate authentication: Each organization may require separate authentication
- Unified dashboard: View all organizations in one dashboard
- Organization switching: Switch between organizations easily
- Isolated data: Data is isolated per organization
Managing Multiple Organizations
- Sign in to each: You may need to authenticate with each organization separately
- Configure tokens: Each organization may need its own token (for GitLab/Azure)
- Switch in dashboard: Use the organization selector to switch
- Aggregate views: View metrics across all organizations
Team Access
Team Membership
Team access in Codity inherits from your version control system:
- GitHub: Team membership determines repository access
- GitLab: Group membership determines project access
- Azure DevOps: Team membership determines project access
What Teams Can Access
- Repositories: Access to repositories based on team membership
- Metrics: View metrics for accessible repositories
- Reviews: See review comments in accessible repositories
- Settings: Configure settings for repositories you have admin access to
Organization-Level Settings
Available Settings
- Default review instructions: Organization-wide default instructions
- Token configuration: Organization-level tokens (GitLab/Azure)
- Repository defaults: Default settings for new repositories
Who Can Configure
- Organization admins: Can configure organization-level settings
- Repository admins: Can override organization defaults for their repositories
Best Practices
For Organization Admins
- Configure defaults: Set organization-wide defaults for consistency
- Manage tokens: Configure and rotate organization-level tokens
- Monitor access: Review who has access to what
- Document settings: Keep track of organization-level configurations
For Users
- Understand structure: Know which organization a repository belongs to
- Switch as needed: Switch between organizations to access different repositories
- Request access: Request access in the version control system if needed
Common Scenarios
Scenario: Multiple GitHub Organizations
Setup:
- Install Codity GitHub App on each organization
- Select repositories in each organization
- Switch between organizations in dashboard
Usage:
- View repositories from all organizations
- Switch organization to see different repositories
- Metrics are aggregated per organization
Scenario: GitLab Groups and Personal Projects
Setup:
- Sign in with GitLab OAuth
- Configure Personal Access Token
- Enable repositories from groups and personal projects
Usage:
- View repositories from all groups/projects
- Switch between groups in dashboard
- Personal projects appear as separate "organization"
Scenario: Multiple Azure DevOps Organizations
Setup:
- Sign in with Azure DevOps OAuth for each organization
- Configure Personal Access Token for each organization
- Enable repositories from each organization
Usage:
- View repositories from all organizations
- Switch between organizations in dashboard
- Each organization requires separate token
Troubleshooting
"Organization Not Found"
Symptoms:
- Organization doesn't appear in dropdown
- Cannot access organization repositories
Causes:
- Not a member of organization
- Organization not connected to Codity
- Authentication issue
How to Fix:
- Verify organization membership in version control system
- Check if organization is connected to Codity
- Re-authenticate if needed
"Cannot Switch Organizations"
Symptoms:
- Organization dropdown is empty
- Cannot access other organizations
Causes:
- Only member of one organization
- Authentication issue
- Token doesn't have organization access
How to Fix:
- Verify you're a member of multiple organizations
- Check authentication status
- Verify token permissions