# Roles ### Overview 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 {% hint style="info" %} For a detailed explanation check the section on [setting up your first project](broken://pages/hMsdc13TGMKoxO7vdY3P) {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ozone.one/ozone-end-user-guide/faq/roles.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.