Update user limit doc articles
Summary
As of 2022-12-28 the 5 user limit is enabled for any net new namespaces (parent level groups) created on GitLab.com and we've started to notify existing namespaces that the limit will be implemented in the near future.
To account for this we should make the following updates to our user limit documentation.
Checklist
-
Update Free user limit article -
Index Read only namespaces -
Add Read only namespaces to the global nav
Changes to make
- On docs.gitlab.com/ee/user/free_user_limit.html we should update the following copy:
From:
A five-user limit applies to top-level namespaces with private visibility on GitLab SaaS. This limit is being rolled out gradually, and impacted users will be notified in GitLab.com at least 60 days before the limit is applied.
When the five-user limit is applied, top-level private namespaces exceeding the user limit are placed in a read-only state. These namespaces cannot write new data to repositories, Git Large File Storage (LFS), packages, or registries.
To:
A five-user limit applies to newly created top-level namespaces with private visibility on GitLab SaaS. For existing namespaces, this limit is being rolled out gradually, and impacted users will be notified in GitLab.com at least 60 days before the limit is applied.
When the five-user limit is applied, top-level private namespaces exceeding the user limit are placed in a read-only state. These namespaces cannot write new data to repositories, Git Large File Storage (LFS), packages, or registries. You can learn more about what is included vs excluded in the read-only state here[hyperlink to read-only state doc article]
- We should make the read-only state article visible in the doc navigation and allow it to be index by search engines
- We should update the icons on the user limit article so does not list
all tiers
but instead only listsFree"
.