Seats, keys, and devices

Your access to SQUAT rests on your seat, which activates with your account sign-in when you buy a plan. A license key is an optional extra credential for connections that can’t use your sign-in. Both live on the Seats page of your account.

Every plan includes seats. The Seats page shows each seat, its role, and whether a key is attached. Seats and keys can carry a friendly name — “CI key”, “Dana’s laptop” — set it or rename it anytime, so two keys are never just two prefixes.

Signing in with your account covers everyday use. Attach a key to your seat only when a tool has to connect without your sign-in session — a CI pipeline, a scheduled agent, or a client that only takes keys. The complete key (it starts with sqk_) is shown exactly once, at attach time; copy it somewhere safe right then. Afterwards the page shows only its prefix and status.

From the Seats page you can rotate a key (revoke it and attach a replacement in one move — expect a brief outage for that key’s connections while you update them) or simply revoke it. Revoking a key never touches the seat: your sign-in access, your teammate’s access, and your workspace data are all unchanged. Only connections made with that key stop working.

Each key works on up to three active devices, and a device pack adds three more. The Devices page lists them — rename one, or de-register it to free the slot immediately. Connecting by URL with a browser sign-in counts one device per sign-in, and reconnecting from the same place doesn’t use up new slots. A team repository set up for CI counts as one shared device for the whole team.

Add a seat by your teammate’s account email on the Seats page and pick a role — owner, admin, runner, or viewer; least privilege pays off. They sign in with their own account, no key required. Full detail on roles, support access, and the audit trail is in the manual’s Roles & security page.