Manage permissions
To edit permissions, you need the relevant permissions yourself, for example, only Group admins can assign other users as Group admins.
If your company currently does not have any Group admins, ask Snyk support to promote at least one user.
Changing roles
To change roles for a user:
Click on the Members tab in the Snyk Web UI (example link: https://app.snyk.io/org/your-org-name/manage/members).
Find the member to update.
Update the role for that member, using the dropdown next to role.
Alternatively, use the Update a member's role in the organization API call to update the role of the members in your Organizations. This API call does not support updating the role of Group members. For updating the role of a Group member, follow the preceding steps to make changes via the UI.
Permissions per role
The Group Member role does not directly provide the user any rights. A Group Member needs to be granted an organization role or promoted to Group Admin.
Add/delete projects
x
x
x
Update project with new snapshot
x
x
x
Open fix PR's
x
x
x
Delete snapshot from project history
x
x
x
View team members
x
x
x
x
Invite/remove team members
x
x
Change team members’ roles
x
x
Create an Org level service account*
x
x
Manage plans and billing for this organization
x
x
Leave organization
x
x
x
Delete organization
x
x
View organization reporting
x
x
x
x
View organizations
x
x
x
x
Create an organization
x
View organization integrations
x
x
x
x
Edit organization integrations
x
x
Create group level Service accounts*
x
Set a License policy*
x
Set a Security policy**
x
Set global notifications preferences
x
Access to the account overall reporting (Group level reports)
x
x
(*) Only in paid accounts (**) Only in Enterprise Plan
Editing project attributes from the Snyk CLI
The Organization Collaborator role lacks permission to edit Project attributes, including using the CLI snyk monitor command with arguments such as --project-environment. Attempting to use these arguments without the proper permission causes the snyk monitor command to fail.
Users or service accounts requiring the ability to edit project attributes must be an Organization Admin or use a custom role with org.project.attributes.edit assigned. Alternatively, remove any arguments that edit the project attributes from the monitor call.
Last updated
Was this helpful?