A home page built around what needs attention

The first page an admin sees in Keyboard should answer one question: is there anything I need to deal with? This week's release rebuilds the dashboard home page around that question, fixes how team usage is measured against limits, and makes the dashboard's tables faster to scan. Self-hosted organizations also get a way to see which releases are available to them.

Needs attention, up front

For IT Admins. The home page now opens with a Needs attention strip: a row of cards, each tinted by category, for the things that need action:

• teams that are over or near their usage limit;
• flagged and failed AI actions;
• access reviews that are overdue or due soon;
• connectors that are failing on 5% or more of their API calls;
• API usage outliers;
• available updates.

When there are more cards than fit, arrows and page dots let you move through them. The strip says "All clear" only when every check actually ran, and notes when some checks couldn't run, so an empty strip never hides a check that silently failed.

Why it matters: an admin can open the dashboard and see in seconds whether anything is waiting on them, without visiting each section in turn.

At a glance: trends and activity

For CIOs. Below the strip, At a glance tiles show the last 30 days of AI events, AI spend, active users and policy coverage, each with the change against the previous 30 days.

A single row then brings together:

• AI activity: a 7-day chart with a tooltip for each day, navigable by keyboard.
• Team AI usage: the top five teams, with progress bars against their limits and the date each limit resets.
• Top connectors: the five most-used connectors.

Every number on the page now comes from live data, with no sample or placeholder values.

For CISOs. Recent activity now matches the audit log table: date, user, tools and action, with the same badges for suspected prompt injection and for content that was not redacted. Anything that stands out on the home page looks the same when you follow it into the audit log.

Team usage measured correctly against limits

For IT Admins and CIOs. Team usage is now measured in the same unit as team limits (actions), so active teams no longer appear far over their limit when they aren't. The home page, the Needs attention cards and the team usage bars now reflect where each team actually stands.

Why it matters: limits are only useful if the numbers behind them are right. Admins can now trust a "near limit" warning and act on it.

Sort any table by any column

For IT Admins. Clicking a column header now sorts almost every multi-column table in the dashboard. The first click sorts A to Z, and a second click reverses it. Some details that make this work well:

• Empty cells stay at the bottom in both directions.
• Paged lists sort every row before splitting them into pages, not just the page you're on.
• Status and risk columns sort by severity, not alphabetically.
• Lists whose default order carries meaning (for example, granted items first) keep it until you click a header.

Search boxes across the dashboard also get a consistent focus outline, so it's clear which one you're typing in.

Release discovery for self-hosted installs

For CIOs. Organizations that run Keyboard in their own infrastructure pull its components through Keyboard's image registry. Standard update tools can now list the releases available there, for the same components and under the same access checks as before, so they can detect new versions and propose upgrades instead of failing to find any. Nothing new is exposed: only the published versions of components an organization is already allowed to pull.

Why it matters: self-hosted teams can keep Keyboard current with the update tooling they already use.

Getting started

The new home page is live for every organization. Open the Keyboard dashboard to see what needs your attention, and visit the Keyboard docs to learn more.