From 8e8fc443eb5622e17b6d89f140f0c501eb32bf31 Mon Sep 17 00:00:00 2001 From: lukaesque Date: Sat, 13 Jun 2026 15:49:35 +0200 Subject: [PATCH] clarify who can see private repositories --- content/collaborating/repo-permissions.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/content/collaborating/repo-permissions.md b/content/collaborating/repo-permissions.md index ea4dec9..93bb076 100644 --- a/content/collaborating/repo-permissions.md +++ b/content/collaborating/repo-permissions.md @@ -20,7 +20,7 @@ repository as private. Let's break down what this means: - If your profile's visibility is set to "Limited", _all_ of your non-private repositories will only be visible to logged in users. - If your profile's visibility is set to "Public", _all_ of your non-private repositories will be shown to everyone. -- If you do not want anyone (apart from [your fellow collaborators](https://docs.codeberg.org/collaborating/invite-collaborators/)) +- If you do not want anyone* (apart from [your fellow collaborators](https://docs.codeberg.org/collaborating/invite-collaborators/)) to see your repositories, mark your repository as "Private". The visibility of your profile can be changed in the [Privacy settings](https://codeberg.org/user/settings). @@ -28,11 +28,14 @@ Be careful when you set your profile's visibility to "Limited"; Even if a reposi _not logged in_ will get a [404 error](https://en.wikipedia.org/wiki/HTTP_404) if they try to access your repository — it will seem as if it does not exist at all! + Privacy Settings in Codeberg's User Settings +*Codeberg's Moderation Team and infrastructure administrators can access private repositories as per the [Privacy Policy](https://codeberg.org/Codeberg/org/src/branch/main/PrivacyPolicy.md) + ## Collaborators There are four permission levels: **Read**, **Write**, **Administrator** and **Owner**.