Admin Usage Lens¶
Menu Location: Kiva Tools > Admin Usage Lens
Last Updated: 2026-10-25
Overview¶
Admin Usage Lens reconstructs what each admin account on a store actually did over a chosen window. It reads three activity logs that the store already keeps and rolls them into one card per admin, so you can see where time goes, what kinds of work dominate, when people work, and how much the AI assistant is used. The intended use is spotting what AI could take over for an admin.
The page is read-only. It does not change any data, add a migration, or write a setting. It is gated to Kiva admins: anyone else who opens it is sent to the dashboard. The page is available on the Kiva Logic master site. On other stores it is not in the menu and redirects away.
Kiva staff can also pull the same per-admin aggregate as JSON without an admin login, by calling the page with format=json and the AI query API key, optionally with a days value. This mode uses the same key and trust as the read-only AI query endpoint and returns the same numbers the page renders. It is for Kiva automation only and is not used by store admins.
Primary Functions:
- Window picker for Last 7, 30, 60, or 90 days (default 30), which reloads the page on change
- A count of admins active in the window
- One card per admin, ordered by logged actions, highest first
- Top pages, action categories, peak hours, and AI assistant usage on each card
- An Analyze with AI button per admin that writes a plain-English "what to automate" summary
What Each Card Shows¶
Each card is headed by the admin's display name (first and last name, falling back to the username), their access level and username, their real actions count and average per day for the window, and, when there were any, a separate + N automated figure.
Automated events are system-written log rows that a single admin click fans out into, such as adding each recurring item while generating a week's orders, "could not add" notices, and per-recipient email send or skip confirmations. They are triggered by an admin but are not admin work, so they are kept out of the action count, the page table, the action categories, and peak hours. The + N automated figure shows how much fan-out the admin's actions caused without inflating their workload.
Where time goes (top pages). The 15 pages that admin opened most often, with a hit count for each, taken from the admin page clickstream. A new design or a specific tool dominating this table is the clearest signal of where an admin spends their day.
What they do (actions). Action counts grouped into categories: catalog, pricing, subs, recurring, orders, customers, messaging, inventory, login, navigation, and other. Each logged action is assigned to the first matching category, so the split shows the shape of the work rather than a raw event list.
When (peak hours). The five busiest hours of the day for that admin, based on logged action times. Useful for matching automation or digests to when someone is actually working.
AI assistant. The number of AI assistant turns that admin made in the window, the dollar cost of those turns, and the tools those turns used, if any.
Analyze with AI¶
The Analyze with AI button on an admin's card sends that admin's computed usage summary to the AI assistant and renders the reply in a panel above the cards. The summary covers the admin's action count, top pages, action categories, peak hours, and AI usage. The reply is a short bulleted read on what the admin spends time on and the highest-value things that could be automated for them.
The analysis is generated when you click, not stored. Reloading the page clears the panel, and asking again produces a new reply. If there is no activity in the window, the page says so instead of sending an empty summary.
Common Use Cases¶
- Deciding what to automate. Run the lens across a month, find the page or category that dominates every admin's card, and use that as the candidate for an AI or bulk tool.
- Spotting uneven tool adoption. Compare cards to see whether one admin lives in a page the others never touch, which often means a workflow is unclear or a tool is unknown.
- Checking whether AI assistant investment is landing. The AI assistant block shows turns, cost, and tools per admin, so a rollout that nobody uses is visible immediately.
- Understanding workload and timing. Action counts per day and peak hours give a factual picture of when admins are active.
Troubleshooting¶
An admin is missing from the page. The roster is built from logged admin actions in the window, so an account with no actions in that window has no card. An admin who only used the AI assistant and performed no logged admin action will also not appear.
"No admin activity logged in this window." Nothing was logged for any admin in the selected window. Choose a longer window.
A page has no clickstream or no peak hours. Those two blocks come from different logs than the action counts. A store or period with one log populated and the other not will show an empty block with its own message.
The AI analysis fails. The panel shows the error returned by the AI assistant. Nothing else on the page depends on it, and the usage cards above and below remain accurate.
Recent Updates¶
2026-10-24: Initial release. Per-admin usage cards built from the admin page clickstream, the action log, and the AI assistant log, with a selectable 7/30/60/90 day window and a per-admin Analyze with AI synthesis.
2026-10-24: Added a key-authed headless JSON mode so Kiva staff can read a store's aggregate without an admin session. Same data and action categories as the page; supports a days parameter.
2026-10-25: System-authored cascade events (the rows one "generate orders" click fans out into: adding each recurring item, "could not add" notices, email send and skip confirmations, bulk SMS summaries) are now excluded from the action counts, page table, action categories, and peak hours. Their volume is reported separately as + N automated on each card, and the Analyze with AI summary states both figures.