Integrations
How integrations work
Scoped access, connected per workflow and revocable at any time.
4 min read
An integration gives Operator scoped access to one connected system so a workflow can read the context it needs. This guide explains how connections are granted, scoped and removed.
How a connection works
An integration gives Operator access to a specific system so it can read the context a workflow needs and prepare or perform the work you allowed.
Connections are made per workspace and are tied to the workflows that use them.
Why permissions are scoped
Broad access is easy to grant and hard to reason about later. Scoped access keeps the blast radius of any mistake small and keeps review meaningful.
Connect only what a workflow requires
Start with the systems in the lane you chose. Add another connection when a workflow actually needs it, not in advance.
Removing access
A connection can be disconnected. Once removed, Operator no longer has access to that system, and workflows depending on it stop until the connection is restored.
Key takeaway
Connect narrow, review the loop, then widen. Access you never granted cannot be misused.
Continue learning
Email and calendar
Connect the systems your day already runs on so Operator can prepare real work.
3 min read
Managing permissions
Decide what each connection is allowed to read and do.
3 min read
Set up your Operator
Create your workspace, connect the systems Operator needs and set sensible approval boundaries before you expand.
6 min read