Sample data · this company and its people are invented.
People
Each person makes their own key with a one-time code. Nobody else ever sees their key.
Key shown once — copy it now
"Your manager added you to TIER. Open /claim on this server and enter the code they gave you. You will get your own key; only you hold it."
Connect this laptop
Server address:
Put the key in a private file named key-file on your laptop, then run:
Supported tools and models (/supported)
After the first upload, People shows the last upload date and Keys shows Used yet? Used. Device keys belong to the same person.
Ask your TIER owner to map your Copilot or Cursor login. Usage from before the mapping never counts.
Unmapped vendor users
| Vendor | Vendor user ID / login | Suggested person | Actions |
|---|
| Vendor | Vendor user ID | Person | Status |
|---|
People
| Person | Group | Node manager | Card | Last data upload | Status | Keys and actions |
|---|
A new code can be issued only while the person has no key. Once someone has claimed their key, you can end it only by marking them as left.
Add person
Invite a manager
The node stays when its manager leaves. The parent invites a replacement. Keys bind to the node and never grant a wider branch.
New-person handoff
Creating a person does not count them toward the privacy floor.
Existing keys are Stored (not shown).
KeysHistory and retention
Mark as left revokes all personal, device and node keys and closes membership now. Work from their time here stays in team totals.
Erase personal data is a separate, top-level admin action that keeps name-free totals.
People and key audit
| When (UTC) | Action | By | Subject |
|---|