Organizations & Teams

Greptile uses a two-level hierarchy: organizations at the top and teams underneath. Each connected GitHub org or GitLab group becomes a team within your Greptile organization.

​

Navigating the hierarchy

A breadcrumb in the sidebar shows your current context.

• Organization level: My Workspace — manages cross-team settings, billing, and integrations
• Team level: My Workspace / my-github-org — manages repositories, reviews, and team members for a single GitHub org or GitLab group

Click the breadcrumb to switch between your organization and its teams. The sidebar navigation changes depending on which level you’re viewing:

​

Teams

The Teams page (organization level) lists every connected GitHub org and GitLab group. Each team card shows:

• Team name and parent organization
• Code provider (GitHub or GitLab)
• Number of repositories
• Reviews today

Click a team to view its repositories, pull requests, and settings.

​

Adding team members

​

Organization level

​

Team level

Navigate to a team, then click Team Settings > People to manage members at the team level.

​

Managing repositories

From a team view, click Manage Repos to enable or disable repositories.

• Enabled tab: Shows active repositories. Select and click Disable Repos or Disable All.
• Disabled tab: Shows inactive repositories. Select and click Enable Repos or Enable All.

​

Auto-enable new repositories

Greptile can automatically enable reviews on new repositories as they are created in a GitHub org or GitLab group.

1. Go to Code Review Settings in the sidebar
2. Scroll to Auto-enable New Repos
3. Toggle the switch to enable

This setting is available at both the organization and team levels.

​

Syncing settings across teams

Team-level Code Review Settings can inherit from the parent organization. The Inheritance & Sync section (team level only) lets you sync a team’s review configuration to match its parent.

• Sync from Parent — reverts the team’s settings to match the organization defaults
• Sync Now — triggers an immediate sync (disabled when the team already matches)
• Custom context inheritance — rules set at the organization level appear automatically in the team’s Custom Context page, labeled “Inherited from (org name)“

​

Onboarding for invited members

When a new user accepts an invitation and joins an existing organization, they land directly in the org dashboard as a Member. A guided setup in Personal Settings > Review Settings walks them through connecting to GitHub/GitLab:

1. Link your GitHub or GitLab profile — connects their code provider account so Greptile can identify their PRs
2. Install the bridge app — installs the CLI that routes fix requests from GitHub to their local coding agent
3. Choose your coding agents — selects which agents (Claude Code, Cursor, Codex, Devin) appear on Fix in X buttons

A banner at the top of the page prompts the user to connect their account before review preferences take effect. Members can also customize their personal review preferences:

• Summary, issues table, and diagram visibility
• Collapsible sections and default-open behavior
• Comments outside the diff

​

Code providers

The Code Providers page (organization level) shows your connected accounts. For each provider you can see:

• Provider type (GitHub or GitLab)
• Last sync timestamp
• Number of teams and repositories

Click Add Provider to connect additional GitHub or GitLab accounts.

​

What’s next?

• Configure review settings at the organization or team level
• Add custom standards that apply across teams
• View analytics for review activity and team metrics