Workspaces and roles

A workspace (an organisation in the API) is where a business lives on enios: its apps, its books, its people. Everything in it is kept strictly apart from every other workspace, down to the database. Your account gets a personal workspace when it is created; a business you start or join is another one, and you can be a member of several.

Roles

Each member holds one role in a workspace. The role fixes what the person may do; there are no per-feature switches to forget.

Role	May
Owner	Everything, including closing the workspace. A workspace always has at least one owner.
Admin	Everything an owner may, except closing the workspace.
Staff	See who is in the workspace and use the assistant on its data.
Accountant	See who is in the workspace, read the books and reports, and export data.

The permissions behind the roles, in the words the API uses:

Permission	Owner	Admin	Staff	Accountant
members.view see who is in the workspace	✓	✓	✓	✓
members.manage invite, change roles, remove	✓	✓
settings.manage settings and connections	✓	✓
billing.manage plan, payment method, invoices	✓	✓
books.view books and reports	✓	✓		✓
data.export export the workspace's data	✓	✓		✓
ai.use the assistant on the workspace's data	✓	✓	✓
org.delete close the workspace	✓

Managing members

Until the members page arrives in the interface, owners and admins manage members through the API at core.enios.one: /api/members lists them, /api/members/set adds a person or changes a role, and a DELETE on /api/members/<id> removes one. The last owner cannot be demoted or removed. Every change is written to the audit trail.