Skip to content

Guidance on permissions for fine-grained tokens #365

Open

Description

@madchap

Hi,

It would be great to have guidance on which permissions are needed when using fine-grained tokens. Thanks!

Activity

  1. eilidhmae commented on Jan 24, 2025

    @eilidhmae

    Second this. I am blocked, and find this step too vague to proceed.

  2. backspace commented on Oct 30, 2025

    @backspace

    yes, did something change about permissions for tokens? I remember it being a checklist with code-like names as described in the documentation (org:read) but in the Github UI they’re all English-y names now

    Image
  3. backspace commented on Oct 30, 2025

    @backspace

    Following up, I found that these permissions are what worked:

    Image

    I didn’t iterate this one step at a time because I needed someone to approve permissions changes for me, but this is probably the minimal set, or close to it, for our structure, at least.

  4. KevinWu098 commented on Jan 5, 2026

    @KevinWu098

    Implemented PAT on an org recently. Based on this comment in a similar thread, I was able to get it working. My settings being:

    Actions: Read/Write
    Contents: Read/Write
    Metadata: Read (required)

    Happy to put up a PR to add this guidance to the docs, lmk @peter-evans

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions