- Adding people to Earnie, for Admins.
- Signing in, for everyone in your organisation.
- The setup wizard, which the first administrator runs once to connect your code and start the first scan.
Before You Begin
To sign in, you need to be a member of the workspace already. Earnie doesn’t create an account the first time someone signs in through single sign-on (SSO). An Admin adds you first, as described in Adding People to Earnie. To run the setup wizard, you need to be the workspace’s first administrator: the person SCANOSS set up when it created your workspace, or the person set as the first administrator when your organisation installed Earnie. You also need access to your code:- GitHub: owner rights on the GitHub organisation that holds the repository. If you aren’t an owner, the wizard gives you a link to send to an owner, so they can finish the connection.
- GitLab: a group, project, or service account access token with the
apiandread_repositoryscopes, and the Maintainer role on the projects you want to scan.
Adding People to Earnie
An Admin gives each person access by adding them as a member:- Go to Settings, then the Members tab.
- Select Add member.
- Enter the person’s Email. Use the address they sign in with at your identity provider, so Earnie can recognise them.
- Choose their Role: Admin, Operator, or Viewer. Team & roles explains what each role can do.
- Select Add member.
Signing In
- Open your Earnie address in a browser.
- On the Sign in to Earnie page, select Sign in with corporate SSO.
- Earnie redirects you to your organisation’s identity provider, the service your company uses to manage logins. Sign in there as you normally do.

After You Sign In
Where you land depends on who you are and how you arrived:- The first administrator goes to the setup wizard each time they sign in, until they finish or skip it.
- If you opened a link to a specific Earnie page while signed out, for example from a pull request comment, Earnie takes you to that page after you sign in.
- Everyone else goes to the last project they viewed, or to All Projects. If your organisation has only one project, you go straight into it.
The Setup Wizard

You can leave the wizard and come back. Earnie reopens it at the first step you haven’t completed. Once the first scan has started, it reopens at Add members.
Skip setup, at the top right, ends the wizard at any point. So does finishing it. Either way, the wizard doesn’t open again, and you complete any remaining steps from the Finish setup card in the sidebar.
1. Welcome
The first screen explains what the wizard builds: one governed inventory of all your code, with what Earnie’s scanners find in it. Under Where your code lives, select the GitHub or GitLab card, then select Connect GitHub or Connect GitLab. If that provider is already connected, the button reads Continue and takes you straight to step 3.2. Connect a Provider
- GitHub
- GitLab

- Authorise Earnie so it can see which GitHub organisations you belong to. Select Connect GitHub, then copy the code Earnie shows, select Open GitHub, and enter the code there.
- Choose the organisation that will own the connection. The list shows whether you’re an owner or a member of each one, and also offers your personal account.
- Create the app. Select Create app for your organisation. Earnie creates a private Earnie app for it on GitHub. If you aren’t an owner of the organisation, you can’t create the app. Earnie gives you a hand-off link to send to an owner instead. The link works once and lets the owner finish the setup without an Earnie account.
- Install the app. Select Install on GitHub, and choose the repositories Earnie may read.
3. Select Repository
In this step you create your first project: the codebase Earnie governs, together with its scans, decisions, and rules.- Pick the repository this project will govern. The list shows the repositories the connection can reach. Use Filter repositories to find one.
- Name the project. Earnie fills in the repository’s name when you pick it. You can change it and add a description.
- Choose what the first scan runs.
- Scanners analyse the source code itself: OSS matching, Cryptography, and AI provenance, depending on what your organisation has. Earnie selects all of them. You can turn any off, but at least one must stay on. If your organisation has only one scanner, this choice doesn’t appear. See AI provenance for what the AI scanner identifies.
- Download Git LFS models appears when AI provenance is on. It controls whether Earnie fetches model files stored in Git LFS so it can identify them. Keep the project preference, which is off for new projects, or download or skip for this scan only. Downloads use the repository owner’s Git LFS bandwidth quota.
- Intelligence layers add data to what the scanners find: Vulnerabilities and License. Both are on. Turning one off makes the first scan finish sooner, and you can re-run a scan with more layers at any time.
- Select Continue.
4. First Scan

5. Add Members (Optional)

6. Starter Policy (Optional)

What’s Next
Your first scan is now running. Next:- Your first scan follows the scan through to completion and explains what it shows.
- Connecting a repository explains the access you granted and how to connect more repositories.
- Team & roles covers adding and managing members later.
