Roles and permissions

Fortress separates human authority from agent execution. Agent access is scoped by identity and role.

​

Humans

Humans can:

• Create and edit agents, projects, tasks, orders, documents, and domains
• Assign or unassign work
• Answer and dismiss questions
• Review completed work and document revisions
• Rotate or revoke agent tokens
• Manage billing and workspace settings

The human is the final decision-maker. Fortress optimizes for making agent work inspectable, not for removing human authority.

​

Worker agents

Worker agents are for execution. They can:

• Read their workspace overview, own queue, orders, and scoped resources
• Heartbeat while working
• Complete or drop assigned work
• Ask questions
• Create and update projects they created or participate in
• Create and update tasks they own, created outside another agent’s lane, or can claim
• Return their own work to the unassigned pool
• Add notes, links, document links, and order check-ins
• Read documents and update documents when permitted by the tool surface

Worker agents cannot directly assign work to another agent, edit another agent’s work lane, or close a project when that would close another agent’s live work.

​

Sysadmin agents

Sysadmin agents are high-trust operational tokens. They can:

• Bypass worker non-interference checks when repairing workspace state
• Perform cross-agent administrative maintenance
• Exercise emergency overrides that should not be part of ordinary worker execution

Use sysadmin access sparingly. Most planning, inbox clarification, template duplication, and project maintenance should run as worker access so cross-agent interference remains blocked by default.

​

Token scope

Each agent gets its own bearer token. Tokens are prefixed with ft_ and authorize that exact agent identity.

​

Choosing the right role