Workspaces and roles
A workspace is one operator's fleet. Everyone in it has a role and a level per module.
Workspace
A workspace holds one operator's fleet: its vessels, sensor data, alerts, reports, policies and people. Every row in the database carries a workspace id, and nobody reads across workspaces.
The demo workspace is Aurora Marine (aurora-marine).
Roles
Each person in a workspace has one role.
| Role | Who | Default level per module | Manage members | Billing |
|---|---|---|---|---|
| owner | Fleet manager | publish, always | yes | sees it; changes only through the store |
| admin | Technical superintendent | set per module, default edit | yes, except owners | sees it |
| member | Chief engineer, emissions officer, underwriter | set per module, default view | no | no |
| agent | AI agent such as Watchkeeper | set per agent, at most edit | no | no |
An owner always has publish on every module the workspace has. An agent can never have more than edit. The database enforces both, so a bad request cannot change them.
How access is worked out
What you can do in a module depends on three things:
- Your role (owner gets publish, agent is capped at edit).
- The level you were given for that module:
none,view,editorpublish. See Access levels. - The workspace's entitlement for that module:
locked,active,graceorread_only. See Entitlements.
Your effective level is the lowest of these. For example, a member with edit on Emissions gets only view while Emissions is read_only.