TRUST & SECURITY
Security and governance
Identity, permissions, secrets, approvals and audit evidence.
Overview
Security is a design and operating responsibility. Exact controls vary by deployment, identity provider, integrations and configuration; verify the controls enabled in your environment before relying on them.
Identity and access
Use approved authentication and least-privilege roles. Review access when responsibilities change and remove access when it is no longer needed.
Secrets
Keep credentials in an approved secrets manager. The current Settings → Integrations page checks that connection credential storage is configured; the deployment-side CONNECTIONS_SECRET is required to encrypt newly saved credentials. Never commit the secret, place it in prompts or publish it in documentation. Existing environment-variable integrations are separate from saved connections.
Execution boundaries
Separate permission to read information from permission to change systems. Validate authorisation immediately before consequential actions.
Human oversight
Define approvals for sensitive, external, financial, legal, production or otherwise high-impact actions.
Audit and retention
Agree what evidence is recorded, who can inspect it, how long it is retained and how privacy obligations are met.
Data handling
Classify information, minimise collection and avoid sending personal or confidential data to services that are not approved for that purpose.
Incident response
Document how to disable an integration, revoke a credential, preserve evidence and notify the appropriate owner.
Worked example
Review a read-only integration
A reporting workflow needs to read approved records but has no business reason to modify them.
- 1Create or select an identity dedicated to this integration.
- 2Grant access only to the required records and read operations.
- 3Store credentials in the organisation's approved secret manager.
- 4Test that intended reads work and attempted writes are denied.
- 5Document the owner, expiry or rotation process, monitoring and revocation steps.
Was this guide useful?
Send feedback or flag a gap. Include the article link so the team can improve the right guide.