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.
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? Agents → New agent opens the guided setup: describe the job or pick a preset, choose what it can use and what needs your sign-off, try it on an example, then publish. See Creating an agent.
3. Dry-run a version
Dry-run an agent first: it reasons for real against an example you give it, with every change and every connected app simulated, so you can see what it would do safely. The guided setup asks for a dry run of exactly what you are about to publish.
4. Publish, then run for real
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. Once it is published, run it for real.
- 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.
5. Review in the Approval Centre
Under the default human-approval policy, when 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.