> For the complete documentation index, see [llms.txt](https://vampauth.gitbook.io/vampauth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vampauth.gitbook.io/vampauth-docs/api-reference/management/scopes.md).

# Scopes and permissions

A scope allows a token to attempt an operation. The account still needs current access and the corresponding project capability.

| Scope                            | Capability/access                                                                                 |
| -------------------------------- | ------------------------------------------------------------------------------------------------- |
| account:read                     | Current account                                                                                   |
| projects:read                    | Owned/member projects                                                                             |
| projects:write                   | Unrestricted token for create; edit\_settings for edits                                           |
| projects:delete                  | Project owner                                                                                     |
| collaborators:write              | Project owner, including listing                                                                  |
| keys:read                        | view\_keys                                                                                        |
| keys:write                       | create\_keys to create; edit\_keys for edit/ban/unban/renew; reset\_hwids for reset               |
| keys:delete                      | delete\_keys; independent of write/read                                                           |
| groups:read                      | Any of view\_keys/create\_keys/edit\_keys/manage\_key\_groups/manage\_checkpoints/manage\_loaders |
| groups:write                     | manage\_key\_groups                                                                               |
| loaders:read                     | Script owner or linked-project manage\_loaders                                                    |
| loaders:source:read              | Same access, separate permission for protected output                                             |
| loaders:write                    | Publish/manage/move/rotate; manage\_loaders for default payload                                   |
| loaders:delete                   | Permitted loader deletion                                                                         |
| providers:read / providers:write | manage\_checkpoints                                                                               |
| hwid-bans:read / hwid-bans:write | manage\_hwid\_bans                                                                                |
| analytics:read                   | Current access; metrics also filtered by domain permissions                                       |

Binding/FFA edits require edit\_keys **and** reset\_hwids. The explicit reset action needs reset\_hwids without edit\_keys.

Loader moves authorize both old and new projects and preserve the script owner. Linked publishes use the project owner's quotas. Detached loaders are script-owner-only and require an unrestricted token.

Read-only presets exclude protected output and mutations. Full management explicitly includes destructive/output scopes. Select custom scopes when your integration needs less. Write scopes never imply reads, including when a recipe first GETs an ETag.

## Next steps

* [Teams and permissions](/vampauth-docs/features/teams.md)
* [Management API errors](/vampauth-docs/troubleshooting/api-errors.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://vampauth.gitbook.io/vampauth-docs/api-reference/management/scopes.md?ask=<question>&goal=<user_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.