Read-only namespaces

On GitLab.com, a top-level namespace is placed in a read-only state when it either:

While a namespace is in a read-only state, a banner appears at the top of the page.

Your ability to write new data to read-only namespaces is restricted. For more information, see Restricted actions.

Remove the read-only state

To restore a namespace to its standard state, you can:

For exceeded free user limits:
- Reduce the number of members in your namespace.
- Start a free trial, which includes an unlimited number of members.
- Purchase a paid tier.

Feature	Action restricted
Container registry	Create, edit, and delete cleanup policies Push an image to the container registry
Merge Requests	Create and update an MR
Package registry	Publish a package
Repositories	Add tags Create new branches Create and update commit status Push and force push to non-protected branches Push and force push to protected branches Upload files Create merge requests
CI/CD	Create, edit, admin, and run pipelines Create, edit, admin, and run builds Create and edit admin environments Create and edit admin deployments Create and edit admin clusters Create and edit admin releases
Namespaces	For exceeded free user limits: Invite new users

When you try to execute a restricted action in a read-only namespace, you might get a 404 error.

Edit this page to fix an error or add an improvement in a merge request.

Create an issue to suggest an improvement to this page.

Create an issue if there's something you don't like about this feature.

Propose functionality by submitting a feature request.

View pricing to see all GitLab tiers and features, or to upgrade.

Try GitLab for free with access to all features for 30 days.

If you didn't find what you were looking for, search the docs.

If you want help with something specific and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).