Getting started
Your first governed workforce
This guide takes you from first sign-in to a department of digital workers, with a first run reviewed through the approval gate — about fifteen minutes.
1. Create your organisation
Sign up at app.syftos.com. Your account creates an organisation (your tenant). Every agent, run, approval and audit record belongs to it, isolated from every other organisation. Invite teammates from Settings → Members; roles range from Viewer through Operator and Approver to Admin and Owner.
2. Deploy a department
The fastest start is a department: a ready-built team of digital workers, plus any pre-wired workflows, deployed in one step. From Departments, pick one (for example Inbound Sales or Research) and deploy it.
Everything arrives as drafts: draft agents and draft workflows in your workspace. Nothing is live until you review and publish it through the usual gate, so a deploy is always safe to explore.
Prefer to build your own? Create a single worker from a preset under Agents → New agent. Each is born sensible, governed and tool-suggested, ready for you to tailor its objective.
3. Publish a version
An agent's behaviour lives on its versions. Edit the draft (objective, instructions, model, tools), then publish. Publishing freezes that version permanently and makes it the configuration new runs use; in-flight runs pinned to a previous version are unaffected.
- A version needs an objective, instructions and at least one tool before it can publish.
- Choose a model your plan includes. Frontier models (e.g. the largest OpenAI and Anthropic models) require Growth and above.
4. Dry-run, then run for real
Dry-run an agent first: it executes against sample input with every side effect simulated, so you can see its reasoning safely. When you're happy, run it for real.
5. Review in the Approval Centre
This is the heart of SyftOS. The moment a run wants to do something with a side effect (send an email, create a task, move a deal, issue a refund) it pauses and creates an approval request in the Approval Centre. Nothing happens until a human with the right permission decides.
- Agents never hold the power to approve their own actions.
- Organisations can require that the person who proposed an action isn't the one who approves it (segregation of duties).
- A paused run waits as long as it needs to; approving it resumes it exactly where it left off.
6. Audit & trust
Every domain event is projected to an append-only audit log that is never edited and never deleted: a version published, a run completed, an action approved or rejected. Review it under Audit log, and watch each worker's track record build up under its trust score. This is what lets you delegate to digital workers with confidence: everything they do is gated and recorded.