Skip to content

Members and roles

A member is a person who belongs to your organization. Each member has one role that decides what they may do. Only an admin or an owner can manage members. Every member can see the list.

You do not create accounts for people yourself. You invite an email address, and the person joins when they first sign in with it.

The app describes each role like this:

Role What the app says
Viewer Can see inventories
Member Can also submit reports
Admin Can also manage members, API keys and trusted publishers
Owner Full control, including owners

In more detail:

  • A viewer reads everything: units, releases, findings, VEX statements and exports.
  • A member also uploads SBOMs, adds products, variants and releases, and records and decides VEX statements.
  • An admin also manages members, API keys, trusted publishers, package mappings and the settings of the organization.
  • An owner can do all that, and is the only role that may grant, change or remove an owner. Owners also see what Affectra staff changed in the organization. See Organizations and data isolation.

The roles table lists each action and the role it needs.

  1. Open Members under Organization in the app.
  2. Under Invite someone, enter the Email and choose a Role. The text under the form says what the role may do.
  3. Select Invite.

The person shows in the list with the status Invited. When they have signed in, it changes to Active.

An admin can give the roles viewer, member and admin. Only an owner can give the owner role. Give people the lowest role that lets them do their work.

If you invite someone who is already a member, Affectra tells you so.

The start page of the app offers the sign-in options your Affectra is set up with:

  • Continue with GitHub. Affectra uses the email address that GitHub reports as verified.
  • Continue with single sign-on. This leads to the sign-in page of the identity provider. With a password account, a person signs in with a password or a passkey.

A password account always needs a second factor, either an authenticator app or a passkey. A person who has none sets one up before they get in.

Affectra links a sign-in to a membership by the email address you invited, and only when the provider says the address is verified. A person who signs in with an address nobody invited sees There is no Affectra account for that email. Ask an admin of your organization to invite you, or to link your GitHub organization.

If someone has no GitHub account and no company sign-in, select Create a password account when you invite them. The checkbox appears only when your Affectra can create password accounts. Affectra emails them a link to choose a password and set up an authenticator app. The link works for 24 hours.

If the link expired, select Resend setup email next to the person. It shows for members whose status is Invited. Affectra sends the email only if the account was never set up. It answers the same either way, so nobody can use it to find out who has an account.

In the list, choose another role in the Role column. It applies at once.

  • Only an owner can give, change or take away the owner role. If you are an admin, the role of an owner shows as text, without a picker.
  • An organization always keeps at least one owner. Changing the last owner to another role, or removing them, fails with An organization must keep at least one owner. Make someone else an owner first.

Select Remove next to the person and confirm Remove … from this organization? They lose access at once. Only an owner can remove an owner.

Removing someone does not delete what they did. VEX statements they recorded and SBOMs they uploaded stay.

If your people already belong to a GitHub organization, you can let them join without an invitation.

You need to be an admin of that GitHub organization, and to have signed in to Affectra with Continue with GitHub. Affectra asks GitHub which organizations you administer when you sign in, and links only one of those. This way nobody can link a GitHub organization they don’t run.

  1. Sign in with Continue with GitHub. If you signed in another way, or became an admin on GitHub since, sign out and sign in with GitHub again.
  2. On Members, find the card GitHub organization and select Link GitHub.
  3. Enter the GitHub organization, optionally a Team (optional), and the Role they get. The role is viewer, member or admin, never owner.
  4. Select Save. If GitHub didn’t list you as an admin of that organization, Affectra answers To link a GitHub organization, sign in with GitHub as an admin of that organization, then save again.

Members of that GitHub organization or team then join with that role when they sign in with GitHub. They show with the badge via GitHub. They leave again when they are removed on GitHub, at their next sign-in with GitHub. A role you changed by hand is kept, and invited members are never removed this way.

Three things to know:

  • If you remove a via GitHub member in Affectra but they are still in the GitHub organization, they join again the next time they sign in with GitHub. To keep them out, remove them on GitHub too, or select Unlink.
  • A GitHub organization that restricts access for OAuth apps must approve Affectra. Otherwise GitHub hides its members, and nobody joins.
  • Affectra remembers the GitHub organization by its ID, not its name. If the organization is renamed on GitHub, the link keeps working.

A link saved before Affectra checked this is not verified. Until an admin of the GitHub organization saves it again, it adds nobody, removes nobody, and the card says The link to … is not verified and adds no one. To fix it, follow the steps above and select Change, then Save.

Unlink asks Unlink the GitHub organization? People it added stay members until you remove them.

Under Settings, an admin can turn on Four eyes for agent proposals. See Assess findings with VEX.