> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gitlocalize.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Visibility

> How a repository's visibility on GitHub determines who can see and contribute to it on GitLocalize.

A repository on GitLocalize keeps the visibility it has on GitHub. This is not configurable
separately.

| On GitHub | On GitLocalize | Who can contribute |
| --------- | -------------- | ------------------ |
| Private   | Private        | Team members only  |
| Public    | Public         | Anyone             |

## Private repositories

Someone who is not on the team gets a 404 — the repository does not appear to exist:

<Frame>
  <img src="https://mintcdn.com/gitlocalize/lskpih6euvpzy4qL/images/private-repository-404.png?fit=max&auto=format&n=lskpih6euvpzy4qL&q=85&s=62c7f1145eb1b3fbe4b9da3e4ed7fd6c" alt="A 404 error shown to a user without access" width="397" height="317" data-path="images/private-repository-404.png" />
</Frame>

There is no request-access flow, so [adding translators to the team](/roles) is a prerequisite
rather than a convenience. Nobody can find their way to a private repository on their own.

## Public repositories

Anyone can open a public repository and translate in it without being on the team, which is what
makes crowdsourced translation possible.

Roles still govern what those contributors can do. Without an Admin or Moderator role they can create
review requests but not pull requests, so community contributions are reviewed before reaching the
repository. See [Reviews and pull requests](/reviews).