> ## Documentation Index > Fetch the complete documentation index at: https://panaptico.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Route Actions From Verified State in Panaptico > Configure Panaptico to drive work, access, network placement, deploys, and approvals when verified state shows a gap. Integrates bidirectionally with existing tools. When Panaptico verifies that reality has diverged from your declared intent, it can route action automatically. Because the routing decision is grounded in evidenced verification, not assumption, your existing enforcement tools act only when the ledger proves they should. This guide explains the five routing patterns and how to configure them. ## Routing patterns Panaptico supports five common action types that integrate with tools you already use. ### Work routing to owners Every gap becomes a ticket with an owner. Panaptico creates the ticket, assigns it based on the resource or population, and tracks it until re-verification closes the loop. * **Typical integration:** ServiceNow, Jira, or Azure DevOps * **Trigger:** Signal or tracked field result changes to Off target, Unknown, or Unobserved * **Outcome:** A ticket is created with the evidence attached. When the fix lands and Panaptico re-verifies, the ticket is resolved automatically. ### Risk-adaptive access Authentication and authorization paths adapt based on verified risk signals. A user with clean posture gets standard access; a user with elevated risk gets a harder path. * **Typical integration:** Okta, Entra ID, or SailPoint * **Trigger:** Enriched Signal score crosses a threshold (for example, unmanaged device + anomalous location) * **Outcome:** The identity provider steps up authentication, requires additional approval, or limits session scope. ### Network placement and quarantine Devices or traffic segments are moved based on verified compliance state. * **Typical integration:** Cloudflare, Palo Alto Networks, or Cisco * **Trigger:** Device posture Signal is Off target (missing patch, no EDR agent, expired certificate) * **Outcome:** The device is placed on a quarantine VLAN, restricted to remediation resources, or blocked from sensitive segments. ### Verification-gated deploys Deployments proceed only when pre-deployment verification passes, and roll back automatically when post-deployment verification fails. * **Typical integration:** LaunchDarkly, GitHub Actions, or Azure DevOps * **Trigger:** Pre-deploy probe (for example, canary health check) returns Off target, or post-deploy Signal drifts * **Outcome:** The deployment is blocked or rolled back before broader impact occurs. ### Risk-proportional approvals Approval requirements scale with the verified risk of a change. * **Typical integration:** ServiceNow, Slack, or custom workflow tools * **Trigger:** Change request evaluation crosses a risk threshold based on affected populations and current posture * **Outcome:** Low-risk changes auto-approve; high-risk changes require additional reviewers or CAB approval. ## Bidirectional integration Panaptico routing is bidirectional with your existing tools. The platform does not replace Okta, Cloudflare, ServiceNow, or LaunchDarkly. It tells them when to act, based on proof. The tools enforce; the ledger decides. This also means that actions taken by those tools can feed back into Panaptico as evidence. A ServiceNow ticket resolution, an Okta step-up event, or a Cloudflare quarantine placement can all become Signals that verify the loop closed. ## Configure routing in the dashboard 1. Go to **Routing** in the dashboard and click **New Route**. 2. Choose the source: a Signal, tracked field, or Initiative gap. 3. Select the action type from the patterns above. 4. Connect the target system (for example, ServiceNow project or Okta policy). 5. Define the trigger condition (for example, Off target for 2 consecutive polls). 6. Set the scope: which populations or resources this route applies to. 7. Save and enable. Panaptico begins routing when the condition is met. ## Next steps Build budget-level programs that combine intent, verification, and routing. Understand how every routing decision is backed by full evidence.