Bengar Console AVAILABLE
Where a person reads what happened and decides what needs deciding.
What it is
- The control plane: agents, permits, policies, approvals, executions, audit, proofs, API keys and roles.
Why it exists
- Authorization decisions only a machine can see are decisions nobody reviews.
How it works
- Sign in, pick a project, and work inside it.
- Every page re-authorizes at the Gateway; hiding a link is a courtesy, not a control.
Who uses it
- Administrators, approvers, auditors, policy authors
Security boundary
- ADMIN is not implicitly every role — it cannot approve, author policy or register a permit.
- The Console holds no private key and never constructs an approval payload.
- No screen grants a role today; that is set up out of band.
Example flow
A morning
- Read the dashboard: decisions in the last 24 hours, what is pending, what is unknown.
- Reconcile an UNKNOWN execution after checking the merchant.
- Read the audit trail for the agent that produced it.
Current status
| Capability | Status | Where |
|---|---|---|
| Sign in and pick a project | AVAILABLE | /projects |
| Grant a role to a person | AVAILABLE | /projects/:id/security/members |
| Read the audit trail | AVAILABLE | /projects/:id/audit |
| Create, list and revoke API keys | AVAILABLE | /projects/:id/api-keys |
Related API
/v1/console/**