Home Dashboard

The Home dashboard is the first thing you see after signing in. The page title states the one thing that needs attention — for example how many critical findings are still open — so you do not have to scan the rest of the page to know where you stand. Press g h from anywhere to get back to it.

​

Glance numbers

Four numbers sit under the title. Each one is a link:

• Critical — findings that are still open at critical severity
• High — findings at high severity
• For retest — findings waiting on a retest
• Assets — hosts in your attack surface

During the free Micro Pentest trial the three finding counts match the Findings page — they only include that trial, not other pentests. The refresh icon in the top right reloads every card without reloading the page. Pressing r does the same thing.

​

Finish setting up

If your name is missing, GitHub is not connected, or billing is not set up yet, a Finish setting up card appears under the page title. Each row says why it matters and takes you through:

• Add your name — so comments and assignments show who you are
• Connect GitHub — needed for pentests and PR reviews (members and admins)
• Reconnect Bitbucket or Reconnect Azure DevOps — shown instead of Connect GitHub when your only source-control connection has expired. It opens that integration so you can reconnect it (members and admins)
• Set up billing — adds a payment method so scans and reviews can run (admins only, and only when Billing is switched on for your organisation)
• Connect your Slack account — lets you ask @Odin in Slack and makes your replies there show as you (only when your organisation has connected Slack and your account isn’t linked yet)

A blue progress bar sits at the top of the card. The card tracks how many of those steps are done, and disappears once they are. The same card also appears at the top of Testing > PR Reviews for the remaining testing steps. You can dismiss the Slack row with its close button. It stays hidden for a week in that browser, then comes back if your account still isn’t linked. See Linking your Slack account. If Odin has already found your Slack account by email, Home shows a We found you in Slack banner instead of the Slack row. Select Confirm it’s you to confirm the match from your profile. First-time payment setup for pay-as-you-go stays in this card rather than a second banner. Later billing problems get their own banner. See Prompts and banners. The same two setup steps also sit in a Get started card at the bottom of the sidebar until they are done: Connect GitHub and Add a payment method. Below them, Connect your AI agent is marked Optional and does not count towards progress. The card disappears once the two required steps are complete. Organisations still on a billed trial see the trial checklist in that slot instead.

​

Set up with your AI agent

Members and above see a Set up Odin with your AI agent card under Finish setting up until they connect an agent to the organisation, either by signing in or with an API key they created that has been used. Select Copy setup prompt, then paste the prompt into Claude Code, Codex, Cursor, VS Code or another AI agent. The agent:

1. Connects to the Odin MCP server. You sign in to Odin when asked. Most agents need a restart before Odin’s tools appear; paste the prompt again afterwards.
2. Checks what your organisation has already set up, and looks at the repository it is running in.
3. Recommends the setup that fits, with links to the pages your organisation has: for example, connecting GitHub and turning on PR reviews for that repository, adding your domains as assets, or connecting your issue tracker.
4. Helps you reach a first result. It offers to fix your most severe open finding, or suggests turning on PR reviews if there are none.
5. Offers to add a short Odin section to the repository’s AGENTS.md or CLAUDE.md, so later sessions know about Odin.

The agent asks before it changes anything. Show prompt shows the full text before you copy it. The prompt holds no API key. Cursor and Codex connect with a Read & Write key that you keep in the ODIN_API_KEY environment variable. Dismiss the card with ×. It stays dismissed for that organisation in this browser. The same prompt is always available at the top of Workspace > AI agents. Read-only members don’t see the card, because they can’t connect an agent.

​

Getting started

Home is the same dashboard for every organisation. Turn on PR reviews from Testing in the sidebar. Launching an AI pentest or Micro Pentest from Odin is currently unavailable. The sun or moon control in the top bar switches appearance between Light, Dark, and System. System follows your operating system.

​

Prompts and banners

If initial workspace setup could not finish, Workspace setup is still pending appears after signing in, including after a reload. Your organisation is saved. Owners can select Retry setup to resume the remaining connections or first-scan setup without creating another workspace. You can keep exploring while optional connections are unavailable. The message disappears once setup is confirmed complete. For organisations without Intelligence, when there are Critical or High findings, an alert banner repeats those same glance counts and links to the Findings page filtered to those severities. The numbers match the Critical and High tiles — they are not a separate “awaiting action” subset. Organisations with Intelligence see Your next steps instead of the Critical items banner. It lists up to five open findings ranked by what matters most to the organisation, with Fix now, Next, and Later priorities. All by priority opens Findings in priority order. If there is nothing to act on, the card says No open findings need action. If priorities cannot load, it points you to Findings so you can still review them. Both this card and the Critical items banner are hidden when Findings is switched off for your organisation. Open a finding from Your next steps to read it in a preview. Home and Intelligence previews offer the same permitted finding actions: assign or clear an assignee, create or view a linked tracker issue, and inspect available retest history. Your role and the finding’s state determine which controls appear; Read only users can inspect available history without write controls. Pay-as-you-go organisations can also see a billing banner. Select it to open Billing:

• Payment recovery needed — a payment failed or needs action from you. New billable work is paused until the outstanding balance is paid. Any pay-as-you-go organisation can see this, including older accounts billed after usage.
• Add credits to start billable work — prepaid accounts only. The payment method and tax location are set up, but there are no credits left. Add credits before you start a billable service.

Plan organisations never see this banner. See Pay as you go. Plan organisations see a credit banner instead when their balance needs attention. Plan credits are spent first, then adhoc credits, so scans keep running while either balance lasts:

• Plan credits running low — less than 20% of this period’s plan credits are left. The banner also shows your adhoc balance, if you have one.
• Plan credits used for this period — your plan credits are used up and scans are now using your adhoc credits. The banner shows the adhoc balance and the date your plan credits renew.
• Adhoc credits running low — your plan credits are used up and your adhoc balance is below 20% of your plan’s allowance.
• Out of credits — you have no plan or adhoc credits left. Buy adhoc credits or upgrade your plan to keep running scans.

You can dismiss the banner for the rest of your browser session. See Billing for plan and adhoc credits.

​

Overview cards

Open findings sits on the left and takes two thirds of the row. Attack surface and Status stack on the right. The chart stretches to that column so every status stays visible:

• Open findings: a stacked area chart of open findings over time. Critical sits on top, then High, Medium, and Low. The filled area under each layer is the open count at that date. A finding stays in the stack from the day it is reported until it is acknowledged or fixed and retested. The legend shows the latest counts. During the trial the series includes locked findings so you can see how many there are; a note under the chart says how many need a paid plan.
• Attack surface: asset counts by type (Domains, Subdomains, IPs). Active, Inactive, and Unverified totals sit at the bottom of the card. Empty types still show 0 so the card stays the same height.
• Status: counts through the status lifecycle — Reported, Fixing, Needs Revision, Open for Retest, Fixed & Retested, and Risk accepted. Each row uses the same progress mark as Findings, and statuses with no findings still show 0 so the card stays the same height. During the trial these counts include locked findings.

Activity sits under that grid. Each entry names the finding (or other item) and what changed, plus when it happened. Click an entry to open the related finding, asset, or settings page. Two cards have an empty state. Open findings reads No findings yet until a Critical, High, Medium, or Low finding is reported. Activity reads No recent activity until there is activity on your findings, pentests or team. Attack surface and Status have no empty state; they show 0 in every row.