Teams for a git TUI

g1tz shows you the repository. Teams show you who you work with: one organization, the roles a GitKraken team already knows, seats, teams, shared workspaces and an audit log. Signed in from the terminal with a code, never a pasted token.

npm i -g @profullstack/g1tz
g1tz login          # prints a code; approve it at /account
g1tz org create Acme
g1tz members invite bo@acme.test --role admin
g1tz teams create Platform
g1tz workspaces create Everything
g1tz                # press t for the Team screen

Roles

Role	Seat	Users	Teams	Billing	Insights	Transfer
Owner	yes	✓	✓	✓	✓	✓
Admin	yes	✓	✓	✓	✓
Lead	yes		✓		✓
User	yes
Billing Contact	no			✓

One owner per organization. Admins cannot change or remove the owner. The Lead role exists on plans with Insights.

What a plan unlocks

Plan	Seats	Unlocks
Community	1	Everything local: the repository, staging, Pulse. A personal organization.
Pro	up to 2	Invite people and assign roles; shared workspaces for the whole organization.
Advanced	up to 10	Teams, and workspaces only a team sees; one verified email domain that joins people on sign-in.
Business	up to 100	Any number of verified domains; Insights and the Lead role; audit log export.
Enterprise	unlimited	Custom contract and a support SLA.

The plan is an OpenAccess entitlement: buy it once for a principal and every app that honours the product hears about it. See plans.

Where the terminal fits

g1tz login asks the server for a code, prints it with a link, and waits. You approve it in a signed-in browser. The terminal receives a 90-day token and keeps it in ~/.config/g1tz/cloud.json, mode 600.
t in the TUI opens the Team screen: members with roles, teams, workspaces with their repositories, seats, and which features the plan unlocks.
Every change is a command: g1tz members, g1tz teams, g1tz workspaces, g1tz plan, g1tz audit. --json prints the server's answer.
The same operations run the account page, so nothing the browser can do is missing from the terminal.