Many people. Many keys. One account.
Troops carve your account into shared spaces. Each one has its own members, its own site keys, its own permissions. A leaked credential stays contained to one troop. Seats meter collaboration without metering work.
Anatomy of a troop.
Unlimited multi-member troops, each holding its own site keys, members, and access tokens. Member access is per-troop, so a leak in one troop doesn't blow up the others. Every account also gets one personal troop, single-member, undeletable, that lives alongside.
Members · 4
| Member | Permissions | Scope |
|---|---|---|
alice@yourdomain.comLead · joined 3 months ago | CreateEditReadManage | Full |
bob@yourdomain.comEngineer · joined 6 weeks ago | CreateEditReadManage | Full |
consultant@contractor.ioContractor · invited 2 days ago | CreateEditReadManage | marketing only |
ci-deployTroop Access Token · last used 14 min ago | CreateEditReadManage | Full |
Site keys · 3
- marketing
- signup-flow
- checkout
Where it fits
Sub-teams that need their own integration surface: marketing, support, infra. Or staging vs prod environments where the same humans need different access boundaries.
Four permissions. Two scopes. No surprises.
The smallest permission set that lets you express the memberships you actually need. Each permission is independent. Scope decides which site keys the permissions apply to.
| Permission | What it lets the member do |
|---|---|
| Create | Mint new site keys inside the troop. |
| Edit | Change configuration on existing site keys. |
| Read | View site keys and their statistics, but change nothing. |
| Manage | Add and remove members, change their permissions and scope. |
Scope
On top of the four permissions, every membership has a scope: full troop access, or a list of specific site keys the member can touch. A contractor with Read on one site key sees one card; a lead with Manage on the whole troop sees everything.
Where it fits
A contractor that needs read-only on one site key. A junior dev that can edit but not delete. A lead with Manage but no Create. The set is small on purpose.
One pool. Counted once.
Seats are account-level. Users and access tokens both consume one each. Sharing the same identity across multiple troops in the same account costs nothing extra.
- aliceuser
- bobuser
- caroluser
- consultantuser
- devuser
- qauser
- openavailable
- openavailable
Sharing across troops is free. The same user added to two troops in this account still costs one seat. Personal-troop ownership is also free; only collaboration in custom troops draws from the pool.
The economics
Seats are how the platform meters collaboration. Cheap, predictable, and adjustable from the dashboard without picking up the phone.
Common questions
Sharing site keys with a team without sharing the keys themselves.
- What is a troop?
- A shared space inside your account with its own members, site keys, and permissions. A leaked credential stays contained to one troop instead of exposing the whole account.
- How do troop permissions work?
- Four independent permissions (create, edit, read, and manage) and two scopes (the whole troop, or a list of specific site keys). Granting one permission does not grant the rest.
- How are seats counted?
- One shared account-level pool. Each user and each Troop Access Token consumes one seat. The same person added to several troops in the same account still costs one seat, not several.
- Do I need to contact sales to add seats?
- No. Adjust the seat pool from the dashboard at any time. Add seats when you hire, remove them when contractors roll off.
- Does every account have a troop?
- Yes. Every account gets one personal troop (single-member and undeletable). Custom multi-member troops unlock on the Troop plan and above.
Pick the troop tier. Add your team.
Sign up free on Solo, upgrade to Troop from the dashboard when you need shared site keys. Self-serve seat purchase, no sales round-trip.
Start free