From 9699ec2c874e0397b212bf5372f0719b832ca63a Mon Sep 17 00:00:00 2001 From: silverwind Date: Thu, 22 Oct 2026 23:46:15 +0000 Subject: [PATCH] docs: clarify that team package permissions cover the whole org (#605) Packages belong to the owner, so a team's packages permission covers every package of the organization, regardless of the team's repositories. State that in the access restrictions section, matching the team settings change in https://github.com/go-gitea/gitea/pull/39953. The old note announced a dedicated team permission for finer control, which has existed since the packages unit was added, so it is replaced. Reviewed-on: https://gitea.com/gitea/docs/pulls/605 Reviewed-by: Lunny Xiao Co-authored-by: silverwind --- docs/usage/packages/overview.md | 4 ++-- versioned_docs/version-1.27/usage/packages/overview.md | 4 ++-- versioned_docs/version-28/usage/packages/overview.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/usage/packages/overview.md b/docs/usage/packages/overview.md index 125c0f95..5fcc8ae8 100644 --- a/docs/usage/packages/overview.md +++ b/docs/usage/packages/overview.md @@ -55,11 +55,11 @@ and shows a link to the repository on the package site (as well as a link to the | Package owner type | User | Organization | |--------------------|------|--------------| | **read** access | public, if user is public too; otherwise for this user only | public, if org is public, otherwise for org members only | -| **write** access | owner only | org members with admin or write access to the org | +| **write** access | owner only | members of a team with write access to packages | Please note, that your respective package manager needs to have a [personal access token](development/api-usage.md#authentication) with the permissions `package` set to either Read or Read & Write to download and publish packages respectively. -N.B.: These access restrictions are [subject to change](https://github.com/go-gitea/gitea/issues/19270), where more finegrained control will be added via a dedicated organization team permission. +The packages permission of an organization team applies to all packages of the organization, regardless of the repositories assigned to the team. ## Create or upload a package diff --git a/versioned_docs/version-1.27/usage/packages/overview.md b/versioned_docs/version-1.27/usage/packages/overview.md index 125c0f95..5fcc8ae8 100644 --- a/versioned_docs/version-1.27/usage/packages/overview.md +++ b/versioned_docs/version-1.27/usage/packages/overview.md @@ -55,11 +55,11 @@ and shows a link to the repository on the package site (as well as a link to the | Package owner type | User | Organization | |--------------------|------|--------------| | **read** access | public, if user is public too; otherwise for this user only | public, if org is public, otherwise for org members only | -| **write** access | owner only | org members with admin or write access to the org | +| **write** access | owner only | members of a team with write access to packages | Please note, that your respective package manager needs to have a [personal access token](development/api-usage.md#authentication) with the permissions `package` set to either Read or Read & Write to download and publish packages respectively. -N.B.: These access restrictions are [subject to change](https://github.com/go-gitea/gitea/issues/19270), where more finegrained control will be added via a dedicated organization team permission. +The packages permission of an organization team applies to all packages of the organization, regardless of the repositories assigned to the team. ## Create or upload a package diff --git a/versioned_docs/version-28/usage/packages/overview.md b/versioned_docs/version-28/usage/packages/overview.md index 125c0f95..5fcc8ae8 100644 --- a/versioned_docs/version-28/usage/packages/overview.md +++ b/versioned_docs/version-28/usage/packages/overview.md @@ -55,11 +55,11 @@ and shows a link to the repository on the package site (as well as a link to the | Package owner type | User | Organization | |--------------------|------|--------------| | **read** access | public, if user is public too; otherwise for this user only | public, if org is public, otherwise for org members only | -| **write** access | owner only | org members with admin or write access to the org | +| **write** access | owner only | members of a team with write access to packages | Please note, that your respective package manager needs to have a [personal access token](development/api-usage.md#authentication) with the permissions `package` set to either Read or Read & Write to download and publish packages respectively. -N.B.: These access restrictions are [subject to change](https://github.com/go-gitea/gitea/issues/19270), where more finegrained control will be added via a dedicated organization team permission. +The packages permission of an organization team applies to all packages of the organization, regardless of the repositories assigned to the team. ## Create or upload a package