# Gitsu Team Seats: buy, reserve, and manage access

> **TL;DR** A Gitsu Team is a billing group with two or more paid Seats. The buyer chooses the Seat count in Checkout, always holds one Seat, and reserves other Seats for GitHub logins. The reserved person claims a Seat when that GitHub Identity signs in to Gitsu. Adding a new Seat charges the difference for the rest of the billing period after payment succeeds. Removing a holder ends paid access immediately, while a subscription ending follows its access-end and grace-period rules. A Gitsu Team is not a GitHub organization.

A Gitsu Team is a Gitsu billing group with two or more paid Seats. The buyer chooses the Seat count in Checkout, keeps one Seat for their own GitHub account, and can reserve the remaining Seats for specific GitHub logins. The [pricing page](/pricing) shows the current catalog; this page explains what happens after you choose Team.

## What is a Gitsu Team?

A Gitsu Team is a billing group administered by one Gitsu Account, the buyer. Every subscription belongs to a Team. Pro is a Team with one Seat, held by the buyer. Once the subscription has two or more Seats, Gitsu labels it Team and shows the buyer its Seat list in Billing.

The Team owns the subscription and the Seats, but it does not own your GitHub work. A Seat grants the holder the paid Gitsu capabilities covered by that subscription. GitHub still controls access to repositories, issues and Projects. The buyer's Gitsu Account remains an individual account linked to one GitHub Identity.

That distinction matters when you decide who can use a Seat. A Team does not create a GitHub organization, add anyone to one, or change repository permissions. Gitsu uses GitHub identities to decide who holds paid access, while GitHub permissions continue to decide what that person can reach on GitHub.

## How do I buy Team?

Choose Team on Gitsu's pricing screen, set a Seat count, choose a billing interval, and continue to Stripe Checkout.

1. Sign in with GitHub. Checkout is tied to the signed-in Gitsu Account and its GitHub Identity.
2. Select Team in the pricing cards. The Seat stepper starts at two Seats, and Checkout accepts a whole-number Team count from two through twenty.
3. Choose the monthly or yearly billing interval and the number of Seats you want to buy now. The pricing screen calculates the total from the catalog, so the [pricing page](/pricing) is the place to check the current amount.
4. Choose the Team subscription action and complete the hosted Stripe Checkout. After payment, the buyer holds one Seat and the remaining Seats are open.

The buyer always holds one Seat. Gitsu does not support a buyer who pays for a Team without using Gitsu themselves. If the account already has a current Gitsu subscription, another Checkout is refused and the app directs the account to manage the existing subscription instead of creating a second one.

## How do I reserve a Seat for a teammate?

Reserve a Seat from Billing by choosing a GitHub login for the person who should receive it. Gitsu can show GitHub users who can write to repositories on the selected Project, and the buyer can search GitHub by username when the person is not in that list.

The reservation stores the person's numeric GitHub user ID and their login for display. The ID is the important part because a GitHub login can be renamed. Gitsu does not need the teammate's email address to decide who owns the Seat.

The reservation uses an open Seat first. If the Team has no open Seat, the reservation adds a Seat to the subscription. Gitsu charges the difference for the rest of the current billing period and adds the Seat only if that payment succeeds. A failed payment leaves the Team unchanged.

A reservation lasts one day. Gitsu calculates expiry when it reads the Seat, so an expired reservation becomes open again without waiting for a background job. The buyer can reserve that open Seat again.

## How does a GitHub login claim its Seat?

The reserved person claims the Seat by signing in to Gitsu with the GitHub login the buyer selected. The claim is matched by numeric GitHub user ID, and a successful sign-in changes the Seat from reserved to held.

The buyer can copy a link or email it to the reserved person, but the link only opens the accept page. The sign-in identity decides whether the Seat is claimed. If the reserved login signs in before opening the link, Gitsu claims the Seat during the billing read. The accept page has no extra confirmation step for the matching account.

The link does not let somebody else take the Seat. A person signed in as a different GitHub account is told which login the Seat is reserved for and can switch accounts. A forwarded link therefore does not move paid access to the wrong person. If the reservation expires, is cancelled, or the Team ends, the old link no longer claims anything.

After the claim, the holder sees that they are covered by the buyer's Team in Billing. The holder gets the paid capabilities included with that Seat, while the buyer remains responsible for the subscription and Seat changes.

## How do adding and removing Seats affect charges?

Adding a Seat charges the difference immediately for the rest of the current billing period; removing an open Seat lowers the quantity without issuing a credit for time already paid.

- Reserving an open Seat uses capacity the Team already pays for, so it adds no charge.
- Reserving a Seat when none is open increases the subscription quantity. Gitsu asks Stripe to invoice the difference now and keeps the new quantity only after payment succeeds. A card decline leaves the Team at its previous quantity.
- Removing a held Seat holder ends that person's access immediately, but the Seat stays open and paid. The bill does not go down from that removal alone, so the buyer can give the Seat to someone else.
- Removing an open Seat reduces the subscription quantity with no credit for the rest of the current period. The lower quantity applies to later renewals.

The buyer cannot remove their own Seat. To move a Team back to Pro, first make sure only the buyer's Seat remains and remove the open Seats. That is a quantity change, not a transfer to a different GitHub account.

## Can I move from Pro to Team later?

Yes. Pro is the one-Seat form of the same Team model, so a Pro buyer can grow into Team without moving accounts or creating a second subscription.

There are two routes:

1. Select Team on the pricing screen, choose at least two Seats, and complete Checkout if the account does not already have a current subscription.
2. Open Billing on an existing Pro subscription and reserve a Seat for a GitHub login. If the buyer has no open Seat, Gitsu adds the second Seat and charges the difference for the rest of the period after payment succeeds.

In both cases the buyer keeps their own Seat. The other Seat starts open or becomes reserved for the selected GitHub login. The Team does not need a GitHub organization, and the buyer's existing Gitsu Account remains the account that administers billing.

## What happens when a Seat is removed or a subscription ends?

Removing a held Seat ends that holder's paid access immediately, while ending the subscription follows Gitsu's lifecycle policy for every Seat on that Team.

If the buyer schedules cancellation, all current holders remain entitled until the subscription's Access End Date. If payment becomes past due, access continues during the seven-day grace window while the buyer updates the payment method. A terminal or ended subscription is no longer entitled. A person who holds a Seat on another entitled Team can still use the best entitlement available from those Teams; a removed Seat itself grants nothing.

When a Team ends, a pending reservation cannot be claimed. The former holder can still use the free Web App, and the underlying GitHub Projects, issues and fields remain in GitHub. The subscription controls paid Gitsu access; it does not transfer, delete or lock the GitHub data that Gitsu reads and writes.

## Where do I manage a Team?

The buyer manages the subscription and its Seats from Gitsu Settings, under Billing. The Team view shows the buyer's held Seat, other held Seats, reservations and open capacity. From there the buyer can reserve a login, copy or email a link, resend a reservation, cancel a reservation, remove a holder, or remove an open Seat.

Stripe's Customer Portal remains the place for the card, invoices, billing interval and cancellation. Seat quantity changes stay in Gitsu so the Seat records and the Stripe quantity move together. If you are setting up Gitsu for the first time, start with the [Web App sign-in and Project import guide](/docs/getting-started), then return to Billing when you are ready to buy or manage Seats.

## Frequently asked questions

### What is a Gitsu Team?

A Gitsu Team is a Gitsu billing group administered by one buyer account. It owns one subscription and its paid Seats. Pro is the same model with one Seat; Team is the label used when the subscription has two or more Seats. A Gitsu Team is not a GitHub organization.

### How does someone claim a Gitsu Team Seat?

The buyer reserves the Seat for a GitHub login. The teammate claims it by signing in to Gitsu with that same GitHub account. Gitsu matches the immutable numeric GitHub identity, so a forwarded link or a different signed-in login cannot claim the reservation.

### Does adding or removing a Seat change the bill?

Reserving an open Seat does not add a charge. If no open Seat exists, Gitsu adds one and charges the difference for the rest of the billing period only after the payment succeeds. Removing a holder ends access but leaves the paid Seat open; removing an open Seat lowers the subscription quantity without a credit for the period already paid.

### Can I upgrade Pro to Team?

Yes. Pro is a Team of one, so you can choose Team in the pricing screen and Checkout with at least two Seats, or reserve another Seat from Billing. The buyer keeps one Seat at every Team size.

### What happens after a Seat is removed or a subscription ends?

A removed Seat holder loses paid Gitsu access immediately. A scheduled subscription cancellation keeps access until its Access End Date, and a past-due subscription keeps access during the seven-day grace window. After the subscription is no longer entitled, paid features stop; the GitHub projects and issues remain in GitHub, and the free Web App remains available.