How approval works
In Boidra Platform, the person who creates an AI asset is never the person who approves it. Every agent, MCP server and skill passes a review before it is deployed and published, and a Release Approver makes that decision.
Approvals rest on the roles and scopes your SAP BTP XSUAA assigns. Nothing in SAP's own products is changed along the way.
The review flow
- Create and register. An Agent Engineer creates the asset and registers it; its status is Created and it can still be edited.
- Submit for review. The author presses Submit for review on the asset page.
- Review and approve. A Release Approver checks what the asset does, which data it can reach and which workspace owns it, and approves it.
- Deploy and publish. The asset is deployed by its pipeline and published to the AI Asset Dashboard.
The full workflow, with the deployment diagram, is in Create, register, publish & deploy an agent.
The rules
- Four eyes, always. Submitting for review and approving belong to different roles, so the author of an asset can never approve it.
- The server enforces it, not the screen. An approval from someone without the Release Approver role is refused with
403, and the response names the missing scope. In the app, the button is shown disabled with a note such as "Approve — requires the Release Approver role", so people know whom to ask. - Production is protected. Destructive actions in an environment marked as production ask you to type the environment's name to confirm.
Other changes that need a human
- Environment mapping. When Boidra discovers your BTP subaccounts, it only suggests which environment each belongs to (for example "name matches /prod/"). An admin confirms every suggestion; none is applied automatically.
The audit trail
Every approval and confirmed mapping is written to an append-only, hash-chained audit log. Each entry records who acted, taken from their signed-in SAP BTP identity rather than from anything the browser sends, so an approval cannot be recorded in someone else's name. Because each entry is chained to the one before, an edited or deleted entry breaks the chain and shows.
Who does what
| I want to… | I need |
|---|---|
| Create, register and submit an asset for review | Agent Engineer role |
| Approve an asset in review | Release Approver role |
| Confirm environment mappings, manage environments and keys | Platform Operator role (PlatformAdmin) |
| See every asset, approval and audit entry | Any role (Read) |