Workspaces, members and seats
How teams are organised, what each role can do, and how the seat limit counts.
Everything in Citerva belongs to a workspace — a team account with its own projects, its own plan and its own allowance. You can belong to as many as you are invited to.
A workspace is the unit that matters for billing and for limits: projects, scans per month and provider calls are all counted per workspace, never per person.
Roles
There are two.
| Role | Can |
|---|---|
| Owner | Everything, including billing, inviting and removing members, changing roles, and transferring ownership |
| Member | Everything to do with the measurement itself — create projects, approve prompts, run scans, read and triage recommendations |
A member cannot touch billing or membership. Nothing in the measurement side of the product is owner-only, because a workspace where only one person can approve a prompt set is a workspace where prompt sets do not get approved.
Inviting people
Members → Invite. Enter one or more email addresses and pick a role for each. An invitation is valid for a limited window and can be renewed or revoked from the same page.
Transferring ownership is separate from inviting, and is done from the same page.
Seats
Each plan includes a number of team members:
| Plan | Members |
|---|---|
| Pro | 5 |
| Growth | 20 |
Pending invitations count. An invitation you have sent but nobody has accepted is holding a seat, because the person it was sent to can take it at any moment. A five-seat workspace with two members and three unanswered invitations is full.
Two consequences worth knowing:
- If an invitation is refused because you are at the limit, the message tells you how many seats remain and what the limit is, so you can tell whether to upgrade or to free one up.
- Revoking an unanswered invitation frees its seat immediately. So does an invitation expiring — an email nobody ever opened does not hold a seat for ever.
Inviting several people at once is weighed as a batch: five invitations into a workspace with one seat left is refused as a whole rather than partly sent.
Leaving and removing
A member can leave a workspace, and an owner can remove one. Either way the workspace keeps everything: projects, scans and history belong to the workspace, not to the person who created them.
The owner cannot leave. Transfer ownership to another member first, or delete the workspace. An owner who left would leave it with nobody able to manage billing or membership — the projects and scans would still be there and nobody could administer them.