Missing team permission to delete repos #13680

New Issue

GiteaMirror · 2025-11-02T10:50:08-06:00

GiteaMirror commented

2025-11-02 10:50:08 -06:00

Originally created by @silverwind on GitHub (Nov 6, 2024).

Feature Description

I would like to grant the ability to delete repos to a team, but even with all write-related permissions granted, the users are unable to see the repo "Danger Zone".

I think a new boolean option "Delete repositories" needs to be added to the "Repository access" section in the screenshot, which shows the team permission configuration.

Screenshots

Originally created by @silverwind on GitHub (Nov 6, 2024). ### Feature Description I would like to grant the ability to delete repos to a team, but even with all write-related permissions granted, the users are unable to see the repo "Danger Zone". I think a new boolean option "Delete repositories" needs to be added to the "Repository access" section in the screenshot, which shows the team permission configuration. ### Screenshots <img width="1181" alt="image" src="https://github.com/user-attachments/assets/486c8d29-3d46-4412-8515-dce60c111e3a">

GiteaMirror added the type/proposal label 2025-11-02 10:50:08 -06:00

GiteaMirror commented

2025-11-02 10:50:10 -06:00

@lunny commented on GitHub (Nov 6, 2024):

Administration acces is the answer

@lunny commented on GitHub (Nov 6, 2024): Administration acces is the answer

GiteaMirror commented

2025-11-02 10:50:10 -06:00

@silverwind commented on GitHub (Nov 6, 2024):

Administration acces is the answer

Ok, then I think the text "Members can pull and push to team repositories and add collaborators to them." should be updated to mention that it also grants access to "dangerous actions" like repo deletion.

@silverwind commented on GitHub (Nov 6, 2024): > Administration acces is the answer Ok, then I think the text "Members can pull and push to team repositories and add collaborators to them." should be updated to mention that it also grants access to "dangerous actions" like repo deletion.

GiteaMirror commented

2025-11-02 10:50:10 -06:00

@yp05327 commented on GitHub (Nov 6, 2024):

Actually, the description of these existing permissions are also terrible.
e.g.

sometimes PR unit also needs code access
user can always create issues no matter they have read or write permission. So write only means edit here. but for other units, write also contains the meaning of creating.
For package unit, Manage repository packages. is also strange. It is a motion, but as a description, it should be Registries for packages or something else.

@yp05327 commented on GitHub (Nov 6, 2024): Actually, the description of these existing permissions are also terrible. e.g. - sometimes PR unit also needs code access - user can always create issues no matter they have read or write permission. So `write` only means `edit` here. but for other units, `write` also contains the meaning of `creating`. - For package unit, `Manage repository packages.` is also strange. It is a motion, but as a description, it should be `Registries for packages` or something else.

GiteaMirror commented

2025-11-02 10:50:10 -06:00

@silverwind commented on GitHub (Nov 7, 2024):

user can always create issues no matter they have read or write permission. So write only means edit here. but for other units, write also contains the meaning of creating.

Yeah. I also noticed that a user with only read access to issues can create issue comments, so you are correct.

@silverwind commented on GitHub (Nov 7, 2024): > user can always create issues no matter they have read or write permission. So write only means edit here. but for other units, write also contains the meaning of creating. Yeah. I also noticed that a user with only `read` access to issues can create issue comments, so you are correct.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13680