• Define which roles can create projects
• Restrict project deletion to administrators
• Deletion protection
  • Retention period
  • Delayed project deletion
  • Delayed group deletion
  • Override defaults and delete immediately
• Configure project visibility defaults
• Configure snippet visibility defaults
• Configure group visibility defaults
• Restrict visibility levels
• Configure enabled Git access protocols
• Customize Git clone URL for HTTP(S)
• Configure defaults for RSA, DSA, ECDSA, ED25519, ECDSA_SK, ED25519_SK SSH keys
• Enable project mirroring
• Configure globally-allowed IP address ranges

Control access and visibility

GitLab enables users with administrator access to enforce specific controls on branches, projects, snippets, groups, and more.

Prerequisites:

• You must be an administrator.

To access the visibility and access control options:

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.

Define which roles can create projects

You can add project creation protections to your instance. These protections define which roles can add projects to a group on the instance. To alter which roles have permission to create projects:

Prerequisites:

• You must be an administrator.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. For Default project creation protection, select the desired roles:
   • No one.
   • Administrators.
   • Owners.
   • Maintainers.
   • Developers and Maintainers.
5. Select Save changes.

Restrict project deletion to administrators

Prerequisites:

• You must be an administrator, or have the Owner role in a project.

To restrict project deletion to only administrators:

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. Scroll to:
   • (GitLab 15.1 and later) Allowed to delete projects, and select Administrators.
   • (GitLab 15.0 and earlier) Default project deletion protection, and select Only admins can delete project.
5. Select Save changes.

To disable the restriction:

1. Select Owners and administrators.
2. Select Save changes.

Deletion protection

These protections help guard against accidental deletion of groups and projects on your instance.

Retention period

Groups and projects remain restorable during the retention period you define. By default, this is 7 days, but you can change it. If you set the retention period to 0 days, GitLab removes deleted groups and projects immediately. You can’t restore them.

In GitLab 15.1 and later, the retention period must be between 1 and 90 days. If, before the 15.1 update, you set the retention period to 0 days, the next time you change any application setting, GitLab:

• Changes the retention period to 1 day.
• Disables deletion protection.

Delayed project deletion

Prerequisites:

• You must be an administrator.
• You must enable delayed project deletion for groups before you can enable it for projects. Deletion protection is not available for projects only.
• When disabled, GitLab 15.1 and later enforces this delayed-deletion setting, and you can’t override it.

To configure delayed project deletion:

Delayed group deletion

Groups remain restorable if the retention period is 1 or more days.

In GitLab 16.0 and later, the Keep deleted option is removed, and delayed group deletion is the default.

To enable delayed group deletion in GitLab 15:

1. GitLab 15.11 only: enable the always_perform_delayed_deletion feature flag.
2. On the left sidebar, at the bottom, select Admin.
3. Select Settings > General.
4. Expand Visibility and access controls.
5. For Deletion projection, select Keep deleted.
6. Select Save changes.

Override defaults and delete immediately

To override the delay, and immediately delete a project marked for removal:

1. Restore the project.
2. Delete the project as described in the Administering Projects page.

Configure project visibility defaults

To set the default visibility levels for new projects:

Prerequisites:

• You must be an administrator.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. Select the desired default project visibility:
   • Private - Grant project access explicitly to each user. If this project is part of a group, grants access to members of the group.
   • Internal - Any authenticated user, except external users, can access the project.
   • Public - Any user can access the project without any authentication.
5. Select Save changes.

Configure snippet visibility defaults

To set the default visibility levels for new snippets:

Prerequisites:

• You must be an administrator.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. For Default snippet visibility, select your desired visibility level:
   • Private.
   • Internal. This setting is disabled for new projects, groups, and snippets on GitLab.com. Existing snippets using the Internal visibility setting keep this setting. To learn more about this change, see issue 12388.
   • Public.
5. Select Save changes.

Configure group visibility defaults

To set the default visibility levels for new groups:

Prerequisites:

• You must be an administrator.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. For Default group visibility, select your desired visibility level:
   • Private - Only members can view the group and its projects.
   • Internal - Any authenticated user, except external users, can view the group and any internal projects.
   • Public - Authentication is not required to view the group and any public projects.
5. Select Save changes.

For more details on group visibility, see Group visibility.

Restrict visibility levels

When restricting visibility levels, consider how these restrictions interact with permissions for subgroups and projects that inherit their visibility from the item you’re changing.

To restrict visibility levels for groups, projects, snippets, and selected pages:

Prerequisites:

• You must be an administrator.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. For Restricted visibility levels, select the desired visibility levels to restrict.
   • If you restrict the Public level:
     • Only administrators can create public groups, projects, and snippets.
     • User profiles are visible to only authenticated users through the Web interface.
     • User attributes through the GraphQL API are:
       • Not visible in GitLab 15.1 and later.
       • Visible only to authenticated users in GitLab 15.0.
   • If you restrict the Internal level:
     • Only administrators can create internal groups, projects, and snippets.
   • If you restrict the Private level:
     • Only administrators can create private groups, projects, and snippets.
5. Select Save changes.

Configure enabled Git access protocols

With GitLab access restrictions, you can select the protocols users can use to communicate with GitLab. Disabling an access protocol does not block port access to the server itself. The ports used for the protocol, SSH or HTTP(S), are still accessible. The GitLab restrictions apply at the application level.

GitLab allows Git actions only for the protocols you select:

• If you enable both SSH and HTTP(S), users can choose either protocol.
• If you enable only one protocol, project pages show only the allowed protocol’s URL, with no option to change it.

To specify the enabled Git access protocols for all projects on your instance:

Prerequisites:

• You must be an administrator.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. For Enabled Git access protocols, select your desired protocols:
   • Both SSH and HTTP(S).
   • Only SSH.
   • Only HTTP(S).
5. Select Save changes.

Customize Git clone URL for HTTP(S)

You can customize project Git clone URLs for HTTP(S), which affects the clone panel shown to users on a project’s page. For example, if:

• Your GitLab instance is at https://example.com, then project clone URLs are like https://example.com/foo/bar.git.
• You want clone URLs that look like https://git.example.com/gitlab/foo/bar.git instead, you can set this setting to https://git.example.com/gitlab/.

To specify a custom Git clone URL for HTTP(S) in gitlab.rb, set a new value for gitlab_rails['gitlab_ssh_host']. To specify a new value from the GitLab UI:

Prerequisites:

• You must be an administrator.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. Enter a root URL for Custom Git clone URL for HTTP(S).
5. Select Save changes.

Configure defaults for RSA, DSA, ECDSA, ED25519, ECDSA_SK, ED25519_SK SSH keys

These options specify the permitted types and lengths for SSH keys.

To specify a restriction for each key type:

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. Go to RSA SSH keys.
5. For each key type, you can allow or prevent their use entirely, or allow only lengths of:
   • At least 1024 bits.
   • At least 2048 bits.
   • At least 3072 bits.
   • At least 4096 bits.
   • At least 1024 bits.
6. Select Save changes.

Enable project mirroring

GitLab enables project mirroring by default. If you disable it, both pull mirroring and push mirroring no longer work in every repository. They can only be re-enabled by an administrator user on a per-project basis.

To allow project maintainers on your instance to configure mirroring per project:

Prerequisites:

• You must be an administrator.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > Repository.
3. Expand Repository mirroring.
4. Select Allow project maintainers to configure repository mirroring.
5. Select Save changes.

Configure globally-allowed IP address ranges

Administrators can combine IP address ranges with IP restrictions per group. Use globally-allowed IP addresses to allow aspects of the GitLab installation to work even when IP address restrictions are set per group.

For example, if the GitLab Pages daemon runs on the 10.0.0.0/24 range, you can specify that range as globally allowed. GitLab Pages can still fetch artifacts from pipelines, even if IP address restrictions for the group don’t include the 10.0.0.0/24 range.

To add a IP address range to the allowlist for a group:

Prerequisites:

• You must be an administrator.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > General.
3. Expand Visibility and access controls.
4. In Globally-allowed IP ranges, provide a list of IP address ranges. This list:
   • Has no limit on the number of IP address ranges.
   • Applies to both SSH or HTTP authorized IP address ranges. You cannot split this list by authorization type.
5. Select Save changes.