Teams and seats
Named seats
Section titled “Named seats”A Pro or Enterprise subscription is bought in named seats: a seat is assigned to a person, and it is reassignable — someone leaving does not lose you the seat.
Assignment happens from the account dashboard, reachable through the title bar’s Account ▸ Dashboard button.
| Role | Can |
|---|---|
| admin | Billing, seat management, member management |
| member | Use the plan’s capabilities |
Sharing a project
Section titled “Sharing a project”Restorm has no hosted workspace, and that is a choice: sharing goes through git.
A .restorm project is a text file, serialised deterministically so that diffs stay
readable and merges pair entities correctly. See
.restorm projects and files.
Practical consequences:
- your requests follow the same review cycle as your code: branch, pull request, review;
- the access rights are your forge’s — nothing to administer twice over;
- the API project’s history is the git history, with its
blames and its bisections.
The built-in git makes the operation comfortable from inside the application, conflict resolution in the genuine editors included.
What is not shared
Section titled “What is not shared”Deliberately, these items stay local to each person:
- favorites;
- the workbench layout;
- quick settings saved to the “user” target;
- the response history;
- secrets.
Everyone keeps their own work plan; the project remains the shared contract.
Secrets in a team
Section titled “Secrets in a team”Never write a secret into the project. Two approaches:
- locally, a secrets file next to the project, added to
.gitignore; - in CI, the “environment variable” source, fed by your pipeline’s vault.
See Secrets.