The Overview is the first page of an organization in K-Block Cloud. Its header shows the organization's name. Below it, the page answers two questions: what needs a person right now, and what happened in a recent period.
Every number on the page comes from the Cloud API, which computes it from this organization's recorded data when the page loads. The dashboard shows no sample or placeholder data. Every role (owner, admin, approver, developer, viewer) can open the Overview.
What is on the page
From top to bottom:
| Part | What it tells you |
|---|---|
| Set up K-Block | The setup guide. It is shown until all eight setup steps are done. See Setup guide. |
| Needs attention | What is not fully enforced or waits for a person: emergency stops, observe windows, tools to authorize, policies without an active version. |
| Waiting for approval | Up to five requests that wait for an approver now, each linking to its decision page. |
| Activity | Figures, a daily chart and rankings for the chosen time range. |
On a new organization, some of these parts are hidden until there is something to show (see First run and empty states).
Needs attention
This card lists what is not fully enforced or needs a person now. The card says that every call is still checked by the Gateway, whatever it lists. Each row has a text label, a short explanation, and links to the page where you handle it.
| Label | Shown when | Links to |
|---|---|---|
| Emergency stop | A policy's active version is an emergency stop. The row says whether every call is denied or every call needs approval. | The policy |
| Observe · live keys or Observe · test keys | An agent has an open observe window. Its relaxed decisions are recorded, not enforced. The row shows when the window ends. A window that covers both live and test keys reads Observe · live keys. | The agent |
| Waiting | Approval requests wait for a decision. The row is left out when the Waiting for approval card lists them. | Approvals |
| Stale or Unauthorized | Enabled tools cannot be called until an owner or admin authorizes them (Unauthorized) or authorizes them again after their upstream binding changed (Stale). | Tools & MCP servers |
| No active version | A policy has agents but no active version, so every call of those agents is denied. | Policies |
| Enforced | Everything was read and none of the rows above applies. | Policies |
| Not set up | Shown instead of Enforced when no policy version is active (every agent call is denied) or no agent is active. | Policies or Agents |
| Unknown | Part of the state could not be read. The row names what was not read and claims nothing about it. | Policies |
Below the rows, an Also in effect line lists informational items: shadow versions (evaluated but never enforced) and revoked API keys. Revoked keys are listed only for owners, admins and developers, because only those roles can read API keys.
Where the card reads its state
The card makes its own reads when the page opens:
- the organization's policy status (open observe windows and shadow versions);
- the first 100 policies, and the details of any policy whose active version looks like an emergency stop, to confirm it;
- the first 100 tools;
- the first 100 API keys, for owners, admins and developers only.
Related pages: Emergency stop, Observe and shadow, Tools and MCP servers.
Waiting for approval
This card loads the five newest pending approval requests and lists those whose expiry has not passed, so it can list fewer than five even when more are waiting. Each row shows the tool and action, the amount when the call has one, the agent, the environment (Live or Test) and when the request expires. A row opens the request's decision page.
Review N requests opens the Approvals inbox. The count is the Overview's number of requests waiting now, which can be more than the five rows listed. When nothing is waiting, the card says so and offers Open inbox.
The number of requests waiting counts pending requests whose expiry is still in the future, across all time, not only the chosen range.
Activity
The Activity section covers a range of whole UTC days that ends today (UTC). The header names the range, for example "Last 30 days: 13 September – 12 October 2026, UTC".
Time range
Choose 7 days, 30 days or 90 days. The default is 30 days. The range switch is hidden on a first run (see below). The page does not filter by environment: live and test calls are counted together.
Figures
| Figure | What it counts in the range |
|---|---|
| Protected actions | Every tool call the Gateway recorded, by the time it was created. It is split into Allowed, Requires approval and Denied (the policy decision), each with its share. Relaxed by observe mode counts allowed calls that the policy would have denied or held for approval, allowed only because an observe window was open. Where they stand now groups the same calls by their current status: Open (pending approval, approved, executing), Executed (succeeded, failed), Authorized for the caller (decision only: K-Block authorized, the caller executes; never counted as executed), Not executed (denied, rejected, expired, cancelled). |
| Executions | Executions that finished in the range: Succeeded and Failed. In flight now counts executions that have started and not finished, at any time. |
| Approval decisions | Requests approved plus requests rejected, by decision time. Expired counts requests that were closed as expired in the range, superseded ones included. Median decision time is the median time from request to approval or rejection. |
| Executed amount | The sum of the amounts of executions that succeeded in the range, one total per currency, with the number of executions. Calls without an amount are not counted. Totals are shown with the currency's decimal places and never rounded. |
| Receipts issued | Signed receipts created in the range. See Receipts. |
View actions and View receipts open the matching lists.
Activity per day
The Activity per day chart has a Chart switch with four views:
| View | Series |
|---|---|
| Volume | Protected actions and receipts issued |
| Decisions | Allowed, requires approval and denied, stacked |
| Outcomes | Executions succeeded and failed, stacked |
| Approvals | Requests approved, rejected and expired, stacked |
Each point is one UTC day. When all activity in the range happened on a single day, the page names that day in a sentence instead of drawing a chart. The chart appears once activity spans two or more days.
Top tools, top agents and deny reasons
- Top tools: the five tools with the most calls in the range, with how many were denied.
- Top agents: the five agents with the most calls. Each name opens the agent.
- Deny reasons: up to ten reason codes of denied calls, with a readable name next to the code (for example "No delegation grants the action" for
NO_DELEGATION). See Error codes.
First run and empty states
- Quiet organization. When the range has no protected actions, nothing is waiting for approval and nothing is in flight, the figures are replaced by one line: "No protected actions in the last N days." It also explains that calls made through the K-Block Gateway appear here.
- First run. When the organization is quiet and has no active policy version or no active agent, the page hides the range switch and the Waiting for approval card, and the setup guide leads. Needs attention is hidden too when the only thing it would say is Not set up.
- Range with no activity but open work. If the range has no protected actions but something is still waiting for approval or in flight, the figures stay visible next to the "No protected actions" line, so you can see the open work.
How the page refreshes
The page reads its data once when it opens. Changing the time range reads the figures again, but not the Needs attention card. The page does not poll. If someone decides an approval, or an agent makes a call, while the page is open, reload the page to see it.
The observe banner at the top of every organization page is the exception: it reads the policy status every 30 seconds, when the window gets focus and when the tab becomes visible again. So the banner can show a new observe window before the Needs attention card does.
If the Overview cannot be loaded, the page shows "Could not load the overview" with the reason (and, when known, an error code and a request ID) and Try again. The setup guide is still shown, without a state for the steps that depend on the Overview's counts (see Setup guide). Select Try again or reload the page. If the error continues, contact K-Block support and give them the code and the request ID shown in the error. Common problems explains the codes you may see.