> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/managing-account/roles-and-permissions.md). # Roles and permissions The roles and permissions in Snyk API & Web Roles and permissions overview. Permissions control access to the main features of Snyk API & Web. For instance, to add a target, the user must have the `Create Target` permission. You can group permissions using [Roles](https://plus.probely.app/roles). For instance, the built-in role `Developer` can view targets, change target settings, change findings, and start target scans, but cannot add targets. You can then map roles to users at an account level, team level, or target level. When you are [adding a user](https://plus.probely.app/users), you can set the user's: * Global role, which is applied to all targets of the account (the role is set at an account level or global scope). * Team role, which is applied to all targets of that team. * Target role, which is applied solely to that target. As such, you can have a user that has, for instance, the role `Developer` at an account level, the role `SecOps` on a specific team, and the role `Admin` on a specific target. Learn more about this by visiting [Get started with teams](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/managing-account/get-started-with-teams.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/managing-account/roles-and-permissions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.