Project API Key Scopes

When creating an API key in the project settings, you can predefine access permissions for that key by selecting the relative scopes. The following table describes the permissions that each scope provides.

Scope	Description
`bot`	Enables communication between a Repeater and the Bright engine
`files:read`	Allows reading and download files from the storage
`files:write`	Allows to associate files with projects, clone files, upload or delete them
`integration.repos:read`	Allows viewing associated repositories, for example, GitHub repositories, Slack channels, or Jira boards
`issues:read`	Allows viewing detected scan issues
`issues:manage`	Allows execution and saving scan issues as new
`scans:delete`	Allows deleting scans
`scans:manage`	Allows editing scan settings
`scans:read`	Allows viewing existing scans
`scans:run`	Allows running and retesting scans
`scans:stop`	Allows stopping scans
`scripts:read`	Allows viewing repeater’s scripts
`scripts:write`	Allows creating, editing and deleting repeater’s scripts
`repeaters:read`	Allows viewing organization’s repeaters
`repeaters:write`	Allows creating, editing, and deleting a repeater, as well as testing repeater connection to a network