Skip to main content
Request capture and the persisted Decisions page are enabled in the current sandbox deployment. Provider decision delivery is still pending, so the console shows Policy decision delivery is not connected yet with empty history. Successful inference alone does not create a decision: actual per-policy results require a verified event feed. Existing recorded decisions remain available if delivery later disconnects, but requests without authoritative evaluation results are not presented as completed checks.
Open Decisions in the console to review actual policy evaluations for the selected workspace. The page includes all projects by default, independently of the sidebar’s project selector.

​
Find decisions

Search by request ID, decision ID or policy. Filter by:
  • Time: the last 24 hours, 7 days, 30 days, 90 days or year.
  • Decision: Allowed or Blocked.
  • Check status: Complete, Partial or Failed.
  • Direction: Request or Response.
  • Project: one project or all workspace projects.
Clear filters returns to the default view: all projects and outcomes from the last 24 hours. The table shows the newest matching records, up to 100, with times in UTC. The number shown is the displayed row count, not the total number of historical decisions. A link with ?policy=<policy ID or name> starts with that policy in the search field. Editing the search or clearing filters removes that preset.

​
Read a decision

The table shows the evaluation time, decision, check status, number of evaluated policies, direction and project. Select a row or its time to open Decision details. An allowed request does not by itself mean every check succeeded. Monitoring checks can report a match or failure without blocking delivery. Read the outcome and check status together; missing evidence is not converted into an assumed pass, failure or per-policy match.

​
Recorded data and access

Decision history contains metadata about evaluations. It does not display request text, generated output, policy rule text, raw credentials or provider payloads. Policy names and versions identify the evaluated policy snapshot rather than implying that later edits changed an earlier result. Current members can view their workspace’s recorded decisions. Switching workspaces changes the history and clears the selected detail. Request and decision IDs belong to this service; use them to identify the corresponding request without sharing prompts or responses. No matching rows means no recorded decisions match the current view. It does not prove that no requests were made or that every request passed its checks. Before recording is connected, or when authoritative delivery is unavailable, use the delivery notice and request activity to understand what is known.