How do Roles work? How are they scoped?


Ozone provides granular permissions that can be customised to suit your needs of what level of access a user has to the CI/CD workflow. Some users may require only access to request for workflow executions, whereas others may be expected to set the governance standards through templating of CI/CD workflows along with all the permissions that are expected of a role with just workflow execution permissions.

Ozone takes this a step further by allowing you to scope a role to a member within a project, thus enabling just the right amount of access without disrupting the productivity that development teams require

For a detailed explanation check the section on setting up your first project

Last updated