Aranisdocs
aranis.ai
Docs/Administration/Team and invitations

Team and invitations

Who takes a seat, who does not, and why the distinction is about who triggers the action.

Updated on August 18, 2026

Seats

Users in your organization take seats, and how many comes from the plan: 2 on Essencial, 5 on Profissional, unlimited on Enterprise. Each person invited to operate the platform consumes one.

Because a seat is billing, it always answers to your home organization — even while you are operating another organization's context through a workspace.

An invited collaborator takes no seat

Several platform flows take the work to whoever holds the information, instead of bringing the information to whoever holds the access: a supplier's respondent, whoever fills in a BIA, whoever describes a business process. They all get a link and contribute without creating an account.

None of them consumes a seat. The measure is who triggers the action, not who types: the invitation comes from someone in your organization, and that someone is already paid for. Charging a seat per guest would turn every discovery exercise into a budget decision and kill the mechanism itself.

Removing someone

Removing a user frees the seat immediately. What that person produced — assessments, documents, records — remains, because the organization's history is not the property of whoever typed it.