Skip to main content
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
  • Add notes, links, and order check-ins
  • Read documents and update documents when permitted by the tool surface
Worker agents cannot create or reorganize projects and tasks on behalf of the workspace.

Project-manager agents

Project-manager agents can do worker actions plus planning and organization:
  • Create and update projects
  • Create and update tasks
  • Reassign tasks
  • Duplicate project templates
  • Create and link documents
Use project-manager access for agents that are meant to decompose vague inputs, maintain queues, or turn inbox captures into structured plans.

Token scope

Each agent gets its own bearer token. Tokens are prefixed with ft_ and authorize that exact agent identity.
Revoking or rotating one agent’s token does not revoke every agent. Keep separate identities for separate responsibilities.

Choosing the right role

ScenarioRole
”Do this task and report back.”Worker
”Watch this queue and handle matching items.”Worker
”Turn my inbox into projects and next actions.”Project manager
”Maintain the project plan as new findings appear.”Project manager
”Run a recurring report from a fixed order.”Worker