Use integrations control to prove an action is safe before it runs.
The integrations control surface is where operators move from adapter knowledge into runtime decision-making. It is designed to keep validate, evaluate, and execute in one place so deny reasons stay visible.
Who this is for
Operators, solution engineers, and controlled-release teams working with adapters and fail-closed execution paths.
When to use it
Use this when onboarding a new adapter, testing an action payload, investigating a deny, or preparing an approved live execution.
Required setup
Required setup: active tenant context, admin session, and a known adapter. Admin routes require tenant_id and redirect to login if the admin session is missing.
How to use
1. Open the control surface
Enter through /admin/integrations?tenant_id=<tenant> after starting an admin session for the tenant.
2. Choose adapter and inspect schema
Review the adapter list and schema so the request payload matches the integration contract before you submit anything.
3. Validate the intent
Use validate first to catch malformed payloads and obvious missing fields without invoking policy or execution.
4. Evaluate policy
Run evaluate to see allow or deny decisions, policy basis, and risk reasoning. Treat this as the pre-execution gate.
5. Execute only after approval
Use execute only when the evaluate result is acceptable and the change has the necessary approval. Keep dry-run enabled by default unless the operation is explicitly approved live.
What success looks like
Related console surfaces
/admin/integrations?tenant_id=<tenant> - integrations control surface/docs/integrations/adapters/ - adapter reference docs