Skip to main content
Gitar separates two things: organization members, the people with access to your Gitar dashboard, and seats, which control who Gitar reviews code for and what you’re billed for. They’re managed on different pages and don’t have to match.

​
Organization Members

Settings → Organization lists everyone with access to your Gitar dashboard, along with their role.

​
Inviting Members

Organization admins invite members by email from Settings → Organization. Invited members receive an email to join, and appear as Pending until they accept.

​
Roles and Permissions

Dashboard access and roles are unrelated to seats. An admin can have no seat, and a seated developer never needs dashboard access to have their PRs reviewed.

​
Seat Management

Seat management applies to Core and Pro. Enterprise plans include unlimited seats.
Seats control who can trigger features that require one, including through PRs, pushes, and comments. Admins assign seats from Settings → Billing. Unlike organization members, the seats list is pulled from your connected code hosting platform: it lists the members of your GitHub organization, GitLab group, Azure DevOps organization, or Bitbucket workspace, whether or not they’ve ever logged into Gitar. Admins can also add a user manually if your platform doesn’t expose a member list Gitar can read.

​
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 does not automatically review their changes or act on their commands. Gitar posts a notice when they open a PR and replies when they send a command. A seated teammate can still request work on the same PR. No seat is added and nothing is billed until an admin assigns one from Settings → Billing.

​
Seat Tiers

The seats page groups users into three groups:

​
Trial Period

During your trial, seat limits are not enforced. Every PR author is reviewed regardless of seat assignment, so you can see Gitar in action across your whole team before deciding how many seats to buy.

​
Billing Context

How seats relate to billing depends on your plan: For full details on pricing and plan features, see Plans & Billing.

​
Troubleshooting

Members are invite-only. An admin needs to invite them by email from Settings → Organization.
The seats page lists members of your connected GitHub organization, GitLab group, Azure DevOps organization, or Bitbucket workspace. Check that the person is a member there and, for Azure DevOps, that Gitar’s token has the Graph & Identity (Read) scope. If your platform doesn’t support a member list Gitar can read (for example, Azure DevOps Server), add the person manually from Settings → Billing.
An admin needs to assign them a seat from Settings → Billing. During a trial period, seat limits are not enforced, so this message should not appear.