Feature request for "Guest Permission Level"

[derkan]

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

[daviian]

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

[lafriks]

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

[daviian]

@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.

[6543]

@derkan is #6274 what you wanted?

[derkan]

@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)