Skip to main content
Both modes create the same underlying objects — Workstream, Doc Store, Data Store, Agent, Space. The only difference is how many decisions you make yourself versus accept as sensible defaults.

​
Quick setup (3 steps)

Goal-first, with defaults applied automatically. Best for getting a finance user live fast, or for standard processes.
  1. Pick what you need done — choose a task template; it sets the agent, instructions, and skills.
  2. Add the client and its files — name the client, add or connect files, invite people.
  3. Review and go live — preview the output, choose a cadence, publish.
What’s decided for you: the Data Store scope (workstream-based), the skill selection (from the template), and the access defaults (owner + invited people).

​
Advanced setup

Every primitive is explicit. Best when you need precise control — custom schemas, specific skills, tight access.

​
How they relate

  • Same objects. Quick provisions exactly what Advanced builds explicitly — it just applies defaults instead of asking.
  • No dead-ends, both directions. You can start in Quick and switch to Advanced to fine-tune; work already entered carries over. Switching back keeps the advanced settings underneath.
  • Defaults are visible in Advanced. Anything Quick decided for you can be seen and changed in Advanced.

​
What Quick decides, and where to change it

​
Next steps

  1. Builder overview
  2. Create a Workstream
  3. Creating an agent