Integrations

Permissions

How to think about integration scopes, approvals, and connected-account safety.

Permissions determine what a connected application allows PIILOT workflows to do. A workflow should only be connected to accounts and scopes that match the work it is expected to perform.

PIILOT records connector contracts and setup state so users can review which app, operation, required fields, output fields, authentication mode, and safety notes are associated with an automation.

Permission review checklist

Confirm the connected account is the correct workspace account, not a personal account by mistake.
Review the scopes requested by the connected application during authorization.
Use human approval gates for customer-facing, destructive, financial, legal, or irreversible actions.
Check required fields and variable mappings before a workflow is considered ready.
Revoke unused MCP clients and disconnect integrations that are no longer needed.

Approval-aware permission model

flowchart TD
  A[Connector action] --> B{Action risk}
  B -- Low --> C[Run with configured connection]
  B -- Medium --> D[Review setup and mappings]
  B -- High --> E[Approval gate]
  E --> F{Approved?}
  F -- Yes --> C
  F -- No --> G[Stop path]