Members & roles

Access in svitrio is a membership on a project, refined by a role and optional per-member ACLs. Everything a member can see or do resolves to a permission check.

The permission catalogue

Permissions are fine-grained and name a resource and an action. A sample:

• content:read / content:write and the node-level node:read, node:write, node:publish, node:unpublish, node:archive, node:delete.

• member:read, member:invite, member:update, member:remove; template:*, snapshot:*, starter:*.

• Module permissions: ai:read/write, billing:read/write/delete, tickets:read/write, licenses:read/write, settings:read/write, audit:read.

Operator vs project

Project roles govern one tenant. The operator scope is granted explicitly per user (grant-operator / revoke-operator) and unlocks the fleet-wide surfaces.

Authentication

Humans sign in with passkeys or email magic-links. Programmatic access uses API keys — see the API section.