Workforce & org hierarchy

Workforce lets you deploy agents from blueprints, see reporting hierarchy on an org chart, and let a chief propose new agents for approval. Enable with Workforce:Enabled. Blueprints that need events also need Automations; those that need schedules need Scheduled tasks — each catalogue card states its requirements.

Blueprints

Browse the blueprint catalogue (twelve built-in templates across communication, development, productivity, and business/ops packs).

1. Choose a blueprint that matches the outcome you want.
2. Fill required inputs (cron, connections, mailboxes, repos, …).
3. Install — the platform creates the underlying agent, grants, and triggers/schedules in one transaction.
4. Connect any missing apps, then activate related automations/tasks if they start paused.

Installed agents are ordinary AgentDefinition rows — edit them later in Agents like hand-built ones.

Org hierarchy & chief

• Agents can report to a parent agent and belong to an org unit (department).
• Ensure a project chief (Personal kind) when you want proposal/delegation flows.
• The chief can read the catalogue, watch the team, propose agents, and delegate to direct reports — proposals still need human approval before they go live.

Tips

• Prefer blueprints over assembling grants and triggers by hand for common jobs.
• Event-driven templates often start in ScopedAutonomous mode; grants remain the policy boundary.
• Revisit Connections if a blueprint lists apps you have not linked yet.