Dashboard
Dashboard, above Analytics in the sidebar. It is where you land right after signing in, and it is scoped to you — what needs your attention, not the organization's numbers. Switching projects narrows it to that project; the project picker at the top of the sidebar is what moves it.
:::note Recently changed The Dashboard is new. The sidebar item used to point at the page now called Analytics — if you followed this manual's older Quickstart, that is the "Boards" screen it meant. Dashboard and Analytics are two different screens now, both always visible above the rest of the sidebar, Dashboard first. :::
What's on it
Seven sections, each showing at most five items with a link to the full screen for the rest — this is a summary of what needs a look, not another place to work through a long list.
Getting started — four one-time milestones for a new organization (invite a second person, connect a CI source, write a test case, connect Jira). Owners and admins only, and it disappears once every box is checked.
Health, last 7 days — pass rate, tests awaiting automation, outdated tests, tests flagged unstable, and open bugs by severity.
My work — everything you are part of, not everything assigned to you: your sessions, the bug hunts you're on, test cases awaiting your review, open issues you reported, and tests you flagged unstable. Sekee has no general "assignee" field, so this is built from participation — being a session participant, a bug hunt member, a test case's author or reviewer, a bug's reporter — rather than from a task list nobody maintains.
Right now — sessions in progress, bug hunts currently open, and automation runs from the last hour.
Needs attention — overdue bug hunts, unstable tests nobody has picked up, outdated tests, requirements with no coverage, and (where error tracking is on your plan) errors that have recurred today.
Upcoming — sessions and bug hunts starting in the next 7 days.
Team pulse — who has been active in the last 7 days, content changes only. Every reader sees the same scope here, admins included — it is not the organization's full activity log.
Alongside all of it, an Activity rail shows the organization's most recent changes with a search box and a link to the full log.
Sessions and bug hunts you're "on"
"Your sessions" and "bug hunts you're on" mean you are a participant — the same relation that makes commenting on a session or a bug hunt join it automatically. There is no separate step to be added to one.