Integrations
Files and documents
Give Operator the context stored in your documents.
3 min read
Give Operator the context stored in your documents. A connection is only useful in service of a workflow, so decide what you want Operator to carry first, then grant the access that motion needs.
What Operator can use it for
Access is granted per workspace and tied to the workflows that use it. With this connection in place, Operator can:
- use documents as context when preparing work
- attach the right supporting file to a handoff
- summarise a document for a decision
Common workflows
- finance handoffs
- meeting follow-up
- customer health reviews
What context is relevant
- the folders or documents you connect for a workflow
Permissions and access
Access is scoped to the workflow you enabled and can be revoked at any time. Connect the narrowest access that lets the workflow work, not the broadest access the tool offers.
Good to know
Exact permission names differ per provider. Grant only the access the workflow requires and review it periodically.
Where approval happens
- sharing a document outside the company
- deleting or overwriting a file
Human checkpoint
If an action would be awkward to undo, keep it behind an approval.
Disconnecting access
A connection can be removed at any time. Once removed, Operator no longer has access to that system and the workflows depending on it stop until the connection is restored.
The same connect, scope and revoke model applies to every system. How integrations work