Requests & Review
A request asks someone to collect governance evidence for one agent. Two pages handle it:
- Available Requests is the work queue for the people who fill evidence.
- My Requests lists the requests you raised, so you can review and approve them.
Enterprise feature. Both pages are under Governance in the sidebar. Accepting, submitting and requesting changes need Request Queue & Approvals at Read & Write. Approving needs Request Queue & Approvals at Admin. Among built-in roles, Owner and Security & Compliance can do all of these; Department Admin and Auditor can view the pages only. See Compliance.
Request statuses
| Status | Meaning |
|---|---|
| Pending | Created and waiting for someone to accept it |
| Accepted | Someone accepted it and is filling the evidence |
| Submitted | The evidence was submitted for review |
| Changes Requested | The reviewer sent it back with feedback |
| Approved | The reviewer approved the evidence |
| Cancelled | The requester cancelled it |
An agent can have only one open request (Pending, Accepted, Submitted or Changes Requested) at a time.
Raise a request
Requests are raised from a governance profile with Assign to Developer, right after you create the profile. See Evidence Collection. Choose how to notify people:
| Channel | What is sent | Request reference |
|---|---|---|
| Slack | A message in the agent's mapped channel, "AI Compliance: Evidence Collection Request", with your instructions and a View & Accept Request button | Link to the Slack message |
| Jira | An issue "[AI Compliance] Evidence Collection: agent" in the agent's mapped project, labelled ai-compliance and evidence-collection, with your instructions and a link to accept it | Link to the Jira issue |
| Linear | An issue "[AI Compliance] Evidence Collection: agent" in the agent's mapped team, with your instructions and a link to accept it | Link to the Linear issue |
The channel, project or team comes from the agent's mapping in Project Settings → Integrations. See Slack, Jira and Linear.
The request reference is stored with the request and shown on both pages, so reviewers and contributors can jump to the conversation. If sending the notification fails, the request is still created.
A request created with Fill Evidence Myself has no notification. It shows as Not sent in My Requests, where you can still use Send via Slack, Send via Jira or Send via Linear.
Available Requests
Available Requests shows:
- Pending requests that nobody has accepted yet, for anyone with access to the queue. Requests that were never sent are not listed.
- Requests you accepted, while they are Accepted or Changes Requested.
Each row shows the agent, who raised it, the channel it came through, and its status (New, Accepted or Changes requested).
Accept the request
Select Accept Request. The request is assigned to you and disappears from everyone else's queue. If someone accepted it a moment before you, you see "This request was just accepted by another developer."
Fill the evidence
Select Continue Editing to open the evidence form. Fill the eight categories and sign each category's attestation. See Evidence Collection.
Submit
Select Submit for Review. The request becomes Submitted and the evidence becomes Pending Review. Only the person who accepted a request can submit it.
Address feedback
If the reviewer requests changes, the request shows Changes requested with the feedback. Select Address Feedback, update the evidence, and submit again.
My Requests
My Requests lists the requests you raised. Filter by status, or search by agent or developer name. Each row shows the agent, who accepted it, the channel, the status and the relevant dates.
Review the submission
Select Review to open the agent's evidence and check each category.
Approve or request changes
- Approve Submission opens Approve Evidence, where you can add optional notes for the audit trail.
- Request Changes asks for feedback, for example "Data Governance: Clarify retention period". The request and the evidence become Changes Requested. If the request came through Slack, the feedback is posted as a reply in the original thread. If it came through Jira, it is added as a comment on the issue.
You can also Cancel Request any request that is not yet approved.
What approval configures
Approving a submission:
- Marks the evidence Approved and the request Approved.
- Stores a permanent approval record with the approver, requester, time and your notes.
- Configures the agent's AI Guardrails Scheduled Detection policy from the evidence, running Daily. Approve Evidence shows a preview of the labels it will turn on.
| Evidence answer | Detection turned on |
|---|---|
| PII Categories Processed | The matching PII labels |
| Data Leakage Prevention | All PII labels |
| PCI Data Collected | All PCI labels |
| PHI Data Collected | All PHI labels |
| Output Filtering or Abuse Detection | All 14 Ethics & Bias harm categories |
| Protected Attributes Tested | The matching bias types, for example Gender Bias or Age Bias |
| Bias Assessment Completed, with no protected attributes | All bias types |
| Prompt Injection Protection or Jailbreak Detection | Jailbreak / Prompt Injection safety detection |
If no answer maps to a label, no policy is configured. You can change the policy afterwards in Governance → AI Guardrails.
Approval status does not change Framework Coverage. Coverage counts filled and attested evidence whether or not it has been approved.
Audit trail
Creating and updating requests, editing evidence and signing attestations are recorded in the audit log. Review them on the Audit Trail tab of Audit & Export.
Next steps
- Evidence Collection: what goes into a submission.
- AI Guardrails: adjust the detection policy that approval configured.
- Members & Roles: who can accept, review and approve.