Everything here applies only while your organisation is on a trial plan. On a paid plan none of it appears.
The setup wizard
Until the wizard has been finished or skipped, an Owner or Admin who opens Odin is taken to it at/welcome instead of Home. Members go straight to Home. They still get the sidebar checklist, but not the wizard.
The wizard has five steps, listed in a rail down the left of the screen:
- Welcome, which shows your plan and how many trial credits you have
- Add an asset
- Connect GitHub
- Invite your team
- Done
1
Add an asset
Type a domain you own and select Start discovery. Odin adds it as an asset with continuous asset discovery switched on, so it keeps mapping subdomains, IPs and exposed services rather than scanning once. The step shows the cost before you start: about 5 credits a day.
2
Connect GitHub
Select Authenticate with GitHub and install the Odin app. If your GitHub organisation needs an admin to approve the installation, the step says so and waits. Once you’re connected, Odin lists your open pull requests and offers Review this PR on each one, with an estimate of 1 to 5 credits depending on the size of the pull request. You don’t have to wait for the review: results appear on the PR Reviews page in Odin and as inline comments on the pull request.
3
Invite your team
Send invites by email, one address at a time. The step tells you how many seats your plan includes, and lists each person as their invite is sent.
- Take the tour — start the guided tour
- Open Assets — see what discovery has found so far on the Assets page
- Talk to us — open a chat with the Borg team
- Open Odin — go to Home
Example findings
A new trial organisation has nothing in Findings until discovery and your first reviews have run. So the first time an Owner or Admin opens the wizard, Odin adds four example findings for you to learn the triage flow on. They range from High to Low severity and sit at different points in the status lifecycle. Every one carries an Example badge and a title starting with “Example:”, and a banner above the findings table explains what they are. Status changes on an example are practice only. Move one through triage and the finding says so, with the note “Practice mode — status changes on examples don’t stick”. Nothing is saved. Anything that would reach a real system is switched off. You can’t push an example to Linear, Jira or GitHub, export it, or ask for a retest, so there is no way to file a ticket from fake data. The discussion thread does work, and you can post to it. Those comments are saved only in your browser on this device and are never shared. The examples are removed automatically once your first real findings arrive. You can also remove them earlier with Dismiss examples on the banner, which needs the Member role or higher. Dismissing removes all four for everyone in the organisation and cannot be undone. Restarting setup does not bring them back.Example findings never use a number from your organisation’s finding sequence, are not linked to any asset, and are only visible while you’re on a trial plan.
The sidebar checklist
At the bottom of the sidebar, a Trial setup panel tracks six tasks and shows how many are done:
Each row links to the page where you’d do the work. A task on a page your organisation can’t open is hidden rather than shown as a dead link. Underneath, Take the tour lets you start the tour again. Owners and Admins also have Restart setup, with the identity verification and organisation-wide effect described above.
When the trial is close to ending, the panel adds a prompt to choose a plan, with the days left and the credits you’ve used. This happens within 48 hours of the trial end date, or once you have less than a fifth of your trial credits left. After the trial ends, the prompt changes to Trial ended · choose your plan.
The panel is only shown during the trial. Choosing a plan ends the trial, so the panel goes away.
The guided tour
The tour is a seven-step walkthrough of the triage flow, using the example findings. It covers:- The Findings list
- Opening a finding
- Moving a finding through triage
- The discussion thread
- Sending a finding to your issue tracker
- The credits and progress on Home
- The sidebar checklist
When the trial ends
A trial ends on whichever comes first: the trial end date passing, or the trial credits running out. A banner then appears across the workspace, titled Your trial has ended or You’ve used all your trial credits. The workspace becomes read-only. Your findings, assets and configuration all stay visible, but new scans, reviews and most other changes are blocked until someone chooses a plan. View trial summary on the banner opens a summary of what the trial produced:- Assets discovered, and how many are continuously monitored
- Security findings, by severity
- PR reviews completed, and the findings they raised
- Pentests completed
- Credits used, out of the credits granted
- Credits remaining
Quickstart
The first things to do after signing in