Skip to content

Roles and what each may do

Every member of an organization has one of four roles. Each role may do everything the role before it may do. Members and roles shows how to invite people and change roles.

A Yes means the role may do it. A dash means it may not. If a role may not do something, the app hides the control or shows it disabled, and the API answers 403.

Action Viewer Member Admin Owner
See units, releases, findings, VEX statements, proposals, package mappings, settings and the list of members Yes Yes Yes Yes
Export VEX as OpenVEX, CycloneDX or CSAF, and download SBOMs and their signatures Yes Yes Yes Yes
Turn their own finding emails on or off Yes Yes Yes Yes
Turn their own daily digest of agent proposals on (anyone may turn it off) - Yes Yes Yes
Send collector reports and import offline bundles - Yes Yes Yes
Add or rename products, variants and releases - Yes Yes Yes
Upload SBOMs and build provenance - Yes Yes Yes
Record VEX statements - Yes Yes Yes
File a proposal - Yes Yes Yes
Decide a VEX or unit-link proposal - Yes Yes Yes
Decide a package mapping proposal - - Yes Yes
Add and delete package mappings - - Yes Yes
Link units that report an unknown version to a release (aliases) - - Yes Yes
Set a product’s key and support end - - Yes Yes
Delete products, variants, releases and SBOMs - - Yes Yes
Invite members, change roles and remove members, except owners - - Yes Yes
Link or unlink a GitHub organization - - Yes Yes
See, create and revoke API keys - - Yes Yes
Add, change and delete webhooks, send test events and see their delivery logs - - Yes Yes
Add and remove trusted publishers - - Yes Yes
Turn the signature policy on or off - - Yes Yes
Turn vulnerability feeds on or off - - Yes Yes
Change the settings: CSAF namespace, four eyes for agent proposals and the time of the proposals digest - - Yes Yes
Give, change or remove the owner role - - - Yes
See the staff activity of the organization - - - Yes

With Four eyes for agent proposals on, a person cannot decide a proposal filed with their own sign-in, nor one from an API key they created, whatever their role.

An organization always keeps at least one owner.

An API key has its own two access levels, not the roles above. See API keys.

What the key may do Read only Can propose changes
Everything a viewer sees and exports Yes Yes
Send collector reports, upload SBOMs and build provenance, add products, variants and releases, record VEX statements and file proposals - Yes
Decide a proposal - -
Manage members, keys, trusted publishers or settings, or delete anything - -

A key made before keys had access levels can propose changes.

A run of a trusted publisher can upload SBOMs and build provenance. It can do nothing else.

Affectra staff create an organization and its first owners. They cannot see your data. See Organizations and data isolation.