Members and permissions

The two instance roles

Role	Can do
Admin	Everything: create projects and users, register workers, change instance settings.
Member	Work in the projects they have been granted, and nothing else.

Project access

A member sees only the projects on their allowed list. Everything follows from that: the sidebar, global search, My tasks and every API response are filtered to what the account may see.

Under Settings → Users an administrator creates accounts — username, full name, password — and grants project access. A project can additionally name project administrators in its own General settings: full control of that project, no instance powers.

Tokens follow the same rules

An API token never grants more than its owner has. It can grant less: a scoped token is limited to chosen projects and behaves as a member inside them, with no administrative powers, whoever created it. The scope is enforced centrally, so it applies identically to REST and MCP.