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

# Members & Seats

> Manage team members and seat assignments for your organization

export const ThemeImage = ({src, alt}) => {
  let lightSrc, darkSrc;
  if (src.includes("-light.")) {
    lightSrc = src;
    darkSrc = src.replace("-light.", "-dark.");
  } else if (src.includes("-dark.")) {
    darkSrc = src;
    lightSrc = src.replace("-dark.", "-light.");
  } else {
    lightSrc = src;
    darkSrc = src;
  }
  return <span>
      <img className="block dark:hidden rounded-lg border" src={lightSrc} alt={alt} />
      <img className="hidden dark:block rounded-lg border" src={darkSrc} alt={alt} />
    </span>;
};

## Overview

Organization admins can manage team members and control who has access to Gitar features through seat assignments. The members page provides a centralized view of everyone in your organization, their roles, and their seat status.

## Inviting Members

Gitar syncs members directly from your connected code hosting platform -- no manual invites are needed.

* **GitHub**: All organization members are automatically synced. Outside collaborators also appear and are marked with a "Collaborator" badge.
* **GitLab**: All group members are automatically synced.

Once you connect your code host, members appear in your Gitar organization automatically.

## Seat Management

<Note>Seat management applies to the **Core** and **Pro** plans. Enterprise plans include unlimited seats.</Note>

Seats control which users get Gitar's automatic features on their PRs. Admins assign seats from the organization settings page at [app.gitar.ai](https://app.gitar.ai).

### With a Seat

Users with an assigned seat get full access to Gitar's automatic capabilities, including:

* Automatic code review on their PRs
* CI failure analysis
* All other features included in their plan

### Without a Seat

Users without a seat can still open PRs, but Gitar will not process them automatically. They will see a message asking an admin to assign them a seat.

### Seat Tiers

The seats page groups users into three tiers:

1. **Seated** -- Users who currently have a seat assigned and receive full Gitar features.
2. **Active without a seat** -- Users who are actively contributing but do not have a seat assigned.
3. **Inactive** -- Users who have not had recent activity.

### Trial Period

During a trial, seat limits are not enforced. All members get full access to Gitar features regardless of seat assignment.

## Roles and Permissions

| Role       | Description                                                                    |
| ---------- | ------------------------------------------------------------------------------ |
| **Admin**  | Can manage seats, configure settings, manage billing, and set up integrations. |
| **Member** | Can use Gitar features on their PRs when assigned a seat.                      |

## Billing Context

How seats relate to billing depends on your plan:

* **Free plan**: PR summaries on unlimited repos. No seat management.
* **Core and Pro plans**: Usage is allocated per seat on a monthly billing cycle. You are billed based on the number of seats assigned.
* **Enterprise plan**: Unlimited usage with no seat limits.

For full details on pricing and plan features, see [Plans & Billing](/account-billing/plans).

## Troubleshooting

<AccordionGroup>
  <Accordion title="A team member doesn't appear in the members list">
    Members are synced from your connected code hosting platform. Ensure the person is a member of your GitHub organization or GitLab group. Once they have been added there, they will appear in Gitar automatically.
  </Accordion>

  <Accordion title="Gitar says a user doesn't have a seat">
    An admin needs to assign them a seat from the organization settings page. Navigate to your organization settings at [app.gitar.ai](https://app.gitar.ai) and assign a seat to the user. During a trial period, seat limits are not enforced, so this message should not appear.
  </Accordion>
</AccordionGroup>