[Feature] Hide Users and Orgs from public #1669

New Issue

GiteaMirror · 2025-11-02T04:08:59-06:00

GiteaMirror commented

2025-11-02 04:08:59 -06:00

Originally created by @mmarif4u on GitHub (Apr 3, 2018).

Currently when require_sign_in is set to false, non logged in users can see all other users and organizations which in some cases may not be a good idea as some people may want to keep them private. Only show public repositories.

A setting in app.ini to enable/disable this would be nice feature to have.

Originally created by @mmarif4u on GitHub (Apr 3, 2018). Currently when `require_sign_in` is set to false, non logged in users can see all other users and organizations which in some cases may not be a good idea as some people may want to keep them private. Only show public repositories. A setting in app.ini to enable/disable this would be nice feature to have.

GiteaMirror added the type/feature issue/confirmed labels 2025-11-02 04:08:59 -06:00

GiteaMirror closed this issue

2025-11-02 04:08:59 -06:00

GiteaMirror commented

2025-11-02 04:09:00 -06:00

@adilinden commented on GitHub (Apr 3, 2018):

Yes, was looking for this too. Using organization to group repositories. Showing only organizations with public repos to to the un-logged-in would be a nice feature.

@adilinden commented on GitHub (Apr 3, 2018): Yes, was looking for this too. Using organization to group repositories. Showing only organizations with public repos to to the un-logged-in would be a nice feature.

GiteaMirror commented

2025-11-02 04:09:00 -06:00

@NetOpWibby commented on GitHub (Apr 24, 2018):

I'm looking to transition to Gitea from my self-hosted GitLab instance and this is a feature that I miss. REQUIRE_SIGNIN_VIEW = true is nice but I'd like to have some public repos.

@NetOpWibby commented on GitHub (Apr 24, 2018): I'm looking to transition to Gitea from my self-hosted GitLab instance and this is a feature that I miss. `REQUIRE_SIGNIN_VIEW = true` is nice but I'd like to have _some_ public repos.

GiteaMirror commented

2025-11-02 04:09:00 -06:00

@agaida commented on GitHub (May 27, 2018):

I would like private orgs too - somethings should stay private - and showing some empty organizations (because all repos are private/hidden isn't really helpful

@agaida commented on GitHub (May 27, 2018): I would like private orgs too - somethings should stay private - and showing some empty organizations (because all repos are private/hidden isn't really helpful

GiteaMirror commented

2025-11-02 04:09:00 -06:00

@ghost commented on GitHub (Jun 3, 2018):

And hiding users/organizations with a template keeps them discoverable by trying URLs. I'd like to make my admin user or other sensitive users private and undiscoverable.

@ghost commented on GitHub (Jun 3, 2018): And hiding users/organizations with a template keeps them discoverable by trying URLs. I'd like to make my admin user or other sensitive users private and undiscoverable.

GiteaMirror commented

2025-11-02 04:09:00 -06:00

@SoulSeekkor commented on GitHub (Oct 11, 2018):

I'd like to add a +1 to this, looking to switch from Bitbucket but need to be able to have organizations not show up for users that don't have permissions for repos in them first.

@SoulSeekkor commented on GitHub (Oct 11, 2018): I'd like to add a +1 to this, looking to switch from Bitbucket but need to be able to have organizations not show up for users that don't have permissions for repos in them first.

GiteaMirror commented

2025-11-02 04:09:00 -06:00

@mcnesium commented on GitHub (Oct 12, 2018):

I run Gitea in Docker and have Apache proxy requests into the container. As a workaround to this issue, I set a proxy pass for gitea.domain/explore/ to the root of the container as well, which results in a 404 when the page is requested:

ProxyPass           /explore/  http://localhost:port/
ProxyPassReverse    /explore/  http://localhost:port/
ProxyPass           /          http://localhost:port/
ProxyPassReverse    /          http://localhost:port/

This of course results in noone being able to explore any of repos, users or organizations, not even logged in users, but that is ok for my own instance.

@mcnesium commented on GitHub (Oct 12, 2018): I run Gitea in Docker and have Apache proxy requests into the container. As a workaround to this issue, I set a proxy pass for `gitea.domain/explore/` to the root of the container as well, which results in a 404 when the page is requested: ProxyPass /explore/ http://localhost:port/ ProxyPassReverse /explore/ http://localhost:port/ ProxyPass / http://localhost:port/ ProxyPassReverse / http://localhost:port/ This of course results in noone being able to explore any of repos, users or organizations, not even logged in users, but that is ok for my own instance.

GiteaMirror commented

2025-11-02 04:09:00 -06:00

@stale[bot] commented on GitHub (Jan 7, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 7, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:09:00 -06:00

@markg85 commented on GitHub (Jan 22, 2019):

Just to add a "me too".
Though personally i don't have a use for it. I can imagine people working for organisations where they prefer to keep it hidden but still organized. Thus having an option to mark an organization as private would be sane there.

@markg85 commented on GitHub (Jan 22, 2019): Just to add a "me too". Though personally i don't have a use for it. I can imagine people working for organisations where they prefer to keep it hidden but still organized. Thus having an option to mark an organization as private would be sane there.

GiteaMirror commented

2025-11-02 04:09:00 -06:00

@SoulSeekkor commented on GitHub (Jan 24, 2019):

Yeah the fact that organizations show up for a user even though they have no permissions on any repos within it is keeping me from potentially switching over to soley using Gitea.

@SoulSeekkor commented on GitHub (Jan 24, 2019): Yeah the fact that organizations show up for a user even though they have no permissions on any repos within it is keeping me from potentially switching over to soley using Gitea.

GiteaMirror commented

2025-11-02 04:09:01 -06:00

@stevoh6 commented on GitHub (Feb 12, 2019):

Hi, I was looking for this too. "Using organization to group repositories. Showing only organizations+users with public repos to to the un-logged-in" would be a nice feature. We would like to have some hidden organizations/users with private repos together with some public organizations/users/repos.

@stevoh6 commented on GitHub (Feb 12, 2019): Hi, I was looking for this too. "Using organization to group repositories. Showing only organizations+users with public repos to to the un-logged-in" would be a nice feature. We would like to have some hidden organizations/users with private repos together with some public organizations/users/repos.

GiteaMirror commented

2025-11-02 04:09:01 -06:00

@lunny commented on GitHub (Feb 28, 2019):

Private organization has been implemented and merged into master.

@lunny commented on GitHub (Feb 28, 2019): Private organization has been implemented and merged into master.

GiteaMirror commented

2025-11-02 04:09:01 -06:00

@markg85 commented on GitHub (Feb 28, 2019):

It apparently is this commit: 64ce159a6e

Someone should probably close this issue.

@markg85 commented on GitHub (Feb 28, 2019): It apparently is this commit: https://github.com/go-gitea/gitea/commit/64ce159a6eacc81962d07a8f5ef7f69c17365363 Someone should probably close this issue.

GiteaMirror commented

2025-11-02 04:09:01 -06:00

@stevoh6 commented on GitHub (Feb 28, 2019):

Hi all, I updated gitea to newest version and do some testing. Repositories are fine, they are hidden, but even I setup correct config settings (FORCE_PRIVATE = true, DEFAULT_PRIVATE = private, DEFAULT_ORG_VISIBILITY = private) Users and organization are still visible even the new one.
There isnt also any setting regarding Users. Repositories working fine. Should I create defect, or I missing something?

Edit: it will be in 1.8.x ?

@stevoh6 commented on GitHub (Feb 28, 2019): Hi all, I updated gitea to newest version and do some testing. Repositories are fine, they are hidden, but even I setup correct config settings (FORCE_PRIVATE = true, DEFAULT_PRIVATE = private, DEFAULT_ORG_VISIBILITY = private) Users and organization are still visible even the new one. There isnt also any setting regarding Users. Repositories working fine. Should I create defect, or I missing something? Edit: it will be in 1.8.x ?

GiteaMirror commented

2025-11-02 04:09:02 -06:00

@lafriks commented on GitHub (Apr 8, 2019):

@stevoh6 private organization option will be in 1.8.0

Users will still be visible to all

@lafriks commented on GitHub (Apr 8, 2019): @stevoh6 private organization option will be in 1.8.0 Users will still be visible to all

GiteaMirror commented

2025-11-02 04:09:02 -06:00

@brallow commented on GitHub (Jun 12, 2019):

I need that too.
I need a git server which collaborate with 2 or more different organizations. They should NOT to see each other (including their org/repo) at all.

@brallow commented on GitHub (Jun 12, 2019): I need that too. I need a git server which collaborate with 2 or more different organizations. They should NOT to see each other (including their org/repo) at all.

GiteaMirror commented

2025-11-02 04:09:02 -06:00

@sapk commented on GitHub (Jun 12, 2019):

@brallow this should be available in the 1.8.0+ versions. You can try the latest stable version : https://github.com/go-gitea/gitea/releases/tag/v1.8.2

@sapk commented on GitHub (Jun 12, 2019): @brallow this should be available in the 1.8.0+ versions. You can try the latest stable version : https://github.com/go-gitea/gitea/releases/tag/v1.8.2

GiteaMirror referenced this issue

2025-11-02 11:59:39 -06:00

[PR #1674] [MERGED] Adding #issuecomment to the URL in E-Mail notifications #15987

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#1669