Skip to content

Conversation

@Emyrk
Copy link
Member

@Emyrk Emyrk commented Nov 12, 2025

Description

Adds a brief section to the API & Session Tokens documentation explaining API key scopes.

Changes

  • Added "API Key Scopes" section to docs/admin/users/sessions-tokens.md
  • Includes overview of scope functionality and security benefits
  • Documents scope format (resource:action) and wildcard usage
  • Provides CLI examples for creating scoped tokens
  • Lists common scope examples with descriptions

Motivation

Users need documentation on how to create and use scoped API tokens for improved security by limiting token permissions to only necessary operations.

Testing

  • Reviewed documentation formatting
  • Verified markdown structure
  • Confirmed examples are accurate

Add a section to the sessions-tokens documentation explaining API key
scopes, including:
- Overview of scope functionality and security benefits
- Scope format (resource:action) and wildcard usage
- CLI examples for creating scoped tokens
- Common scope examples with descriptions
Add documentation for allow lists as an advanced feature that can be
combined with scopes to restrict tokens to specific resource UUIDs.
Make it explicit that allow lists are exclusive - tokens can ONLY act on
resources in the allow list. Add example showing how to maintain access
to other resources by being exhaustive with allow list entries.
Emphasize the exhaustive nature of allow lists by showing that
additional entries would be needed.
Replace organization:* with user:read which is a valid scope.
@Emyrk Emyrk marked this pull request as ready for review November 12, 2025 22:46
@Emyrk Emyrk requested a review from stirby November 14, 2025 14:30
@Emyrk Emyrk merged commit a272843 into main Nov 17, 2025
27 checks passed
@Emyrk Emyrk deleted the docs/add-api-key-scopes-documentation branch November 17, 2025 17:34
@github-actions github-actions bot locked and limited conversation to collaborators Nov 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants