Set who may use a repository's actions and workflows

Set access_level: none, or organization to let the workspace's other private repositories use this repository's actions and reusable workflows (user is read as organization).

PUT/repos/{owner}/{name}/actions/permissions/access

Needs the Admin role.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: workflow with action set_access, and the same inputs
Scope: An access token needs repo:admin.

Path parameters

Name	Type	Required	Description
`owner`	string	Yes	The workspace that owns the repository.
`name`	string	Yes	The repository’s name.

Body parameters

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name	Type	Required	Description
`access_level`	string	Yes	One of `none`, `organization`, `user`.

Example request

curl -X PUT https://api.g1t.sh/repos/flagon-io/shared-workflows/actions/permissions/access \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "access_level": "organization"
  }'

Example response

A successful request answers 200 with:

{
  "access_level": "organization"
}

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.