Gitea: [Feature] Hide Users and Orgs from public

[mmarif4u]

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.

[adilinden]

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.

[NetOperatorWibby]

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.

[agaida]

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

[ghost]

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.

[SoulSeekkor]

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.

[mcnesium]

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.

[stale[bot]]

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.

[markg85]

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.

[SoulSeekkor]

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.

[stevoh6]

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.

[lunny]

Private organization has been implemented and merged into master.

[markg85]

It apparently is this commit: https://github.com/go-gitea/gitea/commit/64ce159a6eacc81962d07a8f5ef7f69c17365363

Someone should probably close this issue.

[stevoh6]

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 ?

[lafriks]

@stevoh6 private organization option will be in 1.8.0

Users will still be visible to all

[brallow]

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.

[sapk]

@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