Managing Access Scopes

For some Bright operations and integrations, you will need specific scanning and management permissions provided by selecting the relative access scopes. For example, to enable integration with your CI pipeline, you may require to create an organization or a personal API key with a predefined set of scopes. Each scope grants the permission to perform a certain action, such as create, run, view, edit, or delete a particular Bright component.

There are three cases when you can select access scopes: