Read-only namespaces and projects

Read-only namespaces

  • Tier: Free
  • Offering: GitLab.com

A namespace is placed in a read-only state when it exceeds the free user limit, and when the namespace visibility is private.

To remove the read-only state of a namespace and its projects, you can:

Restricted actions

When a namespace is in a read-only state, you cannot execute the actions listed in the following table. If you try to execute a restricted action, you might get a 404 error.

FeatureAction restricted
Container registryCreate, edit, and delete cleanup policies.
Push an image to the container registry.
Merge requestsCreate and update a merge request.
Package registryPublish a package.
CI/CDCreate, edit, administer, and run pipelines.
Create, edit, administer, and run builds.
Create and edit admin environments.
Create and edit admin deployments.
Create and edit admin clusters.
Create and edit admin releases.
NamespacesFor exceeded free user limits: Invite new users.

Read-only projects

  • Tier: Free, Premium, Ultimate

A project is placed in a read-only state when it exceeds the allocated storage limit on the:

  • Free tier, when any project in the namespace is over the free limit.
  • Premium and Ultimate tiers, when any project in the namespace is over the fixed project limit.

Restricted actions

When a project is read-only due to storage limits, you can’t push or add large files (LFS) to the project’s repository. A banner at the top of the project or namespace page indicates the read-only status.