Skip to main content
A member is a person who can sign in to your organisation in Earnie. Each member holds one role, which decides what they can see and do. This page explains the three roles, how to add and manage members, and which role can do what. Not everyone who works with Earnie needs to be a member. Developers and coding agents usually work through pull request checks, the CLI, and the API, using API keys rather than a seat in the web app. Before you start: Adding, removing, and changing members’ roles needs the Admin role. Every role can see the Members list.

Three Roles

Members Earnie has three roles. They separate the people who change the rules from the people who do the daily review work. The roles are built in, and you can’t create your own or change what one allows. To compare the roles side by side in the app, select Compare all capabilities on the Members page. For the full list, see Who Can Do What.

Adding a Member

  1. Go to Settings → Members.
  2. Select Add member.
  3. Enter the person’s Email, and choose their Role.
  4. Select Add member.
Use the email address the person signs in with at your identity provider. They can sign in straight away with your organisation’s single sign-on (SSO): send them your Earnie address. On their first sign-in, Earnie matches the email the identity provider sends to the member you added, and refuses an email it doesn’t know. There’s no password to set and no invitation email. See Signing in.
If your Earnie deployment uses password sign-in. Some deployments turn on password sign-in instead of, or alongside, SSO. Then adding a member shows a one-time set-password link. Copy it and send it to the person yourself: Earnie doesn’t send it, and you can’t see it again. The link works once and expires after 72 hours.

Managing Members

The Members page lists everyone who can sign in to the organisation, with each one’s role and last sign-in. Search by email, or filter by role.
  • To change a role, pick a new role from the member’s row. The change applies from the member’s next action. You can’t change your own role.
  • To see what a member did, choose View in audit log from the row’s actions menu. This needs access to the audit log.
  • To remove a member, choose Remove from organization from the row’s actions menu, then Remove member. They lose access at once: Earnie ends their sessions and revokes every API key they created. Their triage decisions and audit entries stay on the record. You can’t remove yourself.
With password sign-in, the actions menu also offers Create set-password link for a member who has no password yet, and Reset password for one who has. The organisation always keeps at least one Admin, so Earnie refuses to remove the last Admin or change their role.
Changing a role doesn’t change a member’s API keys. A key keeps the scopes it was created with. If you lower someone’s role, review the API keys they created, and revoke any that carry more than their new role allows.

Branding

Settings → Branding holds your organisation’s logo. Earnie prints it in the header of the HTML, Excel, and PDF snapshot reports and reports that you make from the Reports page.
  • To upload a logo, select Upload logo, or drop the image onto the page. Use a PNG or JPEG of up to 512 KB. Earnie saves it as soon as the upload succeeds.
  • To replace the logo, select Replace logo, or drop a new image.
  • To remove it, select Remove logo. Snapshots generated afterwards have no logo in their reports.
A snapshot keeps the logo it was generated with, and every report rendered from it shows that logo. Changing the logo affects only snapshots you generate afterwards, never one that already exists. Every role can see the current logo. Only an Admin can upload, replace, or remove it.

Regulations

Settings → Regulations lists the compliance packages your organisation can make, each with who it’s for and its files. Tick the regulations that apply to your organisation and save with the bar at the bottom of the page. The New export sheet then lists those packages first and marks them Applies to your organization. The choice only orders and marks packages. It never hides one, and it doesn’t state that you comply with anything. Every role can see the list. Only an Admin can change it, and the change is recorded in the audit log.

Who Can Do What

In this table, ✓ means the role can do it, and a dash means it can’t. Some entries are more specific:
Earnie usually hides the actions your role can’t take. Some pages, such as Scan Configuration, show their settings without letting you change them, and say which role can. If a control you expect isn’t there, your role doesn’t allow it.

What’s Next

Pipelines and scripts don’t sign in as members. Next, set up API keys for your pipelines and scripts.