# Usage and activity: sign-ins, recent use, run results and the access review

Dokimore documentation · Plans, billing and your account · Updated 2026-11-16 · 6 min read

Written for: QA leads and test managers, Engineering managers · Where it applies: every market

> Usage & Activity (/usage) is every account's own history: when you signed in and from where, which features you used on which days, how many runs you started and how many passed, and what they cost at list price. The owner of a team, a co-admin and an auditor see the same for the workspace, member by member, with seat use and a quarterly access review that records a decision per member as evidence. The page shows what the server allows the account to see: a member never sees a teammate's history, and no IP address or raw browser string is shown to anyone.

## Who sees what

Every signed-in account opens My activity and Reports. The owner of a team, a co-admin and an auditor also open Team and Access review for their workspace. The platform's own administrator opens Platform and Cost analytics as well. The tabs follow the server's answer about the account, not a setting in the browser: a view the account may not open is not offered, and if a refusal still arrives the page shows your own activity and says so in a note.

A member of a team never sees a teammate's history. Nobody sees an IP address or a raw browser string on this page: the sign-in place is the approximate city, region and country that DB-IP derives from the address, and the device is the browser, operating system and type parsed from the user agent.

## My activity

- Pick a window of 7, 30, 90 or 365 days. The tiles give sign-ins and the last one, active days out of the window, runs with how many passed and failed, the pass rate with its 95% interval once there are enough runs to compute one, features used, and failed sign-ins with the count for the last seven days.
- Engagement is a band (active, cooling or dormant, or never for an account that has not signed in yet) with a score out of 100 and the reasons behind it, so the word is never the whole story.
- Daily activity is one bar per day of requests and runs; the darker top of a bar is the failed runs. Under it: this week against last week, and any day that stands out.
- Recent use lists each feature with its requests, runs, pass rate and the last time you used it. Recent sign-ins lists when, the outcome and its reason, the method (password, passkey or a sign-in provider), the place and the device.
- Usage cost is the list-price estimate of the runs in the window, by feature. The footer says when the history was last updated.

## Team

The Team tab lists every member with their role, last sign-in, last activity, active days, runs, pass rate, engagement band and signals. Seats shows how many are in use against the plan's maximum and how many are reclaimable, held by members who are dormant or have never signed in. Needs attention names the members whose signals warrant a look: a burst of failed sign-ins, a privileged role signing in without a second factor, a dormant privileged account, or a sign-in from a new country within twelve hours of the last one.

## Access review

Once a quarter, a workspace reviews who still needs access: the periodic user access review that ISO 27001 control A.5.18 and SOC 2 criteria CC6.2 and CC6.3 ask for. The tab ranks every member by risk (time since the last sign-in or any activity, a privileged role, no second factor, never active since joining) and recommends a decision with its reason.

- Decisions are Keep, Review role, Revoke and Exception. A reason is required for anything but Keep, and it is stored with the decision.
- You cannot decide your own access; another administrator does. An auditor reads the review and its decisions but records none.
- Recording a decision is evidence: it changes no access by itself. Removing a member or changing a role is done on the team page, and a change made there is what the next review sees.

## Reports

Reports compose a month or a year: requests, runs, passed, failed and sign-ins by day for a month or by month for a year, the change against the previous period, and a few highlights in words. Download CSV writes the same rows for a spreadsheet; a cell that starts with a formula character is neutralised, so a feature name can never run as a formula. A team administrator's report covers the workspace; everyone else's covers their own account.

## What is counted, and for how long

The page reads three records the platform already keeps: the request log of every signed-in call, the run index that every feature writes to (recordings and replays, test folders, QA Testing workflows and keyword runs, the API runner, performance tests, accessibility scans and crawls, security scans), and the sign-in history, refused attempts included. A scheduled job folds them into one row per person, feature and UTC day, recomputing the last three days each time it runs, so a number can lag the event by a little while. The rollup is kept for 400 days, as are sign-in records; the window you pick never reaches further back than that.

A run counts as passed or failed by what it reported, not by the fact that it finished: an API run whose tests failed, a keyword run whose items failed and an accessibility scan that could not cover every page all count as failed.

## Questions people ask about this

### Why does the page show zero for today?

The history is recomputed by a scheduled job; the footer gives the time of the last update. Sign-ins and runs made since then appear after the next run.

### Can a team member see what I did?

No. A member sees only their own activity. The owner of the team, a co-admin and an auditor see the workspace, member by member.

### Does recording a Revoke decision remove the member?

No. The decision is recorded as evidence of the review. Removing the member is done on the team page.

This guide is about the pricing page, with every plan and its limits: https://dokimore.com/pricing

Source: https://dokimore.com/documentation/usage-and-activity
