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

# Organizations & Teams

> Manage your Greptile organization: navigate the org/team hierarchy, invite members, assign roles, sync settings, and configure team-level access.

Greptile has **organizations** (your workspace) and **teams** (each GitHub org or GitLab group you connect).

## One org vs. multiple

**One connected org or group** — most workspaces look like this. The top-left breadcrumb shows your workspace name only. Use **Organization Settings** for members, billing, and providers. There is no **Team Settings** tab.

**Two or more connected orgs or groups** — the breadcrumb shows `Workspace / team-name`. Pick a team from the dropdown to switch context. **Team Settings** appears for team-specific member access.

<Frame>
  <img src="https://mintcdn.com/greptile/kTEOEt_jfh6iINFC/images/workspace-dropdown.png?fit=max&auto=format&n=kTEOEt_jfh6iINFC&q=85&s=9db1cba09a640fa35a15337719dd50a2" alt="Workspace dropdown showing org and team hierarchy" width="2940" height="1430" data-path="images/workspace-dropdown.png" />

  <figcaption>Breadcrumb with multiple teams connected</figcaption>
</Frame>

<Note>
  Steps below that mention **Team Settings** only apply when you have multiple teams connected. Otherwise, use **Organization Settings**.
</Note>

## Roles

### Organization roles

Set under **Organization Settings → People**.

* **Admin** — Billing, members, code providers, integrations, and organization-wide review settings.
* **Member** — Day-to-day use: analytics, repos, pull requests, and custom context. Cannot change billing, providers, or org-wide settings.

At least one admin must remain. The last admin cannot be removed until another is promoted.

### Team roles

Only relevant with multiple teams connected. Set under **Team Settings → People**.

* **Admin** — Manage members for that team. Cannot edit **Code Review Settings** (organization admins only).
* **Member** — View team repos, pull requests, and custom context; enable or disable repos for that team.

Organization admins always have full access to every team.

## Adding members

<Steps>
  <Step title="Go to Organization Settings">
    Open **Organization Settings → People**.
  </Step>

  <Step title="Invite members">
    Click **Send Invite** or **Invite Link**.

    <Frame>
      <img src="https://mintcdn.com/greptile/kTEOEt_jfh6iINFC/images/org-settings-people.png?fit=max&auto=format&n=kTEOEt_jfh6iINFC&q=85&s=fb12b4cdad48c16b9ac21bc0cfc74d6d" alt="Organization people management" width="2940" height="1430" data-path="images/org-settings-people.png" />

      <figcaption>Manage organization members</figcaption>
    </Frame>
  </Step>

  <Step title="Assign roles">
    Choose **Admin** or **Member**.
  </Step>
</Steps>

To limit someone to a specific GitHub org or GitLab group, select that team in the breadcrumb, then open **Team Settings → People**.

<Frame>
  <img src="https://mintcdn.com/greptile/kTEOEt_jfh6iINFC/images/team-settings-people.png?fit=max&auto=format&n=kTEOEt_jfh6iINFC&q=85&s=796eda3d01a8fffd3bdd8fa608d50b03" alt="Team people management" width="2940" height="1430" data-path="images/team-settings-people.png" />

  <figcaption>Team member access (multiple teams only)</figcaption>
</Frame>

## Managing repositories

Open **Repositories** and click **Manage Repos** to enable or disable repos.

<Frame>
  <img src="https://mintcdn.com/greptile/kTEOEt_jfh6iINFC/images/manage-repos.png?fit=max&auto=format&n=kTEOEt_jfh6iINFC&q=85&s=27bac108ca8a70ef0656f8ef8a79b3f1" alt="Manage repositories dialog" width="2940" height="1430" data-path="images/manage-repos.png" />

  <figcaption>Enable or disable repositories</figcaption>
</Frame>

* **Enabled** — select repos and click **Disable Repos** or **Disable All**
* **Disabled** — select repos and click **Enable Repos** or **Enable All**

Organization admins can manage repos across the whole workspace. With multiple teams, team members can also manage repos for their team.

### Auto-enable new repositories

1. Go to **Code Review Settings**
2. Scroll to **Auto-enable New Repos**
3. Toggle on

Only organization admins can change this.

<Frame>
  <img src="https://mintcdn.com/greptile/K9D4AfJzUy9sOdP6/images/auto-enable-and-sync.png?fit=max&auto=format&n=K9D4AfJzUy9sOdP6&q=85&s=b15c874aa98be485b80248aff6fbeb1b" alt="Auto-enable and sync settings" width="2940" height="1430" data-path="images/auto-enable-and-sync.png" />

  <figcaption>Auto-enable new repos and sync settings</figcaption>
</Frame>

## Syncing settings across teams

With multiple teams, each team can inherit review settings from the organization. On a team's **Code Review Settings** page, use **Inheritance & Sync**:

* **Sync from Parent** — match organization defaults
* **Sync Now** — sync immediately (disabled when already in sync)

Organization-level custom context rules also appear on team **Custom Context** pages as inherited.

## Onboarding for invited members

New members land in the org dashboard and are guided through **Personal Settings → Review Settings**:

1. Link GitHub or GitLab profile
2. Install the bridge app
3. Choose coding agents for Fix with your Agent

Members can also set personal preferences for summaries, diagrams, collapsible sections, and comments outside the diff.

<Note>
  **Members** do not see **Code Providers** or **Integrations** — admins only.
</Note>

## Code providers

Admins connect GitHub or GitLab under **Code Providers**. Click **Add Provider** to connect more orgs or groups.

<Frame>
  <img src="https://mintcdn.com/greptile/8PzYIxBdzrtuAyXk/images/code-providers.png?fit=max&auto=format&n=8PzYIxBdzrtuAyXk&q=85&s=a2063769204adea7e190186ec1ed41b8" alt="Code providers page" width="2280" height="1408" data-path="images/code-providers.png" />

  <figcaption>Connected code providers</figcaption>
</Frame>

<Tip>
  If a GitHub organization does not appear when you add a provider, see [GitHub organization not listed](/troubleshooting/common-issues#github-organization-not-listed).
</Tip>

## What's next?

* [Configure review settings](/code-review/controlling-nitpickiness)
* [Add custom standards](/code-review/custom-standards)
* [View analytics](/analytics)