Skip to main content
No. Every output waits for a human to approve it. Publishing an agent starts preparation, not delivery.
No. Each client is an isolation boundary; people and agents only reach clients they’re scoped to. See Isolation and multi-tenancy.
A Workstream is a client (the isolation boundary). An Engagement is a process for that client (R&D, transfer pricing, close). One client can have several engagements. See Workstreams and Engagements.
Doc Store = files (documents). Data Store = structured tables. See Doc Stores and Data Stores.
No. End users work in finance terms (client, files, task). The platform terms (workstream, doc store, agent, space) are for builders. The Glossary maps them.
Skills grant capability, not access. Grant the agent access to the data separately. See Access scoping.
Quick for speed and standard processes; Advanced when you need explicit control. Same objects underneath. See Quick setup vs Advanced setup.
Yes — run a task on demand. See Running a task.
Set a notification rule (email, Slack, or Teams). See Notifications.
There are options for bring-your-own-key, open-weight / self-hosted models, and on-prem / residency deployments. Confirm what’s enabled for your plan. See Data handling and compliance.