Overview
Fast answers for owners and stakeholders.
Alignment enforced through procedure.
Fast answers for owners and stakeholders.
| Date | Chats | Blocked | No Answer | Useful Feedback |
|---|
Admin-only user and question reporting over Q interaction logs.
Amazon Quick query events and Snowflake Agent requests remain explicitly labelled because they are different activity units.
| Source | Evidence | Date | User | Agent | Activity Unit | Count | Conversations | Status / Outcomes |
|---|
| User | Resources | Agents | Flows | Direct | Group | Owner |
|---|
| Resource | Type | Users | Direct | Group | Owner |
|---|
| Via | Principal | Users | Resources | Rows |
|---|
| Source | Evidence | User | Resource Type | Resource | Role | Via | Principal | State | Updated |
|---|
Snapshot deltas from Quick metadata syncs. This starts from the first sync after history was enabled.
| Source | Evidence | Changed | Type | User | Resource | Via | Role |
|---|
| Source | Evidence | Date | Endpoint | User | Role | Status | Requests | Rows |
|---|
Investigation leads from transparent rules and evaluated behavioural or semantic vectors. A flag is not a finding of misuse, and blocked or unanswered requests are not proof of an authorization denial.
| Source | Inference | Severity | Pattern | User | Score / observed | Comparison | Why flagged | Last Seen |
|---|
| Source | Evidence | Time | User | Agent | Status | Prompt | Response |
|---|
| Source | Evidence | Period | User | Queries | Agents | Conversations | Agent IDs | Last Seen |
|---|
Compares the selected date range against the immediately preceding range of the same length.
| Source | Evidence | User | Baseline Queries | Baseline Agents | Baseline Conversations | Agent IDs | Baseline Last Seen |
|---|
Current Q-log evidence for stakeholder question 8: per-agent outcome volume, common blocked/no-answer patterns, and redacted examples. Semantic top-use-case clustering is not enabled yet.
| Source | Evidence | Agent | Outcome | Events | Share | Users | Conversations | Evidence Preview |
|---|
Current configured scope only—not complete effective Snowflake access or proof of use. NULL and configured-empty arrays remain distinct.
| Source | Evidence | User | Role context | Scope | Masking | Locality | Practice IDs | Data domains | Configuration status | Network aggregate | Source record updated |
|---|
Curated observability counts with approved redacted samples. Generated SQL remains trace metadata rather than a separate SQL audit source.
| Source | Evidence | Date | Agent | Status | Events | Users | Requests | Warnings / Failures | Generated SQL | Evidence Preview |
|---|
Classified observability only. Prompt mentions, trace metadata, and potential access are not proof that exact values were displayed.
| Source | Evidence Type | Date | User | Agent | Data Class | Evidence Rows | Patient | NHI | Practice | Redaction |
|---|
| Reason | Conversation | Details |
|---|
| Check | Status | Type | Observed and threshold |
|---|
Admin-only runtime owner mappings and agent display names. Changes apply immediately across the dashboard.
| Agent | Owners | Updated By | Updated At |
|---|
Ask follow-up questions over the current analytics scope.
Current scope: all agents for the selected reporting window.
How to configure the dashboard, use each section, and complete common Guardian workflows.
Sign in with your Pinnacle account. Guardian starts a new chat by default and either restores your browser snapshot or loads the dashboard from the server.
The line below the header buttons reports sign-in state, cached data, refresh progress, partial failures, ownership changes, chat activity, and report downloads.
If it says Showing cached dashboard, the displayed snapshot includes its saved time. Press Refresh when you need current server data.
The scope bar remains above every section and shows the agents and reporting window currently in use.
Use Overview to understand volume, reliability signals, feedback, ownership, and which agents need attention.
This Advanced-mode section is admin-only. It combines several governed reports while preserving the source and evidence type of every result.
Use Governance Answers for supported stakeholder questions and Who Ran Queries / Requests for labelled Amazon Quick interactions and Snowflake Agent requests.
Review usage, current access, access changes, unusual behaviour, blocked or unanswered interactions, user activity, gone-quiet users, and redacted question examples.
Review request counts, question outcomes, warnings or failures, generated-SQL metadata, and approved patient or practice evidence classifications.
Review endpoint activity and transparent unusual-behaviour flags from Guardian API audit evidence.
Use the Advanced-mode Feedback Explorer to inspect feedback users explicitly submitted.
Health loads with the main Refresh and shows whether the reporting pipeline and supporting metadata are fit for use.
Shows whether reports are current and the measured lag in days.
Shows the overall result and failed checks. The table lists each check and its type.
Shows the share of chat events mapped to known agents.
Shows current coverage against the configured minimum threshold.
Use Ownership Gaps to find active agents without an owner. Admins also receive the Ownership & Naming controls.
Guardian Chat is a read-only analytics assistant. It uses the current agent and date scope and re-checks governed data for every turn.
Comparisons are supported; state the periods you want, for example “last 7 days versus the previous 7 days.”
Usage rankings return five results by default. Ask for an exact depth such as “top 7” or “top 12”, then use “show 5 more” to expand the same ranked scope. Chat rankings are capped at 50 identities per source.
The report button is disabled for all-agent or multi-agent scope. Reports are separate artifacts; asking for one in chat does not replace the download action.
These sequences combine the shared scope with the sections described above.
Use the status line and current scope first; both are designed to explain the dashboard state.