Visibility and permissions
Every list, every number and every statement about where you stand in the project area is filtered to what your account may read. This page explains what follows from that — and what expressly does not.
What the numbers mean
The two numbers above the lists count only what your account may see. They are therefore no statement about the total holding. “53 repositories” means “53 repositories visible to this account”, not “53 in existence”.
Both numbers are worked out afresh on every visit. There is no maintained enumeration in the wiki that could go stale.
Why a missing entry gives nothing away
“No repository” means “none for this account”, not “none in existence”. A project missing from the list either does not exist or has not been released to this account.
The two cases are indistinguishable from outside, and that is deliberate. Were they not, the list would let somebody infer what else exists — which is precisely what the permission is there to prevent.
A role is not the same as access
A project card states either Your project role or Access. The difference is not a matter of wording.
| Statement | Meaning |
|---|---|
| Your project role | You are a member of the project; the role was given to you there. |
| Access | You may do something but are not a member — because the project is publicly readable, for instance. |
Only the first is a membership. Find my projects draws the same distinction: it lists the projects you are a member of, not the ones you may read.
Both statements are information, not permission. What you may actually do is decided in every case by the permission of the namespace concerned.
Related topics
- Projects and repositories (German) — the entry point this page refers to
- Contributing — the ladder of roles and what each rung may do
- Request access — when something you should be able to see is missing