Feature request for "Guest Permission Level" #1844

New Issue

GiteaMirror · 2025-11-02T04:14:55-06:00

GiteaMirror commented

2025-11-02 04:14:55 -06:00

Originally created by @derkan on GitHub (Jun 1, 2018).

Description

This a feature request for defining a new permission level named as Guest. Rights for this level will be:

Add, view Issues (Close only his/her issue)
View Wiki (no updating, deleting)
Watch/Unwatch Project
Star/Unstart Project
Will be able to view and download from releases
Will not be able to view or update private repository code and files
Will not be able to view or update private repository pull requests
Will not be able to fork, create repository, migration or organization

Actually Guest permission level will be a restricted version of Read level without any privileges on private repository codes/files.

This permission is important to make internal or external users to add/watch issues to private repositories themselves.

Please check here. As far as I see, Gitea needs Guest permission level. By this permission level Gitea;

Can be used for documentation(wiki),
Binary distribution(releases)
Bug tracking(issues)

for PRIVATE repositories.

A small comparison:

Gitea	GitLab
Admin	Owner/Maintainer
Read	Reporter
Write	Developer
!!!	Guest

Originally created by @derkan on GitHub (Jun 1, 2018). ## Description This a **feature request** for defining a new permission level named as `Guest`. Rights for this level will be: - Add, view Issues (Close only his/her issue) - View Wiki (no updating, deleting) - Watch/Unwatch Project - Star/Unstart Project - Will be able to view and download from releases - Will not be able to view or update private repository code and files - Will not be able to view or update private repository pull requests - Will not be able to fork, create repository, migration or organization Actually `Guest` permission level will be a restricted version of `Read` level without any privileges on private repository codes/files. This permission is important to make internal or external users to add/watch issues to private repositories themselves. Please check [here](https://docs.gitlab.com/ee/user/permissions.html). As far as I see, Gitea needs `Guest` permission level. By this permission level Gitea; - Can be used for documentation(wiki), - Binary distribution(releases) - Bug tracking(issues) for **PRIVATE** repositories. A small comparison: |Gitea|GitLab| |------|-------| |Admin|Owner/Maintainer| |Read|Reporter| |Write|Developer| |!!!|Guest|

GiteaMirror added the type/proposal type/feature labels 2025-11-02 04:14:55 -06:00

GiteaMirror closed this issue

2025-11-02 04:14:55 -06:00

GiteaMirror commented

2025-11-02 04:14:55 -06:00

@daviian commented on GitHub (Jun 2, 2018):

I think this is already possible with org teams and unit type permissions.

@daviian commented on GitHub (Jun 2, 2018): I think this is already possible with org teams and unit type permissions.

GiteaMirror commented

2025-11-02 04:14:55 -06:00

@lafriks commented on GitHub (Jun 2, 2018):

Not quite, as you can not specify write to issues but read only for other stuff

@lafriks commented on GitHub (Jun 2, 2018): Not quite, as you can not specify write to issues but read only for other stuff

GiteaMirror commented

2025-11-02 04:14:56 -06:00

@daviian commented on GitHub (Jun 7, 2018):

@lafriks AFAIK a read only team is able to create issues at the moment

So a read-only team with disabled Code and Pull Requests has exactly the permissions as requested.
The team members are able to see/create issues, see releases and read the wiki.

@daviian commented on GitHub (Jun 7, 2018): @lafriks AFAIK a read only team is able to create issues at the moment So a read-only team with disabled Code and Pull Requests has exactly the permissions as requested. The team members are able to see/create issues, see releases and read the wiki.

GiteaMirror commented

2025-11-02 04:14:56 -06:00

@6543 commented on GitHub (Sep 7, 2020):

@derkan is https://github.com/go-gitea/gitea/pull/6274 what you wanted?

@6543 commented on GitHub (Sep 7, 2020): @derkan is https://github.com/go-gitea/gitea/pull/6274 what you wanted?

GiteaMirror commented

2025-11-02 04:14:56 -06:00

@derkan commented on GitHub (Sep 8, 2020):

@6543 thanks for ping back. This PR brings a use case: A company runs a Gitea instance that requires login. Most repos are public (accessible/browsable by all co-workers). At some point, a customer or third party needs access to a specific repo and only that repo. Making such a customer account restricted and granting any needed access using team membership(s) and/or collaboration(s) is a simple way to achieve that without the need to make everything private.

But in my feature request this case is needed: A company runs a Gitea instance and wants to allow public users to read wiki,add/read his issuses, download releases for a repo if rights given to him. By this we can make use customer use gitea for:

Binary distribution(automatic updates with using release files) ( no need for web site uploads)
Online help (wiki) (no need for web site out-date web manuals)
Issue handling ( no need for mail conversations for issue handling)

Currently, we can not limit user for not accessing source codes(and PR's)

@derkan commented on GitHub (Sep 8, 2020): @6543 thanks for ping back. This PR brings a use case: A company runs a Gitea instance that requires login. Most repos are public (accessible/browsable by all co-workers). At some point, a customer or third party needs access to a specific repo and only that repo. Making such a customer account restricted and granting any needed access using team membership(s) and/or collaboration(s) is a simple way to achieve that without the need to make everything private. But in my feature request this case is needed: A company runs a Gitea instance and wants to allow public users to read wiki,add/read his issuses, download releases for a repo if rights given to him. By this we can make use customer use gitea for: - Binary distribution(automatic updates with using release files) ( no need for web site uploads) - Online help (wiki) (no need for web site out-date web manuals) - Issue handling ( no need for mail conversations for issue handling) Currently, we can not limit user for not accessing source codes(and PR's)

GiteaMirror commented

2025-11-02 04:14:56 -06:00

@wxiaoguang commented on GitHub (Apr 8, 2025):

We have it now (in 1.24)

Add anonymous access support for private/unlisted repositories #34051

A repository could set permission for anonymous (guest) users.

@wxiaoguang commented on GitHub (Apr 8, 2025): We have it now (in 1.24) Add anonymous access support for private/unlisted repositories #34051 A repository could set permission for anonymous (guest) users. ![image](https://github.com/user-attachments/assets/bd43e680-bf4c-4747-8710-26568ad0a6e5)

GiteaMirror referenced this issue

2025-11-02 12:01:51 -06:00

[PR #1844] [MERGED] LDAP Public SSH Keys synchronization #16080

GiteaMirror referenced this issue

2025-11-02 12:01:59 -06:00

[PR #1855] [MERGED] Delete Public SSH Key tmp file after calculating fingerprint #16087

GiteaMirror referenced this issue

2025-11-02 12:02:01 -06:00

[PR #1856] [MERGED] Setting to disable authorized_keys backup #16088

Sign in to join this conversation.