Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

docs: add API key scopes documentation#20742

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
Emyrk merged 7 commits intomainfromdocs/add-api-key-scopes-documentation
Nov 17, 2025

Conversation

@Emyrk
Copy link
Member

Description

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

Changes

  • Added "API Key Scopes" section todocs/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 keyscopes, 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 becombined with scopes to restrict tokens to specific resource UUIDs.
Make it explicit that allow lists are exclusive - tokens can ONLY act onresources in the allow list. Add example showing how to maintain accessto other resources by being exhaustive with allow list entries.
Emphasize the exhaustive nature of allow lists by showing thatadditional entries would be needed.
Replace organization:* with user:read which is a valid scope.
@EmyrkEmyrk marked this pull request as ready for reviewNovember 12, 2025 22:46
@EmyrkEmyrk requested a review fromstirbyNovember 14, 2025 14:30
@EmyrkEmyrk merged commita272843 intomainNov 17, 2025
32 checks passed
@EmyrkEmyrk deleted the docs/add-api-key-scopes-documentation branchNovember 17, 2025 17:34
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsNov 17, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@stirbystirbystirby approved these changes

Assignees

@EmyrkEmyrk

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@Emyrk@stirby

[8]ページ先頭

©2009-2025 Movatter.jp