This page describes how the Hane console is organized and what you can see and do on each page. It also explains what the console deliberately does not change, and why.
The Hane console is for organization administrators, developers, and operators. The screens where users do their daily work belong to your apps (such as the reference app).
- It calls only the public API. Everything the console does can also be done through the API with the same permissions. No operation exists only in the console.
- It does not change definitions. The source of truth for types, workflows, agents, and other definitions is the manifests in Git. In the console you view ReleaseBundles and only activate, run canary releases, or roll back.
- You work in a chosen organization, project, and environment. The console calls the API with an access token for the combination selected at the top. What you see and the buttons you get depend on your permissions.
You sign in with your organization’s IdP, and the console exchanges the id_token for a Hane access token.
| Page |
What you can see and do |
| Dashboard |
Active release, records per type, cases and tasks per status |
| Definitions and releases |
Drafts and ReleaseBundles. Activate, start/promote/abort a canary, roll back to an earlier ReleaseBundle |
| Page |
What you can see and do |
| Data |
Definitions, records, relations, and findings. Try typed queries. Closing a finding is the only change you can make |
| Workflows |
Cases and waits, schedules, webhook subscriptions. Retry, restart, or cancel failed cases; trigger schedules manually |
| Approvals |
Claim, unclaim, and decide tasks that need a person (including approvals of outbound actions). Review assignment rules and decider policies |
| Documents |
Document list and search, extracted facts and review stats, index status. Rerun text extraction, place holds, delete |
| Agents |
Try agents in chat; runs, outbound actions, evaluations. Cancel runs or actions, reconcile actions with unknown outcomes, run evaluations |
| Communication |
Sent email, received replies, contact endpoints, sender identities. Verify, stop, resume, reveal, and hold contact endpoints; approve and revoke sender identities |
| Integrations |
Connections, imports and exports, secret rotations. Start imports and exports, give OAuth consent, rotate secrets |
| Browser |
Portal flows, runners, handoffs to people. Revoke runners |
| Voice |
Records and transcripts of AI calls placed by agents |
| API Gateway |
Published customer APIs, Consumers and API keys, call records, daily request counts. Issue and revoke Consumer API keys |
| App Factory |
Your apps, build records, registered images |
| Page |
What you can see and do |
| Members and roles |
Members, roles, and groups. Remove people who have left. Role bindings change through manifests (RoleBinding) or IdP sync |
| Service accounts and API keys |
Issue and revoke API keys. A key is shown only once, when issued |
| Operator engagements |
The basis on which the provider’s operators work in your organization. Stopping one takes effect immediately |
| Secrets |
Register, replace, and revoke secrets. Nobody can see a saved value |
| Page |
What you can see and do |
| Usage and budgets |
Usage for the last 14 days, today’s budget, model calls |
| Audit log |
Every operation in the organization. Requeue undelivered events |
| Emergency stop |
Stop and resume every API and run in the organization. Only the owner can resume |
| Page |
What you can see and do |
| API reference |
The OpenAPI of the public API |
| What you want |
Where to do it |
| Change definitions such as types, workflows, or agents |
Edit the manifests in Git and send them with hanectl apply or Git sync |
| Change role bindings |
RoleBinding manifests or IdP sync |
| Confirm values extracted from documents into the ledger |
Your app (business screens) or the API |