From 632827d03cdee12c1b8cfd1581601fa6c64e08ff Mon Sep 17 00:00:00 2001
From: Suzanne Selhorn <sselhorn@gitlab.com>
Date: Tue, 14 Jan 2025 03:58:24 +0000
Subject: [PATCH] Updating self-managed style
Because we have a new standard
---
doc/administration/admin_area.md | 2 +-
doc/administration/appearance.md | 2 +-
doc/administration/cicd/compute_minutes.md | 2 +-
doc/administration/clusters/kas.md | 4 ++--
doc/administration/get_started.md | 10 +++++-----
doc/administration/gitaly/bundle_uris.md | 2 +-
doc/administration/gitaly/configure_gitaly.md | 2 +-
doc/administration/gitaly/troubleshooting.md | 2 +-
doc/administration/instance_limits.md | 2 +-
doc/administration/integration/diagrams_net.md | 2 +-
doc/administration/integration/terminal.md | 2 +-
doc/administration/lfs/index.md | 2 +-
.../container_registry_metadata_database.md | 2 +-
doc/administration/reporting/spamcheck.md | 2 +-
doc/administration/self_hosted_models/index.md | 2 +-
.../settings/account_and_limit_settings.md | 2 +-
.../settings/import_and_export_settings.md | 2 +-
.../settings/jira_cloud_app_troubleshooting.md | 4 ++--
doc/administration/settings/scim_setup.md | 2 +-
doc/administration/settings/slack_app.md | 2 +-
doc/administration/settings/usage_statistics.md | 2 +-
doc/api/graphql/audit_report.md | 2 +-
doc/api/graphql/branch_rules.md | 2 +-
doc/api/graphql/custom_emoji.md | 2 +-
.../epic_work_items_api_migration_guide.md | 2 +-
doc/api/graphql/sample_issue_boards.md | 2 +-
doc/api/graphql/users_example.md | 2 +-
doc/api/group_webhooks.md | 4 ++--
doc/api/groups.md | 2 +-
doc/api/merge_request_approvals.md | 2 +-
doc/api/project_import_export.md | 2 +-
doc/api/project_webhooks.md | 4 ++--
doc/api/saml.md | 2 +-
doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md | 2 +-
doc/ci/components/index.md | 2 +-
doc/ci/migration/github_actions.md | 2 +-
doc/ci/pipelines/merge_trains.md | 2 +-
doc/ci/runners/runner_fleet_dashboard_groups.md | 2 +-
doc/development/activitypub/actors/index.md | 2 +-
doc/development/activitypub/actors/releases.md | 2 +-
doc/development/activitypub/index.md | 2 +-
doc/development/ai_features/index.md | 2 +-
doc/development/cloud_connector/configuration.md | 2 +-
doc/development/cloud_connector/index.md | 12 ++++++------
.../configure-dev-env-gdk-in-a-box.md | 2 +-
.../first_contribution/configure-dev-env-gdk.md | 2 +-
.../contributing/first_contribution/index.md | 2 +-
doc/development/contributing/index.md | 2 +-
.../documentation/graphql_styleguide.md | 2 +-
.../documentation/styleguide/index.md | 2 +-
.../internal_api/internal_api_allowed.md | 2 +-
doc/development/ruby_upgrade.md | 2 +-
.../gitlab_instrumentation_for_opentelemetry.md | 2 +-
doc/integration/akismet.md | 2 +-
doc/integration/arkose.md | 2 +-
doc/integration/gitpod.md | 4 ++--
doc/integration/jenkins.md | 2 +-
doc/integration/jira/configure.md | 2 +-
doc/integration/saml.md | 4 ++--
doc/integration/sourcegraph.md | 4 ++--
doc/operations/feature_flags.md | 4 ++--
doc/security/email_verification.md | 2 +-
doc/security/hardening.md | 2 +-
doc/security/hardening_nist_800_53.md | 2 +-
doc/security/index.md | 2 +-
doc/security/responding_to_security_incidents.md | 4 ++--
doc/security/two_factor_authentication.md | 2 +-
doc/subscriptions/bronze_starter.md | 2 +-
.../cloud_deployments/auto_devops_with_gke.md | 2 +-
doc/topics/offline/quick_start_guide.md | 4 ++--
...lab_runner_fleet_config_and_best_practices.md | 2 +-
.../observability_django_tutorial.md | 2 +-
.../observability_dotnet_tutorial.md | 2 +-
doc/update/background_migrations.md | 2 +-
.../configuration/offline_configuration.md | 2 +-
.../configuration/offline_configuration.md | 2 +-
.../container_scanning/index.md | 2 +-
.../configuration/offline_configuration.md | 2 +-
.../dependency_scanning/index.md | 2 +-
.../application_security/iac_scanning/index.md | 2 +-
.../policies/merge_request_approval_policies.md | 2 +-
doc/user/application_security/sast/index.md | 2 +-
.../secret_detection/pipeline/index.md | 2 +-
.../secret_detection/push_protection_tutorial.md | 2 +-
doc/user/clusters/agent/install/index.md | 2 +-
doc/user/clusters/agent/work_with_agent.md | 2 +-
doc/user/clusters/environments.md | 2 +-
doc/user/clusters/management_project.md | 2 +-
.../compliance_standards_adherence_dashboard.md | 6 +++---
.../license_scanning_of_cyclonedx_files/index.md | 2 +-
doc/user/custom_roles.md | 2 +-
.../get_started/getting_started_gitlab_duo.md | 2 +-
doc/user/gitlab_duo/use_cases.md | 2 +-
doc/user/gitlab_duo_chat/index.md | 2 +-
doc/user/group/import/index.md | 10 +++++-----
doc/user/group/index.md | 2 +-
doc/user/group/manage.md | 2 +-
doc/user/group/saml_sso/group_sync.md | 6 +++---
doc/user/group/saml_sso/index.md | 8 ++++----
doc/user/group/saml_sso/scim_setup.md | 2 +-
doc/user/group/saml_sso/troubleshooting_scim.md | 6 +++---
doc/user/group/value_stream_analytics/index.md | 2 +-
doc/user/infrastructure/clusters/index.md | 2 +-
doc/user/infrastructure/iac/terraform_state.md | 2 +-
doc/user/okrs.md | 2 +-
doc/user/organization/index.md | 2 +-
.../authenticate_with_container_registry.md | 2 +-
.../container_registry/cosign_tutorial.md | 2 +-
doc/user/packages/container_registry/index.md | 4 ++--
doc/user/packages/nuget_repository/index.md | 2 +-
doc/user/permissions.md | 16 ++++++++--------
doc/user/profile/account/delete_account.md | 2 +-
.../profile/account/two_factor_authentication.md | 8 ++++----
doc/user/profile/achievements.md | 2 +-
doc/user/profile/personal_access_tokens.md | 2 +-
doc/user/profile/service_accounts.md | 2 +-
.../project/clusters/gitlab_managed_clusters.md | 2 +-
doc/user/project/deploy_boards.md | 2 +-
doc/user/project/import/github.md | 2 +-
doc/user/project/import/index.md | 2 +-
.../integrations/gitlab_slack_application.md | 2 +-
doc/user/project/integrations/index.md | 2 +-
.../project/integrations/slack_slash_commands.md | 2 +-
doc/user/project/issue_board.md | 2 +-
doc/user/project/issues/managing_issues.md | 2 +-
.../project/merge_requests/approvals/settings.md | 4 ++--
doc/user/project/merge_requests/index.md | 2 +-
.../milestones/burndown_and_burnup_charts.md | 2 +-
doc/user/project/pages/index.md | 2 +-
doc/user/project/repository/mirror/index.md | 2 +-
doc/user/project/settings/import_export.md | 2 +-
doc/user/project/time_tracking.md | 2 +-
doc/user/project/web_ide/index.md | 2 +-
doc/user/project/wiki/index.md | 2 +-
doc/user/search/advanced_search.md | 2 +-
doc/user/snippets.md | 2 +-
doc/user/version.md | 2 +-
137 files changed, 181 insertions(+), 181 deletions(-)
diff --git a/doc/administration/admin_area.md b/doc/administration/admin_area.md
index 975af7cc4171..c05e40981bd4 100644
--- a/doc/administration/admin_area.md
+++ b/doc/administration/admin_area.md
@@ -29,7 +29,7 @@ Only administrators on GitLab self-managed or GitLab Dedicated can access the **
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/419540) in GitLab 16.10 [with a flag](feature_flags.md) named `ui_for_organizations`. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](feature_flags.md) named `ui_for_organizations`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](feature_flags.md) named `ui_for_organizations`.
On GitLab.com and GitLab Dedicated, this feature is not available.
This feature is not ready for production use.
diff --git a/doc/administration/appearance.md b/doc/administration/appearance.md
index d1cd3a793770..5ef99bd521e8 100644
--- a/doc/administration/appearance.md
+++ b/doc/administration/appearance.md
@@ -99,7 +99,7 @@ You can add also add a [customized help message](settings/help_page.md) below th
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144484) in GitLab 16.10.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](feature_flags.md) named `disable_preferred_language_cookie`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](feature_flags.md) named `disable_preferred_language_cookie`.
On GitLab.com and GitLab Dedicated, this feature is not available.
You can remove the cookie-based language selector from the footer of the sign-in and register pages by enabling the `disable_preferred_language_cookie` feature flag.
diff --git a/doc/administration/cicd/compute_minutes.md b/doc/administration/cicd/compute_minutes.md
index 91c232345418..ba316339c74d 100644
--- a/doc/administration/cicd/compute_minutes.md
+++ b/doc/administration/cicd/compute_minutes.md
@@ -18,7 +18,7 @@ Administrators can limit the amount of time that projects can use to run jobs on
is tracked with a [compute minutes quota](../../ci/pipelines/compute_minutes.md).
[Project runners](../../ci/runners/runners_scope.md#project-runners) are not subject to the compute quota.
-On self-managed GitLab instances:
+On GitLab Self-Managed:
- Compute quotas are disabled by default.
- Administrators can [assign more compute minutes](#set-the-compute-quota-for-a-group)
diff --git a/doc/administration/clusters/kas.md b/doc/administration/clusters/kas.md
index f24fde1eff30..15f3d24ffcf4 100644
--- a/doc/administration/clusters/kas.md
+++ b/doc/administration/clusters/kas.md
@@ -16,7 +16,7 @@ manage the [GitLab agent for Kubernetes](https://gitlab.com/gitlab-org/cluster-i
The KAS acronym refers to the former name, `Kubernetes agent server`.
The agent server for Kubernetes is installed and available on GitLab.com at `wss://kas.gitlab.com`.
-If you use self-managed GitLab, by default the agent server is installed and available.
+If you use GitLab Self-Managed, by default the agent server is installed and available.
## Installation options
@@ -204,7 +204,7 @@ To fix this issue, ensure that the paths are correct.
### `dial tcp <GITLAB_INTERNAL_IP>:443: connect: connection refused`
-If you are running self-managed GitLab and:
+If you are running GitLab Self-Managed and:
- The instance isn't running behind an SSL-terminating proxy.
- The instance doesn't have HTTPS configured on the GitLab instance itself.
diff --git a/doc/administration/get_started.md b/doc/administration/get_started.md
index d5a58f879bce..1cd38c4988cf 100644
--- a/doc/administration/get_started.md
+++ b/doc/administration/get_started.md
@@ -67,7 +67,7 @@ You may need to import projects from external sources like GitHub, Bitbucket, or
### Popular project imports
-- [GitHub Enterprise to self-managed GitLab](../integration/github.md)
+- [GitHub Enterprise to GitLab Self-Managed](../integration/github.md)
- [Bitbucket Server](../user/project/import/bitbucket_server.md)
For assistance with these data types, contact your GitLab account manager or GitLab Support about our professional migration services.
@@ -207,14 +207,14 @@ Learn more about the [data types Geo replicates](../administration/geo/replicati
## Support for GitLab self-managed
-GitLab provides support for self-managed GitLab through different channels.
+GitLab provides support for GitLab Self-Managed through different channels.
- Priority support: [Premium and Ultimate](https://about.gitlab.com/pricing/) self-managed customers receive priority support with tiered response times.
Learn more about [upgrading to priority support](https://about.gitlab.com/support/#upgrading-to-priority-support).
- Live upgrade assistance: Get one-on-one expert guidance during a production upgrade. With your **priority support plan**,
you're eligible for a live, scheduled screen-sharing session with a member of our support team.
-To get assistance for self-managed GitLab:
+To get assistance for GitLab Self-Managed:
- Use the GitLab documentation for self-service support.
- Join the [GitLab Forum](https://forum.gitlab.com/) for community support.
@@ -240,14 +240,14 @@ To get assistance for GitLab SaaS:
- [Account or sign-in issues](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000803379)
- Subscribe to [the status page](https://status.gitlab.com/) for the latest on GitLab performance or service interruptions.
-## API and rate limits for self-managed GitLab
+## API and rate limits for GitLab Self-Managed
Rate limits prevent denial-of-service or brute-force attacks. In most cases, you can reduce the load on your application
and infrastructure by limiting the rate of requests from a single IP address.
Rate limits also improve the security of your application.
-### Configure rate limits for self-managed GitLab
+### Configure rate limits for GitLab Self-Managed
You can make changes to your default rate limits from the **Admin** area. For more information about configuration, see the [**Admin** area page](../security/rate_limits.md#configurable-limits).
diff --git a/doc/administration/gitaly/bundle_uris.md b/doc/administration/gitaly/bundle_uris.md
index c8fab9fc311d..f1576716c648 100644
--- a/doc/administration/gitaly/bundle_uris.md
+++ b/doc/administration/gitaly/bundle_uris.md
@@ -12,7 +12,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/8939) in GitLab 17.0 [with a flag](../../administration/feature_flags.md) named `gitaly_bundle_uri`. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available.
+On GitLab Self-Managed, by default this feature is not available.
To make it available, an administrator can [enable the feature flag](../feature_flags.md)
named `gitaly_bundle_uri`.
On GitLab.com and GitLab Dedicated, this feature is not available. This feature
diff --git a/doc/administration/gitaly/configure_gitaly.md b/doc/administration/gitaly/configure_gitaly.md
index 08cd370be175..ca5506557b84 100644
--- a/doc/administration/gitaly/configure_gitaly.md
+++ b/doc/administration/gitaly/configure_gitaly.md
@@ -1118,7 +1118,7 @@ Configure the `cat-file` cache in the [Gitaly configuration file](reference.md).
> - [Enabled by default](https://gitlab.com/gitlab-org/gitaly/-/merge_requests/6876) on self-managed and GitLab Dedicated in GitLab 17.0.
FLAG:
-On self-managed GitLab, by default this feature is available. To hide the feature,
+On GitLab Self-Managed, by default this feature is available. To hide the feature,
an administrator can [disable the feature flag](../feature_flags.md) named `gitaly_gpg_signing`.
On GitLab.com, this feature is not available. On GitLab Dedicated, this feature is available.
diff --git a/doc/administration/gitaly/troubleshooting.md b/doc/administration/gitaly/troubleshooting.md
index 57cba70caff1..c8ee6f5525a5 100644
--- a/doc/administration/gitaly/troubleshooting.md
+++ b/doc/administration/gitaly/troubleshooting.md
@@ -519,7 +519,7 @@ go tool trace heap.bin
> - [Introduced](https://gitlab.com/gitlab-org/gitaly/-/issues/5700) in GitLab 16.9 [with a flag](../../administration/feature_flags.md) named `log_git_traces`. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md)
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md)
named `log_git_traces`. On GitLab.com, this feature is available but can be configured by GitLab.com administrators only. On GitLab Dedicated, this feature is not available.
You can profile Git operations that Gitaly performs by sending additional information about Git operations to Gitaly logs. With this information, users have more insight
diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md
index e4e44e7667aa..ace848b918e2 100644
--- a/doc/administration/instance_limits.md
+++ b/doc/administration/instance_limits.md
@@ -705,7 +705,7 @@ If the limit value is set to zero, the limit is disabled.
GitLab SaaS subscribers have different limits defined per plan, affecting all projects using that plan.
-Self-managed GitLab Premium and Ultimate limits are defined by a default plan that affects all projects:
+Premium and Ultimate limits on GitLab Self-Managed are defined by a default plan that affects all projects:
| Runner scope | Default value |
|---------------------------------|---------------|
diff --git a/doc/administration/integration/diagrams_net.md b/doc/administration/integration/diagrams_net.md
index 43d77587a32b..7940c0f526ba 100644
--- a/doc/administration/integration/diagrams_net.md
+++ b/doc/administration/integration/diagrams_net.md
@@ -19,7 +19,7 @@ The diagram editor is available in both the plain text editor and the rich text
On GitLab.com, this integration is enabled for all SaaS users and does not require any additional configuration.
-On self-managed GitLab, you can choose to integrate with the free [diagrams.net](https://www.drawio.com/)
+On GitLab Self-Managed, you can choose to integrate with the free [diagrams.net](https://www.drawio.com/)
website, or use a self-managed diagrams.net site in offline environments.
To set up the integration on a self-managed instance, you must:
diff --git a/doc/administration/integration/terminal.md b/doc/administration/integration/terminal.md
index b614beb0d674..f8e180f516d4 100644
--- a/doc/administration/integration/terminal.md
+++ b/doc/administration/integration/terminal.md
@@ -16,7 +16,7 @@ WARNING:
This feature was [deprecated](https://gitlab.com/groups/gitlab-org/configure/-/epics/8) in GitLab 14.5.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `certificate_based_clusters`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `certificate_based_clusters`.
- Read more about the non-deprecated [Web Terminals accessible through the Web IDE](../../user/project/web_ide/index.md).
- Read more about the non-deprecated [Web Terminals accessible from a running CI job](../../ci/interactive_web_terminal/index.md).
diff --git a/doc/administration/lfs/index.md b/doc/administration/lfs/index.md
index a00c5384983b..66cad72c2052 100644
--- a/doc/administration/lfs/index.md
+++ b/doc/administration/lfs/index.md
@@ -11,7 +11,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed
-This page contains information about configuring Git LFS in self-managed GitLab instances.
+This page contains information about configuring Git LFS on GitLab Self-Managed.
For user documentation about Git LFS, see [Git Large File Storage](../../topics/git/lfs/index.md).
Prerequisites:
diff --git a/doc/administration/packages/container_registry_metadata_database.md b/doc/administration/packages/container_registry_metadata_database.md
index 924a5d29cd15..28a0d4873a64 100644
--- a/doc/administration/packages/container_registry_metadata_database.md
+++ b/doc/administration/packages/container_registry_metadata_database.md
@@ -10,7 +10,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/423459) in GitLab 16.4 as a [beta feature](../../policy/development_stages_support.md) for self-managed GitLab instances.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/423459) in GitLab 16.4 as a [beta feature](../../policy/development_stages_support.md) for GitLab Self-Managed.
> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/423459) in GitLab 17.3.
The metadata database enables many new registry features, including
diff --git a/doc/administration/reporting/spamcheck.md b/doc/administration/reporting/spamcheck.md
index 4c3645efecd9..ac281e3407d9 100644
--- a/doc/administration/reporting/spamcheck.md
+++ b/doc/administration/reporting/spamcheck.md
@@ -15,7 +15,7 @@ Spamcheck is available to all tiers, but only on instances using GitLab Enterpri
[Spamcheck](https://gitlab.com/gitlab-org/gl-security/security-engineering/security-automation/spam/spamcheck) is an anti-spam engine
developed by GitLab originally to combat rising amount of spam in GitLab.com,
-and later made public to be used in self-managed GitLab instances.
+and later made public to be used in GitLab Self-Managed instances.
## Enable Spamcheck
diff --git a/doc/administration/self_hosted_models/index.md b/doc/administration/self_hosted_models/index.md
index 55b1e81a15a8..2b9bb7a9a45d 100644
--- a/doc/administration/self_hosted_models/index.md
+++ b/doc/administration/self_hosted_models/index.md
@@ -48,7 +48,7 @@ The configuration for self-hosted models is different to the default configurati
that uses GitLab external AI vendors.
NOTE:
-Both of the following configuration types are for self-managed GitLab instances.
+Both of the following configuration types are for GitLab Self-Managed instances.
### Self-hosted AI gateway and LLMs
diff --git a/doc/administration/settings/account_and_limit_settings.md b/doc/administration/settings/account_and_limit_settings.md
index 9ec99601b630..0f55439d5bc9 100644
--- a/doc/administration/settings/account_and_limit_settings.md
+++ b/doc/administration/settings/account_and_limit_settings.md
@@ -425,7 +425,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/423302) in GitLab 16.7 [with a flag](../feature_flags.md) named `ui_for_organizations`. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../feature_flags.md) named `ui_for_organizations`. On GitLab.com and GitLab Dedicated, this feature is not available. This feature is not ready for production use.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../feature_flags.md) named `ui_for_organizations`. On GitLab.com and GitLab Dedicated, this feature is not available. This feature is not ready for production use.
By default, users can create organizations. GitLab administrators can prevent users from creating organizations.
diff --git a/doc/administration/settings/import_and_export_settings.md b/doc/administration/settings/import_and_export_settings.md
index cf20671709c3..8f97d710cd34 100644
--- a/doc/administration/settings/import_and_export_settings.md
+++ b/doc/administration/settings/import_and_export_settings.md
@@ -203,7 +203,7 @@ The default job limit is:
- For the GitHub importer, 1000.
- For the Bitbucket Cloud and Bitbucket Server importer, 100. The Bitbucket importers have a low default limit because
- we haven't yet determined a good default limit. Administrators of self-managed GitLab instances should experiment with
+ we haven't yet determined a good default limit. Administrators of GitLab Self-Managed instances should experiment with
a higher limit.
To modify this setting:
diff --git a/doc/administration/settings/jira_cloud_app_troubleshooting.md b/doc/administration/settings/jira_cloud_app_troubleshooting.md
index 52605246d828..b84d5e82b9f4 100644
--- a/doc/administration/settings/jira_cloud_app_troubleshooting.md
+++ b/doc/administration/settings/jira_cloud_app_troubleshooting.md
@@ -129,7 +129,7 @@ Depending on how you installed the app, you might want to check the following:
- If you [installed the app manually](jira_cloud_app.md#install-the-gitlab-for-jira-cloud-app-manually):
- Ask [Jira Cloud Support](https://support.atlassian.com/jira-software-cloud/) to verify that Jira can connect to your
- self-managed GitLab instance.
+ GitLab Self-Managed instance.
- [Reinstall the app](jira_cloud_app.md#install-the-gitlab-for-jira-cloud-app-manually). This method might remove all [synced data](../../integration/jira/connect-app.md#gitlab-data-synced-to-jira) from the [Jira development panel](../../integration/jira/development_panel.md).
## Error: `Failed to update the GitLab instance`
@@ -223,7 +223,7 @@ To locate the relevant log entries in Kibana, either:
For the first log:
- `json.status` is `422 Unprocessable Entity`.
-- `json.params.value` should match the self-managed GitLab URL `[[FILTERED], {"instance_url"=>"https://gitlab.example.com"}]`.
+- `json.params.value` should match the GitLab Self-Managed URL `[[FILTERED], {"instance_url"=>"https://gitlab.example.com"}]`.
For the second log, you might have one of the following scenarios:
diff --git a/doc/administration/settings/scim_setup.md b/doc/administration/settings/scim_setup.md
index 0e68c9b06e83..67d62c0a365a 100644
--- a/doc/administration/settings/scim_setup.md
+++ b/doc/administration/settings/scim_setup.md
@@ -4,7 +4,7 @@ group: Provision
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
-# Configure SCIM for self-managed GitLab instances
+# Configure SCIM for GitLab Self-Managed
DETAILS:
**Tier:** Premium, Ultimate
diff --git a/doc/administration/settings/slack_app.md b/doc/administration/settings/slack_app.md
index 3fe557b02018..6455db033310 100644
--- a/doc/administration/settings/slack_app.md
+++ b/doc/administration/settings/slack_app.md
@@ -16,7 +16,7 @@ NOTE:
This page contains administrator documentation for the GitLab for Slack app. For user documentation, see [GitLab for Slack app](../../user/project/integrations/gitlab_slack_application.md).
The GitLab for Slack app distributed through the Slack App Directory only works with GitLab.com.
-On self-managed GitLab, you can create your own copy of the GitLab for Slack app from a [manifest file](https://api.slack.com/reference/manifests#creating_apps) and configure your instance.
+On GitLab Self-Managed, you can create your own copy of the GitLab for Slack app from a [manifest file](https://api.slack.com/reference/manifests#creating_apps) and configure your instance.
The app is a private one-time copy installed in your Slack workspace only and not distributed through the Slack App Directory. To have the [GitLab for Slack app](../../user/project/integrations/gitlab_slack_application.md) on your self-managed instance, you must enable the integration.
diff --git a/doc/administration/settings/usage_statistics.md b/doc/administration/settings/usage_statistics.md
index 15fbf7e7340b..05503c0a6e23 100644
--- a/doc/administration/settings/usage_statistics.md
+++ b/doc/administration/settings/usage_statistics.md
@@ -115,7 +115,7 @@ for all authenticated users, and on the **Admin** area pages. The statuses are:
### Request flow example
The following example shows a basic request/response flow between a
-self-managed GitLab instance and the GitLab Version Application:
+GitLab Self-Managed instance and the GitLab Version Application:
```mermaid
sequenceDiagram
diff --git a/doc/api/graphql/audit_report.md b/doc/api/graphql/audit_report.md
index 68eeb0dd5939..3ba63f27cfa5 100644
--- a/doc/api/graphql/audit_report.md
+++ b/doc/api/graphql/audit_report.md
@@ -21,7 +21,7 @@ You can use GraphiQL to query information about a subset of users.
1. Open GraphiQL:
- For GitLab.com, use: `https://gitlab.com/-/graphql-explorer`
- - For self-managed GitLab, use: `https://gitlab.example.com/-/graphql-explorer`
+ - For GitLab Self-Managed, use: `https://gitlab.example.com/-/graphql-explorer`
1. Copy the following text and paste it in the left window.
This query searches for a subset of users by username. Alternately, you can use their
[Global ID](../../development/api_graphql_styleguide.md#global-ids).
diff --git a/doc/api/graphql/branch_rules.md b/doc/api/graphql/branch_rules.md
index e60db5703878..70dcf38de707 100644
--- a/doc/api/graphql/branch_rules.md
+++ b/doc/api/graphql/branch_rules.md
@@ -24,7 +24,7 @@ You can use GraphiQL to list the branch rules for a project.
1. Open GraphiQL:
- For GitLab.com, use: `https://gitlab.com/-/graphql-explorer`
- - For self-managed GitLab, use: `https://gitlab.example.com/-/graphql-explorer`
+ - For GitLab Self-Managed, use: `https://gitlab.example.com/-/graphql-explorer`
1. Copy the following text and paste it in the left window.
This query searches for a project by its full path, for example `gitlab-org/gitlab-docs`.
It requests all configured branch rules for the project.
diff --git a/doc/api/graphql/custom_emoji.md b/doc/api/graphql/custom_emoji.md
index 9a5990b98ba2..f16392fb2231 100644
--- a/doc/api/graphql/custom_emoji.md
+++ b/doc/api/graphql/custom_emoji.md
@@ -50,7 +50,7 @@ You can use GraphiQL to query the emoji for a group.
1. Open GraphiQL:
- For GitLab.com, use: `https://gitlab.com/-/graphql-explorer`
- - For self-managed GitLab, use: `https://gitlab.example.com/-/graphql-explorer`
+ - For GitLab Self-Managed, use: `https://gitlab.example.com/-/graphql-explorer`
1. Copy the following text and paste it in the left window.
In this query, `gitlab-org` is the group path.
diff --git a/doc/api/graphql/epic_work_items_api_migration_guide.md b/doc/api/graphql/epic_work_items_api_migration_guide.md
index 3e6310923587..ca27398a4e26 100644
--- a/doc/api/graphql/epic_work_items_api_migration_guide.md
+++ b/doc/api/graphql/epic_work_items_api_migration_guide.md
@@ -59,7 +59,7 @@ around with existing queries:
1. Open the GraphiQL explorer tool:
- For GitLab.com, go to <https://gitlab.com/-/graphql-explorer>.
- - For self-managed GitLab, go to `https://gitlab.example.com/-/graphql-explorer`.
+ - For GitLab Self-Managed, go to `https://gitlab.example.com/-/graphql-explorer`.
Change `gitlab.example.com` to your instance URL.
1. Paste a query listed in an example into the left window of your GraphiQL explorer tool.
1. Select **Play**.
diff --git a/doc/api/graphql/sample_issue_boards.md b/doc/api/graphql/sample_issue_boards.md
index 0c467142b845..df4c26a27b82 100644
--- a/doc/api/graphql/sample_issue_boards.md
+++ b/doc/api/graphql/sample_issue_boards.md
@@ -21,7 +21,7 @@ You can use GraphiQL to list the issue boards for a project.
1. Open GraphiQL:
- For GitLab.com, use: `https://gitlab.com/-/graphql-explorer`
- - For self-managed GitLab, use: `https://gitlab.example.com/-/graphql-explorer`
+ - For GitLab Self-Managed, use: `https://gitlab.example.com/-/graphql-explorer`
1. Copy the following text and paste it in the left window. This query
gets issue boards for the `gitlab-docs` repository.
diff --git a/doc/api/graphql/users_example.md b/doc/api/graphql/users_example.md
index 9d02c846e930..6f40b7b8aba6 100644
--- a/doc/api/graphql/users_example.md
+++ b/doc/api/graphql/users_example.md
@@ -19,7 +19,7 @@ You can query a subset of users in a GitLab instance by using:
1. Open GraphiQL:
- For GitLab.com, use: `https://gitlab.com/-/graphql-explorer`
- - For self-managed GitLab, use: `https://gitlab.example.com/-/graphql-explorer`
+ - For GitLab Self-Managed, use: `https://gitlab.example.com/-/graphql-explorer`
1. Copy the following text and paste it in the left window.
This query looks for a subset of users in a GitLab instance by username.
Alternately, you can use their [Global ID](../../development/api_graphql_styleguide.md#global-ids).
diff --git a/doc/api/group_webhooks.md b/doc/api/group_webhooks.md
index e77cc217e150..6d4818542d58 100644
--- a/doc/api/group_webhooks.md
+++ b/doc/api/group_webhooks.md
@@ -431,7 +431,7 @@ Example response:
Resends a specific hook event.
This endpoint has a rate limit of five requests per minute for each hook and authenticated user.
-To disable this limit on self-managed GitLab and GitLab Dedicated, an administrator can
+To disable this limit on GitLab Self-Managed and GitLab Dedicated, an administrator can
[disable the feature flag](../administration/feature_flags.md) named `web_hook_event_resend_api_endpoint_rate_limit`.
```plaintext
@@ -671,7 +671,7 @@ On success, no message is returned.
Trigger a test hook for a specified group.
This endpoint has a rate limit of five requests per minute for each group and authenticated user.
-To disable this limit on self-managed GitLab and GitLab Dedicated, an administrator can
+To disable this limit on GitLab Self-Managed and GitLab Dedicated, an administrator can
[disable the feature flag](../administration/feature_flags.md) named `web_hook_test_api_endpoint_rate_limit`.
```plaintext
diff --git a/doc/api/groups.md b/doc/api/groups.md
index 7076886442be..8d430c51dc4d 100644
--- a/doc/api/groups.md
+++ b/doc/api/groups.md
@@ -1343,7 +1343,7 @@ Parameters:
> - `unique_project_download_limit`, `unique_project_download_limit_interval_in_seconds`, and `unique_project_download_limit_allowlist` [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92970) in GitLab 15.3 [with a flag](../administration/feature_flags.md) named `limit_unique_project_downloads_per_namespace_user`. Disabled by default.
FLAG:
-On self-managed GitLab, by default `unique_project_download_limit`, `unique_project_download_limit_interval_in_seconds`, `unique_project_download_limit_allowlist` and `auto_ban_user_on_excessive_projects_download` are not available.
+On GitLab Self-Managed, by default `unique_project_download_limit`, `unique_project_download_limit_interval_in_seconds`, `unique_project_download_limit_allowlist` and `auto_ban_user_on_excessive_projects_download` are not available.
To make them available, an administrator can [enable the feature flag](../administration/feature_flags.md)
named `limit_unique_project_downloads_per_namespace_user`.
diff --git a/doc/api/merge_request_approvals.md b/doc/api/merge_request_approvals.md
index 9833a02a1806..2d5a6bd4ae28 100644
--- a/doc/api/merge_request_approvals.md
+++ b/doc/api/merge_request_approvals.md
@@ -25,7 +25,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/428051) in GitLab 16.7 [with a flag](../administration/feature_flags.md) named `approval_group_rules`. Disabled by default. This feature is an [experiment](../policy/development_stages_support.md).
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../administration/feature_flags.md) named `approval_group_rules`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../administration/feature_flags.md) named `approval_group_rules`.
On GitLab.com and GitLab Dedicated, this feature is not available.
This feature is not ready for production use.
diff --git a/doc/api/project_import_export.md b/doc/api/project_import_export.md
index 15b4d94a26a5..75a9664f58ab 100644
--- a/doc/api/project_import_export.md
+++ b/doc/api/project_import_export.md
@@ -222,7 +222,7 @@ DETAILS:
**Status:** Beta
FLAG:
-On self-managed GitLab, by default this feature is available. To hide the feature, an administrator can [disable the feature flag](../administration/feature_flags.md) named `import_project_from_remote_file`.
+On GitLab Self-Managed, by default this feature is available. To hide the feature, an administrator can [disable the feature flag](../administration/feature_flags.md) named `import_project_from_remote_file`.
On GitLab.com and GitLab Dedicated, this feature is available.
```plaintext
diff --git a/doc/api/project_webhooks.md b/doc/api/project_webhooks.md
index 0828f20ef368..b00e0e2b66b5 100644
--- a/doc/api/project_webhooks.md
+++ b/doc/api/project_webhooks.md
@@ -363,7 +363,7 @@ Example response:
Resend a specific project webhook event.
This endpoint has a rate limit of five requests per minute for each project webhook and authenticated user.
-To disable this limit on self-managed GitLab and GitLab Dedicated, an administrator can
+To disable this limit on GitLab Self-Managed and GitLab Dedicated, an administrator can
[disable the feature flag](../administration/feature_flags.md) named `web_hook_event_resend_api_endpoint_rate_limit`.
```plaintext
@@ -496,7 +496,7 @@ In GitLab 17.0 and later, this endpoint has a special rate limit:
- In GitLab 17.0, the rate was three requests per minute for each project webhook.
- In GitLab 17.1, this was changed to five requests per minute for each project and authenticated user.
-To disable this limit on self-managed GitLab and GitLab Dedicated, an administrator can
+To disable this limit on GitLab Self-Managed and GitLab Dedicated, an administrator can
[disable the feature flag](../administration/feature_flags.md) named `web_hook_test_api_endpoint_rate_limit`.
```plaintext
diff --git a/doc/api/saml.md b/doc/api/saml.md
index 66f7e2380647..73a1f4154b1b 100644
--- a/doc/api/saml.md
+++ b/doc/api/saml.md
@@ -142,7 +142,7 @@ Example response:
}
```
-## Self-managed GitLab endpoints
+## GitLab Self-Managed endpoints
### Get a single SAML identity
diff --git a/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md b/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md
index eda332efc642..d5e2963dc7a7 100644
--- a/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md
+++ b/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md
@@ -16,7 +16,7 @@ the Amazon [Elastic Container Service (ECS)](https://aws.amazon.com/ecs/).
In this guide, you begin by creating an ECS cluster manually using the AWS console. You create and
deploy a simple application that you create from a GitLab template.
-These instructions work for both SaaS and self-managed GitLab instances.
+These instructions work for both GitLab.com and GitLab Self-Managed instances.
Ensure your own [runners are configured](../../runners/index.md).
## Prerequisites
diff --git a/doc/ci/components/index.md b/doc/ci/components/index.md
index 48e743cfbb1a..7591ea4f347b 100644
--- a/doc/ci/components/index.md
+++ b/doc/ci/components/index.md
@@ -755,7 +755,7 @@ When using third-party CI/CD components, consider the following security best pr
solution instead.
- **Use ephemeral, isolated runner environments**: Run component jobs in temporary,
isolated environments when possible. Be aware of [security risks](https://docs.gitlab.com/runner/security)
- with self-managed GitLab Runners.
+ with self-managed runners.
- **Securely handle cache and artifacts**: Do not pass cache or artifacts from other jobs
in your pipeline to CI/CD component jobs unless absolutely necessary.
- **Limit CI_JOB_TOKEN access**: Restrict [CI/CD job token (`CI_JOB_TOKEN`) project access and permissions](../../ci/jobs/ci_job_token.md#control-job-token-access-to-your-project)
diff --git a/doc/ci/migration/github_actions.md b/doc/ci/migration/github_actions.md
index fe51f9eab726..4cb8cb3a11c1 100644
--- a/doc/ci/migration/github_actions.md
+++ b/doc/ci/migration/github_actions.md
@@ -26,7 +26,7 @@ and deploying your code. Both share similarities including:
Additionally, there are some important differences between the two:
- GitHub has a marketplace for downloading 3rd-party actions, which might require additional support or licenses.
-- Self-managed GitLab instances support both horizontal and vertical scaling, while
+- GitLab Self-Managed instances support both horizontal and vertical scaling, while
GitHub Enterprise Server only supports vertical scaling.
- GitLab maintains and supports all features in house, and some 3rd-party integrations
are accessible through templates.
diff --git a/doc/ci/pipelines/merge_trains.md b/doc/ci/pipelines/merge_trains.md
index 16e4e56dc976..9afb6a07a34d 100644
--- a/doc/ci/pipelines/merge_trains.md
+++ b/doc/ci/pipelines/merge_trains.md
@@ -220,7 +220,7 @@ DETAILS:
> - [Enabled](https://gitlab.com/gitlab-org/gitlab/-/issues/422111) as an [experiment feature](../../policy/development_stages_support.md) in GitLab 16.10.
FLAG:
-On self-managed GitLab, by default this feature is available. To hide the feature,
+On GitLab Self-Managed, by default this feature is available. To hide the feature,
an administrator can [disable the feature flag](../../administration/feature_flags.md)
named `merge_trains_skip_train`. On GitLab.com and GitLab Dedicated, this feature is available.
diff --git a/doc/ci/runners/runner_fleet_dashboard_groups.md b/doc/ci/runners/runner_fleet_dashboard_groups.md
index 2c1f7c1e0298..3657574d7407 100644
--- a/doc/ci/runners/runner_fleet_dashboard_groups.md
+++ b/doc/ci/runners/runner_fleet_dashboard_groups.md
@@ -42,6 +42,6 @@ To view the runner fleet dashboard for groups:
1. Select **Build > Runners**.
1. Select **Fleet dashboard**.
-For self-managed GitLab instances, most of the dashboard metrics work without any additional configuration.
+For GitLab Self-Managed, most of the dashboard metrics work without any additional configuration.
To use the **Runner usage** and **Wait time to pick a job** metrics,
you must [configure the ClickHouse analytics database](runner_fleet_dashboard.md#enable-more-ci-analytics-features-with-clickhouse).
diff --git a/doc/development/activitypub/actors/index.md b/doc/development/activitypub/actors/index.md
index 78fbef349d86..1721da2277dd 100644
--- a/doc/development/activitypub/actors/index.md
+++ b/doc/development/activitypub/actors/index.md
@@ -12,7 +12,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127023) in GitLab 16.5 [with two flags](../../../administration/feature_flags.md) named `activity_pub` and `activity_pub_project`. Disabled by default. This feature is an [experiment](../../../policy/development_stages_support.md).
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available,
+On GitLab Self-Managed, by default this feature is not available. To make it available,
an administrator can [enable the feature flags](../../../administration/feature_flags.md)
named `activity_pub` and `activity_pub_project`.
On GitLab.com and GitLab Dedicated, this feature is not available.
diff --git a/doc/development/activitypub/actors/releases.md b/doc/development/activitypub/actors/releases.md
index bc996fc7af22..9581a634d101 100644
--- a/doc/development/activitypub/actors/releases.md
+++ b/doc/development/activitypub/actors/releases.md
@@ -12,7 +12,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127023) in GitLab 16.5 [with two flags](../../../administration/feature_flags.md) named `activity_pub` and `activity_pub_project`. Disabled by default. This feature is an [experiment](../../../policy/development_stages_support.md).
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available,
+On GitLab Self-Managed, by default this feature is not available. To make it available,
an administrator can [enable the feature flags](../../../administration/feature_flags.md)
named `activity_pub` and `activity_pub_project`.
On GitLab.com and GitLab Dedicated, this feature is not available.
diff --git a/doc/development/activitypub/index.md b/doc/development/activitypub/index.md
index 62d0bac2f324..4e57d0688767 100644
--- a/doc/development/activitypub/index.md
+++ b/doc/development/activitypub/index.md
@@ -12,7 +12,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127023) in GitLab 16.5 [with two flags](../../administration/feature_flags.md) named `activity_pub` and `activity_pub_project`. Disabled by default. This feature is an [experiment](../../policy/development_stages_support.md).
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available,
+On GitLab Self-Managed, by default this feature is not available. To make it available,
an administrator can [enable the feature flags](../../administration/feature_flags.md)
named `activity_pub` and `activity_pub_project`.
On GitLab.com and GitLab Dedicated, this feature is not available.
diff --git a/doc/development/ai_features/index.md b/doc/development/ai_features/index.md
index ced0fba517bd..0d3f5cab17fd 100644
--- a/doc/development/ai_features/index.md
+++ b/doc/development/ai_features/index.md
@@ -266,7 +266,7 @@ else:
**IMPORTANT:** At the [cleaning up](../feature_flags/controls.md#cleaning-up) step, remove the feature flag in AI gateway repository **before** removing the flag in GitLab-Rails repository.
If you clean up the flag in GitLab-Rails repository at first, the feature flag in AI gateway will be disabled immediately as it's the default state, hence you might encounter a surprising behavior.
-**IMPORTANT:** Cleaning up the feature flag in AI gateway will immediately distribute the change to all GitLab instances, including GitLab.com, Self-managed GitLab, and Dedicated.
+**IMPORTANT:** Cleaning up the feature flag in AI gateway will immediately distribute the change to all GitLab instances, including GitLab.com, GitLab Self-Managed, and GitLab Dedicated.
**Technical details:**
diff --git a/doc/development/cloud_connector/configuration.md b/doc/development/cloud_connector/configuration.md
index 4c4dab171ee6..c0a70a8bff86 100644
--- a/doc/development/cloud_connector/configuration.md
+++ b/doc/development/cloud_connector/configuration.md
@@ -230,7 +230,7 @@ To add a new unit primitive, follow [Register new feature for Self-Managed, Dedi
#### CustomersDot configuration
-For GitLab Dedicated and self-managed GitLab instances we are delegating trust to the CustomersDot, the access token issuer.
+For GitLab Dedicated and GitLab Self-Managed instances we are delegating trust to the CustomersDot, the access token issuer.
The configuration is located in [`cloud_connector.yml`](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/main/config/cloud_connector.yml),
and represents an almost exact copy of the GitLab.com configuration.
diff --git a/doc/development/cloud_connector/index.md b/doc/development/cloud_connector/index.md
index 3c7490f71ed1..e63ed9cbe729 100644
--- a/doc/development/cloud_connector/index.md
+++ b/doc/development/cloud_connector/index.md
@@ -38,7 +38,7 @@ because we do not currently have interfaces in place to self-service this.
#### Register the new feature in the JWT issuer
-- For GitLab Dedicated and self-managed GitLab instances, the CustomersDot is the **JWT issuer**.
+- For GitLab Dedicated and GitLab Self-Managed instances, the CustomersDot is the **JWT issuer**.
- For GitLab.com deployment, GitLab.com is the **JWT issuer**, because it's able to [self-sign and create JWTs](architecture.md#gitlabcom) for every request to a Cloud Connector feature.
#### Register new feature for Self-Managed, Dedicated and GitLab.com customers
@@ -149,7 +149,7 @@ As an example, the feature is delivered as a stand-alone service called `new_fea
To decide if the service is available or visible to the end user, we need to:
-- Optional. On self-managed GitLab, if the new feature is introduced as a new [enterprise feature](../ee_features.md#implement-a-new-ee-feature),
+- Optional. On GitLab Self-Managed, if the new feature is introduced as a new [enterprise feature](../ee_features.md#implement-a-new-ee-feature),
check to determine if user has access to the feature by following the [EE feature guideline](../ee_features.md#guard-your-ee-feature).
```ruby
@@ -158,7 +158,7 @@ To decide if the service is available or visible to the end user, we need to:
::License.feature_available?(:new_feature)
```
-- On self-managed GitLab, check if the customer is using an [online cloud license](https://about.gitlab.com/pricing/licensing-faq/cloud-licensing/#what-is-cloud-licensing)
+- On GitLab Self-Managed, check if the customer is using an [online cloud license](https://about.gitlab.com/pricing/licensing-faq/cloud-licensing/#what-is-cloud-licensing)
- Cloud connector currently only support online cloud license for self-managed customers.
- Trials or legacy licenses are not supported.
- GitLab.com is using a legacy license.
@@ -167,7 +167,7 @@ To decide if the service is available or visible to the end user, we need to:
::License.current&.online_cloud_license?
```
-- On GitLab.com and self-managed GitLab, check if the service has free access.
+- On GitLab.com and GitLab Self-Managed, check if the service has free access.
- The feature is considered free, if the [cut-off date](configuration.md) is not set, or it is set in the future.
```ruby
@@ -178,7 +178,7 @@ To decide if the service is available or visible to the end user, we need to:
- Optional. If the service has free access, this usually means that the experimental features are subject to the [Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
- For GitLab Duo features, the customer needs to enable [experimental toggle](../../user/gitlab_duo/turn_on_off.md#turn-on-beta-and-experimental-features) in order to use experimental features for free.
-- On GitLab.com and self-managed GitLab, if the service is not accessible for free, check if the add-on bundled with this service has been purchased by the customer (for the group/namespace)
+- On GitLab.com and GitLab Self-Managed, if the service is not accessible for free, check if the add-on bundled with this service has been purchased by the customer (for the group/namespace)
```ruby
# Returns true if at least one add-on that is bundled with the service is purchased.
@@ -188,7 +188,7 @@ To decide if the service is available or visible to the end user, we need to:
CloudConnector::AvailableServices.find_by_name(:new_feature).purchased?(namespace)
```
-- On GitLab.com and self-managed GitLab, check if the customer's end-user has been assigned to the proper seat.
+- On GitLab.com and GitLab Self-Managed, check if the customer's end-user has been assigned to the proper seat.
```ruby
# Returns true if service is allowed to be used.
diff --git a/doc/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md b/doc/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md
index 364bab466b66..424a19e84072 100644
--- a/doc/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md
+++ b/doc/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md
@@ -11,7 +11,7 @@ your changes, you can use
[GDK-in-a-box](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/gdk_in_a_box.md),
a virtual machine (VM) pre-configured with [the GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit).
-The GDK is a local development environment that includes an installation of self-managed GitLab,
+The GDK is a local development environment that includes an installation of GitLab Self-Managed,
sample projects, and administrator access with which you can test functionality.
It requires 30 GB of disk space.
diff --git a/doc/development/contributing/first_contribution/configure-dev-env-gdk.md b/doc/development/contributing/first_contribution/configure-dev-env-gdk.md
index 60bec122cefe..748f1df0d4e9 100644
--- a/doc/development/contributing/first_contribution/configure-dev-env-gdk.md
+++ b/doc/development/contributing/first_contribution/configure-dev-env-gdk.md
@@ -10,7 +10,7 @@ If you want to contribute to the GitLab codebase and want a development environm
your changes, you can use [the GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit),
a local version of GitLab that's yours to play with.
-The GDK is a local development environment that includes an installation of self-managed GitLab,
+The GDK is a local development environment that includes an installation of GitLab Self-Managed,
sample projects, and administrator access with which you can test functionality.
diff --git a/doc/development/contributing/first_contribution/index.md b/doc/development/contributing/first_contribution/index.md
index a1ac805d8414..f82a0cd2ea78 100644
--- a/doc/development/contributing/first_contribution/index.md
+++ b/doc/development/contributing/first_contribution/index.md
@@ -51,7 +51,7 @@ To get started, select the development option that works best for you:
- GitLab Development Kit (GDK) and GDK-in-a-box - Fully local development.
- GDK is a local development environment that includes an installation of self-managed GitLab,
+ GDK is a local development environment that includes an installation of GitLab Self-Managed,
sample projects, and administrator access with which you can test functionality.
These options rely on local hardware and may be resource intensive.
diff --git a/doc/development/contributing/index.md b/doc/development/contributing/index.md
index c63575fe7a72..70ab886c36cb 100644
--- a/doc/development/contributing/index.md
+++ b/doc/development/contributing/index.md
@@ -81,7 +81,7 @@ and offer support for making contributions.
To write and test your code locally, choose a local development environment.
- [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit), is a local
-development environment that includes an installation of self-managed GitLab, sample projects,
+development environment that includes an installation of GitLab Self-Managed, sample projects,
and administrator access with which you can test functionality.
- [GDK-in-a-box](first_contribution/configure-dev-env-gdk-in-a-box.md),
diff --git a/doc/development/documentation/graphql_styleguide.md b/doc/development/documentation/graphql_styleguide.md
index 4c704f64c7f3..36a48acebccf 100644
--- a/doc/development/documentation/graphql_styleguide.md
+++ b/doc/development/documentation/graphql_styleguide.md
@@ -60,7 +60,7 @@ You can use GraphiQL to list the branch rules for a project.
1. Open GraphiQL:
- For GitLab.com, use: `https://gitlab.com/-/graphql-explorer`
- - For self-managed GitLab, use: `https://gitlab.example.com/-/graphql-explorer`
+ - For GitLab Self-Managed, use: `https://gitlab.example.com/-/graphql-explorer`
1. Copy the following text and paste it in the left window.
<graphql codeblock here>
diff --git a/doc/development/documentation/styleguide/index.md b/doc/development/documentation/styleguide/index.md
index 4984ee5f7a4f..c39399ad7481 100644
--- a/doc/development/documentation/styleguide/index.md
+++ b/doc/development/documentation/styleguide/index.md
@@ -272,7 +272,7 @@ For screenshots:
When including sample URLs in the documentation, use:
- `example.com` when the domain name is generic.
-- `gitlab.example.com` when referring only to self-managed GitLab instances.
+- `gitlab.example.com` when referring only to GitLab Self-Managed instances.
Use `gitlab.com` for GitLab SaaS instances.
### Fake tokens
diff --git a/doc/development/internal_api/internal_api_allowed.md b/doc/development/internal_api/internal_api_allowed.md
index 2689ccc666dd..86af32f07428 100644
--- a/doc/development/internal_api/internal_api_allowed.md
+++ b/doc/development/internal_api/internal_api_allowed.md
@@ -89,7 +89,7 @@ same manner as the standard repositories, and is more prone to the refs issue.
### Parallel push checks
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available,
+On GitLab Self-Managed, by default this feature is not available. To make it available,
an administrator can [enable the feature flag](../../administration/feature_flags.md) named `parallel_push_checks`.
On GitLab.com, by default this feature is not available. To make it available
per project, ask GitLab.com administrator to
diff --git a/doc/development/ruby_upgrade.md b/doc/development/ruby_upgrade.md
index d96902e07e0e..f7041fc3810f 100644
--- a/doc/development/ruby_upgrade.md
+++ b/doc/development/ruby_upgrade.md
@@ -58,7 +58,7 @@ Before any upgrade, consider all audiences and targets, ordered by how immediate
1. **GitLab SaaS**. GitLab.com is deployed from customized Helm charts that use Docker images from [Cloud Native GitLab (CNG)](https://gitlab.com/gitlab-org/build/CNG).
Just like CI/CD, `.ruby-version` is meaningless in this environment. Instead, those Docker images must be patched to upgrade Ruby.
GitLab SaaS is affected with the next deployment.
-1. **Self-managed GitLab.** Customers installing GitLab via [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab) use none of the above.
+1. **GitLab Self-Managed.** Customers installing GitLab via [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab) use none of the above.
Instead, their Ruby version is defined by the [Ruby software bundle](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/config/software/ruby.rb) in Omnibus.
Self-managed customers are affected as soon as they upgrade to the release containing this change.
diff --git a/doc/development/stage_group_observability/gitlab_instrumentation_for_opentelemetry.md b/doc/development/stage_group_observability/gitlab_instrumentation_for_opentelemetry.md
index 685f2c55b4fc..d786bcf9cfa3 100644
--- a/doc/development/stage_group_observability/gitlab_instrumentation_for_opentelemetry.md
+++ b/doc/development/stage_group_observability/gitlab_instrumentation_for_opentelemetry.md
@@ -61,6 +61,6 @@ Once you have a project identified to use:
## Related design documents
-- [GitLab Observability in GitLab.com and Self-Managed GitLab Instances](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/observability_for_self_managed/)
+- [GitLab Observability in GitLab.com and GitLab Self-Managed instances](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/observability_for_self_managed/)
- [GitLab Observability - Metrics](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/observability_metrics/)
- [GitLab Observability - Logging](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/observability_logging/)
diff --git a/doc/integration/akismet.md b/doc/integration/akismet.md
index 8ab719a317d1..0b80522f6591 100644
--- a/doc/integration/akismet.md
+++ b/doc/integration/akismet.md
@@ -23,7 +23,7 @@ Privacy note: GitLab submits the user's IP and user agent to Akismet.
NOTE:
GitLab submits all issues to Akismet.
-Akismet configuration is available to users on self-managed GitLab. Akismet is already enabled on
+Akismet configuration is available to users on GitLab Self-Managed. Akismet is already enabled on
GitLab SaaS (GitLab.com), where its configuration and management are handled by GitLab Inc.
## Configure Akismet
diff --git a/doc/integration/arkose.md b/doc/integration/arkose.md
index 2efc39562747..9a99338ff088 100644
--- a/doc/integration/arkose.md
+++ b/doc/integration/arkose.md
@@ -7,7 +7,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Arkose Protect
WARNING:
-Arkose Protect is used on GitLab.com and is not supported for self-managed GitLab
+Arkose Protect is used on GitLab.com and is not supported for GitLab Self-Managed
instances. The following documents the internal requirements for maintaining
Arkose Protect on GitLab.com. While this feature is theoretically usable in self-managed instances, it
is not recommended at the moment.
diff --git a/doc/integration/gitpod.md b/doc/integration/gitpod.md
index 28c9aecda995..bbbd64e667a1 100644
--- a/doc/integration/gitpod.md
+++ b/doc/integration/gitpod.md
@@ -45,7 +45,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated
-For self-managed GitLab instances, a GitLab administrator must:
+For GitLab Self-Managed instances, a GitLab administrator must:
1. Enable the Gitpod integration in GitLab:
1. On the left sidebar, at the bottom, select **Admin**.
@@ -54,7 +54,7 @@ For self-managed GitLab instances, a GitLab administrator must:
1. Select the **Enable Gitpod integration** checkbox.
1. Enter the Gitpod instance URL (for example, `https://gitpod.example.com` or `https://gitpod.io`).
1. Select **Save changes**.
-1. Register the self-managed GitLab instance in Gitpod. For more information, see the [Gitpod documentation](https://www.gitpod.io/docs/configure/authentication/gitlab#registering-a-self-hosted-gitlab-installation).
+1. Register the GitLab Self-Managed instance in Gitpod. For more information, see the [Gitpod documentation](https://www.gitpod.io/docs/configure/authentication/gitlab#registering-a-self-hosted-gitlab-installation).
GitLab users can then [enable the Gitpod integration for themselves](#enable-gitpod-in-your-user-preferences).
diff --git a/doc/integration/jenkins.md b/doc/integration/jenkins.md
index 540314da3cce..43cf0ca0f90c 100644
--- a/doc/integration/jenkins.md
+++ b/doc/integration/jenkins.md
@@ -220,7 +220,7 @@ For this issue, check:
WebHook Error => execution expired
```
-On self-managed GitLab instances, you can fix this issue by [increasing the webhook timeout value](../administration/instance_limits.md#webhook-timeout).
+On GitLab Self-Managed instances, you can fix this issue by [increasing the webhook timeout value](../administration/instance_limits.md#webhook-timeout).
### Enable job logs in Jenkins
diff --git a/doc/integration/jira/configure.md b/doc/integration/jira/configure.md
index bfae29462e8c..4e19eb6ece90 100644
--- a/doc/integration/jira/configure.md
+++ b/doc/integration/jira/configure.md
@@ -41,7 +41,7 @@ You can enable the Jira issues integration by configuring your project settings
You can also configure the integration for a specific
[group](../../user/project/integrations/index.md#manage-group-default-settings-for-a-project-integration) or an entire
[instance](../../administration/settings/project_integration_management.md#configure-default-settings-for-an-integration)
-on self-managed GitLab.
+on GitLab Self-Managed.
With this integration, your GitLab project can interact with all Jira projects on your instance.
To configure your project settings in GitLab:
diff --git a/doc/integration/saml.md b/doc/integration/saml.md
index 4dedf80c13db..41603f0c2488 100644
--- a/doc/integration/saml.md
+++ b/doc/integration/saml.md
@@ -4,14 +4,14 @@ group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
-# SAML SSO for self-managed GitLab instances
+# SAML SSO for GitLab Self-Managed
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed
This page describes how to set up instance-wide SAML single sign on (SSO) for
-self-managed GitLab instances.
+GitLab Self-Managed.
You can configure GitLab to act as a SAML service provider (SP). This allows
GitLab to consume assertions from a SAML identity provider (IdP), such as
diff --git a/doc/integration/sourcegraph.md b/doc/integration/sourcegraph.md
index a2f390e28049..9fefd702d90d 100644
--- a/doc/integration/sourcegraph.md
+++ b/doc/integration/sourcegraph.md
@@ -11,7 +11,7 @@ DETAILS:
**Offering:** GitLab.com, GitLab Self-Managed, GitLab Dedicated
FLAG:
-On self-managed GitLab, by default this feature is available. To hide the feature,
+On GitLab Self-Managed, by default this feature is available. To hide the feature,
an administrator can [disable the feature flag](../administration/feature_flags.md) named `sourcegraph`.
On GitLab.com, this feature is available for public projects only.
@@ -35,7 +35,7 @@ For an overview, watch the video [Sourcegraph's new GitLab native integration](h
For more information, see [epic 2201](https://gitlab.com/groups/gitlab-org/-/epics/2201).
-## Set up for self-managed GitLab instances
+## Set up for GitLab Self-Managed
DETAILS:
**Tier:** Free, Premium, Ultimate
diff --git a/doc/operations/feature_flags.md b/doc/operations/feature_flags.md
index 139e448c9ad4..e05ee58c25b2 100644
--- a/doc/operations/feature_flags.md
+++ b/doc/operations/feature_flags.md
@@ -57,7 +57,7 @@ next to any feature flag in the list.
## Maximum number of feature flags
-The maximum number of feature flags per project on self-managed GitLab instances
+The maximum number of feature flags per project on GitLab Self-Managed instances
is 200. For GitLab SaaS, the maximum number is determined by [tier](https://about.gitlab.com/pricing/):
| Tier | Feature flags per project (SaaS) | Feature flags per project (self-managed) |
@@ -424,7 +424,7 @@ application can keep running in the current state.
Read the documentation in a SDK project for more information.
-### Self-managed GitLab
+### GitLab Self-Managed
Functionality-wise, there are no differences. Both SaaS and self-managed behave the same.
diff --git a/doc/security/email_verification.md b/doc/security/email_verification.md
index 30bf393e444c..d135fddf625f 100644
--- a/doc/security/email_verification.md
+++ b/doc/security/email_verification.md
@@ -13,7 +13,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/86352) in GitLab 15.2 [with a flag](../administration/feature_flags.md) named `require_email_verification`. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../administration/feature_flags.md) named `require_email_verification`. On GitLab.com and GitLab Dedicated, this feature is not available.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../administration/feature_flags.md) named `require_email_verification`. On GitLab.com and GitLab Dedicated, this feature is not available.
Account email verification provides an additional layer of GitLab account security.
When certain conditions are met, an account is locked. If your account is locked,
diff --git a/doc/security/hardening.md b/doc/security/hardening.md
index 3fad2094f474..16c6313f15f3 100644
--- a/doc/security/hardening.md
+++ b/doc/security/hardening.md
@@ -59,7 +59,7 @@ You can adjust the underlying operating system to increase overall security. For
## NIST 800-53 compliance
-You can configure self-managed GitLab to enforce compliance with the NIST 800-53 security standard. For more information, see [NIST 800-53 compliance](hardening_nist_800_53.md).
+You can configure GitLab Self-Managed to enforce compliance with the NIST 800-53 security standard. For more information, see [NIST 800-53 compliance](hardening_nist_800_53.md).
<!-- ## Troubleshooting
diff --git a/doc/security/hardening_nist_800_53.md b/doc/security/hardening_nist_800_53.md
index 140091a5c681..54ff93d8ace6 100644
--- a/doc/security/hardening_nist_800_53.md
+++ b/doc/security/hardening_nist_800_53.md
@@ -89,7 +89,7 @@ In order to meet FedRAMP requirements, ensure that the
existing identity provider is FedRAMP authorized on the [FedRAMP Marketplace](https://marketplace.fedramp.gov/products). To
meet requirements such as PIV, you should leverage an
identity provider rather than using native authentication in
-self-managed GitLab.
+GitLab Self-Managed.
GitLab provides resources for configuring various
identity providers and protocols, including
diff --git a/doc/security/index.md b/doc/security/index.md
index d7d753c2097b..cc195ad013e1 100644
--- a/doc/security/index.md
+++ b/doc/security/index.md
@@ -69,7 +69,7 @@ You can find all those directories listed in the [Linux package configuration do
### Patching
-Self-managed GitLab customers and administrators are responsible for the security of their underlying hosts, and for keeping GitLab itself up to date. It is important to [regularly patch GitLab](../policy/maintenance.md), patch your operating system and its software, and harden your hosts in accordance with vendor guidance.
+GitLab Self-Managed customers and administrators are responsible for the security of their underlying hosts, and for keeping GitLab itself up to date. It is important to [regularly patch GitLab](../policy/maintenance.md), patch your operating system and its software, and harden your hosts in accordance with vendor guidance.
## Monitoring
diff --git a/doc/security/responding_to_security_incidents.md b/doc/security/responding_to_security_incidents.md
index 9be5d9b123af..178bee8f3e04 100644
--- a/doc/security/responding_to_security_incidents.md
+++ b/doc/security/responding_to_security_incidents.md
@@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
When a security incident occurs, you should primarily follow the processes defined by your organization. The GitLab Security Operations team created this guide:
-- For administrators and maintainers of self-managed GitLab instances and groups on GitLab.com.
+- For administrators and maintainers of GitLab Self-Managed instances and groups on GitLab.com.
- To provide additional information and best practices on how to respond to various security incidents related to GitLab services.
- As a supplement to the processes defined by your organization to handle security incidents. It is **not a replacement**.
@@ -129,7 +129,7 @@ When secrets stored as CI variables are not [masked](../ci/variables/index.md#ma
### Suspected compromised instance
-Self-managed GitLab customers and administrators are responsible for:
+GitLab Self-Managed customers and administrators are responsible for:
- The security of their underlying infrastructure.
- Keeping their GitLab installation up to date.
diff --git a/doc/security/two_factor_authentication.md b/doc/security/two_factor_authentication.md
index 3972ab05927b..e0cc60774f47 100644
--- a/doc/security/two_factor_authentication.md
+++ b/doc/security/two_factor_authentication.md
@@ -204,7 +204,7 @@ DETAILS:
> - Push notification support [introduced](https://gitlab.com/gitlab-org/gitlab-shell/-/issues/506) in GitLab 15.3.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../administration/feature_flags.md) named `two_factor_for_cli`. On GitLab.com and GitLab Dedicated, this feature is not available. This feature is not ready for production use. This feature flag also affects [session duration for Git Operations when 2FA is enabled](../administration/settings/account_and_limit_settings.md#customize-session-duration-for-git-operations-when-2fa-is-enabled).
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../administration/feature_flags.md) named `two_factor_for_cli`. On GitLab.com and GitLab Dedicated, this feature is not available. This feature is not ready for production use. This feature flag also affects [session duration for Git Operations when 2FA is enabled](../administration/settings/account_and_limit_settings.md#customize-session-duration-for-git-operations-when-2fa-is-enabled).
You can enforce 2FA for [Git over SSH operations](../development/gitlab_shell/features.md#git-operations). However, you should use
[ED25519_SK](../user/ssh.md#ed25519_sk-ssh-keys) or [ECDSA_SK](../user/ssh.md#ecdsa_sk-ssh-keys) SSH keys instead. 2FA is enforced for Git operations only, and internal commands such as [`personal_access_token`](../development/gitlab_shell/features.md#personal-access-token) are excluded.
diff --git a/doc/subscriptions/bronze_starter.md b/doc/subscriptions/bronze_starter.md
index bcb4ba24618e..42bf3c52e109 100644
--- a/doc/subscriptions/bronze_starter.md
+++ b/doc/subscriptions/bronze_starter.md
@@ -95,7 +95,7 @@ the tiers are no longer mentioned in GitLab documentation:
- Run pipelines in the parent project [for merge requests from a forked project](../ci/pipelines/merge_request_pipelines.md#run-pipelines-in-the-parent-project)
- [Instance runners compute quota](../ci/pipelines/compute_minutes.md)
- [Push rules](../user/project/repository/push_rules.md)
-- SAML for self-managed GitLab instance:
+- SAML for GitLab Self-Managed:
- [Administrator groups](../integration/saml.md#administrator-groups)
- [Auditor groups](../integration/saml.md#auditor-groups)
- [External groups](../integration/saml.md#external-groups)
diff --git a/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md b/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md
index 48702fed332f..dff535b38b26 100644
--- a/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md
+++ b/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md
@@ -17,7 +17,7 @@ You are using the GitLab native Kubernetes integration, so you don't need
to create a Kubernetes cluster manually using the Google Cloud Platform console.
You are creating and deploying an application that you create from a GitLab template.
-These instructions also work for self-managed GitLab instances.
+These instructions also work for GitLab Self-Managed.
Ensure your own [runners are configured](../../../ci/runners/index.md) and
[Google OAuth is enabled](../../../integration/google.md).
diff --git a/doc/topics/offline/quick_start_guide.md b/doc/topics/offline/quick_start_guide.md
index ec072d1ebe0a..78da95e6a8cc 100644
--- a/doc/topics/offline/quick_start_guide.md
+++ b/doc/topics/offline/quick_start_guide.md
@@ -4,13 +4,13 @@ group: Distribution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
-# Install an offline self-managed GitLab instance
+# Install an offline GitLab Self-Managed instance
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed
-This is a step-by-step guide that helps you install, configure, and use a self-managed GitLab
+This is a step-by-step guide that helps you install, configure, and use a GitLab Self-Managed
instance entirely offline.
## Installation
diff --git a/doc/topics/runner_fleet_design_guides/gitlab_runner_fleet_config_and_best_practices.md b/doc/topics/runner_fleet_design_guides/gitlab_runner_fleet_config_and_best_practices.md
index ef124ced0f25..37a7b7784de2 100644
--- a/doc/topics/runner_fleet_design_guides/gitlab_runner_fleet_config_and_best_practices.md
+++ b/doc/topics/runner_fleet_design_guides/gitlab_runner_fleet_config_and_best_practices.md
@@ -177,7 +177,7 @@ To plan runner scope, consider the following questions:
- Does your organization have security or other policies that require segmenting access to certain types of runners to specific groups or projects?
-The most straightforward way to deploy a runner in a self-managed GitLab environments is to create it for an instance. Runners scoped for an instance are available to all groups and projects by default.
+The most straightforward way to deploy a runner in a GitLab Self-Managed environments is to create it for an instance. Runners scoped for an instance are available to all groups and projects by default.
If you are able to meet all your organization's needs with instance runners, then this deployment pattern is the most efficient pattern. It ensures that you can operate a CI/CD build fleet at scale efficiently and cost effectively.
diff --git a/doc/tutorials/observability/observability_django_tutorial.md b/doc/tutorials/observability/observability_django_tutorial.md
index 1befdfc02bf3..197d5149c192 100644
--- a/doc/tutorials/observability/observability_django_tutorial.md
+++ b/doc/tutorials/observability/observability_django_tutorial.md
@@ -145,7 +145,7 @@ To create an application:
1. To instrument the application, in the `manage.py` file, add the following code.
- Replace `{{PROJECT_ACCESS_TOKEN}}` and `{{PROJECT_ID}}` with the values from your project.
- - If you're using self-managed GitLab, replace `gitlab.com` with your self-managed instance hostname.
+ - If you're using GitLab Self-Managed, replace `gitlab.com` with your self-managed instance hostname.
```python
resource = Resource(attributes={
diff --git a/doc/tutorials/observability/observability_dotnet_tutorial.md b/doc/tutorials/observability/observability_dotnet_tutorial.md
index 1ac9310f165a..423ce3c634f6 100644
--- a/doc/tutorials/observability/observability_dotnet_tutorial.md
+++ b/doc/tutorials/observability/observability_dotnet_tutorial.md
@@ -204,7 +204,7 @@ Next, we'll create a .NET web application that we can instrument. For this tutor
1. Select **Copy project ID**. Save the copied ID for later.
1. Configure your application with instrumentation.
- If you're using self-managed GitLab, replace `gitlab.com` with your self-managed instance hostname.
+ If you're using GitLab Self-Managed, replace `gitlab.com` with your self-managed instance hostname.
1. Run your application.
```shell
diff --git a/doc/update/background_migrations.md b/doc/update/background_migrations.md
index cad1dedc1e63..da0d5ce82eff 100644
--- a/doc/update/background_migrations.md
+++ b/doc/update/background_migrations.md
@@ -183,7 +183,7 @@ There can be [risks when disabling released features](../administration/feature_
Refer to this feature's history for more details.
FLAG:
-On self-managed GitLab, by default this feature is available. To hide the feature, ask an administrator to [disable the feature flag](../administration/feature_flags.md) named `optimize_batched_migrations`.
+On GitLab Self-Managed, by default this feature is available. To hide the feature, ask an administrator to [disable the feature flag](../administration/feature_flags.md) named `optimize_batched_migrations`.
On GitLab.com, this feature is available. On GitLab Dedicated, this feature is not available.
To maximize throughput of batched background migrations (in terms of the number of tuples updated per time unit), batch sizes are automatically adjusted based on how long the previous batches took to complete.
diff --git a/doc/user/application_security/api_fuzzing/configuration/offline_configuration.md b/doc/user/application_security/api_fuzzing/configuration/offline_configuration.md
index 82d1dd7240e2..a5b261c96db3 100644
--- a/doc/user/application_security/api_fuzzing/configuration/offline_configuration.md
+++ b/doc/user/application_security/api_fuzzing/configuration/offline_configuration.md
@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Offline configuration
-For self-managed GitLab instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required for the Web API Fuzz testing job to successfully run.
+For GitLab Self-Managed instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required for the Web API Fuzz testing job to successfully run.
Steps:
diff --git a/doc/user/application_security/api_security_testing/configuration/offline_configuration.md b/doc/user/application_security/api_security_testing/configuration/offline_configuration.md
index 8f19ab995ff8..1e293274951a 100644
--- a/doc/user/application_security/api_security_testing/configuration/offline_configuration.md
+++ b/doc/user/application_security/api_security_testing/configuration/offline_configuration.md
@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Offline configuration
-For self-managed GitLab instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required for the API security testing job to successfully run.
+For GitLab Self-Managed instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required for the API security testing job to successfully run.
Steps:
diff --git a/doc/user/application_security/container_scanning/index.md b/doc/user/application_security/container_scanning/index.md
index 68255e95fcef..b9159a3ad5d0 100644
--- a/doc/user/application_security/container_scanning/index.md
+++ b/doc/user/application_security/container_scanning/index.md
@@ -483,7 +483,7 @@ Vulnerabilities in the log are marked as `Approved` when the corresponding CVE I
### Running container scanning in an offline environment
-For self-managed GitLab instances in an environment with limited, restricted, or intermittent access
+For GitLab Self-Managed instances in an environment with limited, restricted, or intermittent access
to external resources through the internet, some adjustments are required for the container scanning job to
successfully run. For more information, see [Offline environments](../offline_deployments/index.md).
diff --git a/doc/user/application_security/dast/browser/configuration/offline_configuration.md b/doc/user/application_security/dast/browser/configuration/offline_configuration.md
index 3d5d444b3ccf..2f69dcd065cc 100644
--- a/doc/user/application_security/dast/browser/configuration/offline_configuration.md
+++ b/doc/user/application_security/dast/browser/configuration/offline_configuration.md
@@ -7,7 +7,7 @@ type: reference, howto
# Offline configuration
-For self-managed GitLab instances in an environment with limited, restricted, or intermittent access
+For GitLab Self-Managed instances in an environment with limited, restricted, or intermittent access
to external resources through the internet, some adjustments are required for the DAST job to
successfully run. For more information, see [Offline environments](../../../offline_deployments/index.md).
diff --git a/doc/user/application_security/dependency_scanning/index.md b/doc/user/application_security/dependency_scanning/index.md
index bfe755827860..2ae87f7e6e74 100644
--- a/doc/user/application_security/dependency_scanning/index.md
+++ b/doc/user/application_security/dependency_scanning/index.md
@@ -1084,7 +1084,7 @@ You can also [submit new vulnerabilities](https://gitlab.com/gitlab-org/security
## Offline environment
-For self-managed GitLab instances in an environment with limited, restricted, or intermittent access
+For GitLab Self-Managed instances in an environment with limited, restricted, or intermittent access
to external resources through the internet, some adjustments are required for dependency scanning
jobs to run successfully. For more information, see [Offline environments](../offline_deployments/index.md).
diff --git a/doc/user/application_security/iac_scanning/index.md b/doc/user/application_security/iac_scanning/index.md
index d01ca3f8b717..29a2aaa82c29 100644
--- a/doc/user/application_security/iac_scanning/index.md
+++ b/doc/user/application_security/iac_scanning/index.md
@@ -190,7 +190,7 @@ DETAILS:
**Offering:** GitLab Self-Managed
An offline environment has limited, restricted, or intermittent access to external resources through
-the internet. For self-managed GitLab instances in such an environment, IaC requires
+the internet. For GitLab Self-Managed instances in such an environment, IaC requires
some configuration changes. The instructions in this section must be completed together with the
instructions detailed in [offline environments](../offline_deployments/index.md).
diff --git a/doc/user/application_security/policies/merge_request_approval_policies.md b/doc/user/application_security/policies/merge_request_approval_policies.md
index 130cf476cfea..0e610e88ae56 100644
--- a/doc/user/application_security/policies/merge_request_approval_policies.md
+++ b/doc/user/application_security/policies/merge_request_approval_policies.md
@@ -281,7 +281,7 @@ The settings set in the policy overwrite settings in the project.
> - The `fallback_behavior` field was [enabled on GitLab.com, self-managed, and GitLab Dedicated](https://gitlab.com/groups/gitlab-org/-/epics/10816) in GitLab 17.0.
FLAG:
-On self-managed GitLab, by default the `fallback_behavior` field is available. To hide the feature, an administrator can [disable the feature flag](../../../administration/feature_flags.md) named `security_scan_result_policies_unblock_fail_open_approval_rules`. On GitLab.com and GitLab Dedicated, this feature is available.
+On GitLab Self-Managed, by default the `fallback_behavior` field is available. To hide the feature, an administrator can [disable the feature flag](../../../administration/feature_flags.md) named `security_scan_result_policies_unblock_fail_open_approval_rules`. On GitLab.com and GitLab Dedicated, this feature is available.
| Field | Type | Required | Possible values | Description |
|--------|----------|----------|--------------------|----------------------------------------------------------------------------------------------------------------------|
diff --git a/doc/user/application_security/sast/index.md b/doc/user/application_security/sast/index.md
index 31e60eb72e4b..de8b71686c95 100644
--- a/doc/user/application_security/sast/index.md
+++ b/doc/user/application_security/sast/index.md
@@ -889,7 +889,7 @@ For more details see [Semgrep documentation](https://semgrep.dev/docs/ignoring-f
## Running SAST in an offline environment
-For self-managed GitLab instances in an environment with limited, restricted, or intermittent access
+For GitLab Self-Managed instances in an environment with limited, restricted, or intermittent access
to external resources through the internet, some adjustments are required for the SAST job to
run successfully. For more information, see [Offline environments](../offline_deployments/index.md).
diff --git a/doc/user/application_security/secret_detection/pipeline/index.md b/doc/user/application_security/secret_detection/pipeline/index.md
index 654512fece95..d7fc4c8ae0da 100644
--- a/doc/user/application_security/secret_detection/pipeline/index.md
+++ b/doc/user/application_security/secret_detection/pipeline/index.md
@@ -814,7 +814,7 @@ DETAILS:
**Offering:** GitLab Self-Managed
An offline environment has limited, restricted, or intermittent access to external resources through
-the internet. For self-managed GitLab instances in such an environment, pipeline secret detection requires
+the internet. For GitLab Self-Managed instances in such an environment, pipeline secret detection requires
some configuration changes. The instructions in this section must be completed together with the
instructions detailed in [offline environments](../../offline_deployments/index.md).
diff --git a/doc/user/application_security/secret_detection/push_protection_tutorial.md b/doc/user/application_security/secret_detection/push_protection_tutorial.md
index 6e02a873fc1a..aa455e97e1a0 100644
--- a/doc/user/application_security/secret_detection/push_protection_tutorial.md
+++ b/doc/user/application_security/secret_detection/push_protection_tutorial.md
@@ -37,7 +37,7 @@ Make sure you have the following before you complete this tutorial:
- A test project. You can use any project you like, but consider creating a test project specifically for this tutorial.
- Some familiarity with command-line Git.
-Additionally, on self-managed GitLab only, ensure secret push protection is
+Additionally, on GitLab Self-Managed only, ensure secret push protection is
[enabled on the instance](secret_push_protection/index.md#allow-the-use-of-secret-push-protection-in-your-gitlab-instance).
## Enable secret push protection
diff --git a/doc/user/clusters/agent/install/index.md b/doc/user/clusters/agent/install/index.md
index 7f83cf8744b1..2f31e2a841e3 100644
--- a/doc/user/clusters/agent/install/index.md
+++ b/doc/user/clusters/agent/install/index.md
@@ -22,7 +22,7 @@ Before you can install the agent in your cluster, you need:
- [Digital Ocean](https://docs.digitalocean.com/products/kubernetes/getting-started/quickstart/)
- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine/docs/deploy-app-cluster)
- You should use [Infrastructure as Code techniques](../../../infrastructure/iac/index.md) for managing infrastructure resources at scale.
-- On self-managed GitLab instances, a GitLab administrator must set up the
+- On GitLab Self-Managed, a GitLab administrator must set up the
[agent server](../../../../administration/clusters/kas.md).
Then it is available by default at `wss://gitlab.example.com/-/kubernetes-agent/`.
On GitLab.com, the agent server is available at `wss://kas.gitlab.com`.
diff --git a/doc/user/clusters/agent/work_with_agent.md b/doc/user/clusters/agent/work_with_agent.md
index e109e9d84cf0..e9b8df95c48d 100644
--- a/doc/user/clusters/agent/work_with_agent.md
+++ b/doc/user/clusters/agent/work_with_agent.md
@@ -162,7 +162,7 @@ To remove an agent from the UI:
1. Get the `<cluster-agent-token-id>` from a query in the interactive GraphQL explorer.
- For GitLab.com, go to <https://gitlab.com/-/graphql-explorer> to open GraphQL Explorer.
- - For self-managed GitLab, go to `https://gitlab.example.com/-/graphql-explorer`, replacing `gitlab.example.com` with your instance's URL.
+ - For GitLab Self-Managed, go to `https://gitlab.example.com/-/graphql-explorer`, replacing `gitlab.example.com` with your instance's URL.
```graphql
query{
diff --git a/doc/user/clusters/environments.md b/doc/user/clusters/environments.md
index e159a9771791..6774e2396736 100644
--- a/doc/user/clusters/environments.md
+++ b/doc/user/clusters/environments.md
@@ -16,7 +16,7 @@ WARNING:
This feature was [deprecated](https://gitlab.com/groups/gitlab-org/configure/-/epics/8) in GitLab 14.5.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `certificate_based_clusters`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `certificate_based_clusters`.
Cluster environments provide a consolidated view of which CI [environments](../../ci/environments/index.md) are
deployed to the Kubernetes cluster and it:
diff --git a/doc/user/clusters/management_project.md b/doc/user/clusters/management_project.md
index 9f36746d2869..f0b327523d0c 100644
--- a/doc/user/clusters/management_project.md
+++ b/doc/user/clusters/management_project.md
@@ -18,7 +18,7 @@ To manage cluster applications, use the [GitLab agent](agent/index.md)
with the [Cluster Management Project Template](management_project_template.md).
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `certificate_based_clusters`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `certificate_based_clusters`.
A project can be designated as the management project for a cluster.
A management project can be used to run deployment jobs with
diff --git a/doc/user/compliance/compliance_center/compliance_standards_adherence_dashboard.md b/doc/user/compliance/compliance_center/compliance_standards_adherence_dashboard.md
index a3e3c5125e05..980259aaa4ab 100644
--- a/doc/user/compliance/compliance_center/compliance_standards_adherence_dashboard.md
+++ b/doc/user/compliance/compliance_center/compliance_standards_adherence_dashboard.md
@@ -64,7 +64,7 @@ The GitLab standard consists of the following rules:
To comply with the GitLab standard, you must prevent users from approving their own merge requests. For more information,
see [Prevent approval by author](../../project/merge_requests/approvals/settings.md#prevent-approval-by-author).
-On self-managed GitLab, when instance-level setting for [prevent approval by author](../../../administration/merge_requests_approvals.md)
+On GitLab Self-Managed, when instance-level setting for [prevent approval by author](../../../administration/merge_requests_approvals.md)
is updated, the adherence status for all the projects on the instance is not updated automatically.
To update the adherence status for these projects, the group-level or the project-level setting must be updated.
@@ -73,7 +73,7 @@ To update the adherence status for these projects, the group-level or the projec
To comply with the GitLab standard, you must prevent users from approving merge requests where they've added commits. For
more information, see [Prevent approvals by users who add commits](../../project/merge_requests/approvals/settings.md#prevent-approvals-by-users-who-add-commits).
-On self-managed GitLab, when instance-level setting for [prevent approvals by users who add commits](../../../administration/merge_requests_approvals.md)
+On GitLab Self-Managed, when instance-level setting for [prevent approvals by users who add commits](../../../administration/merge_requests_approvals.md)
is updated, the adherence status for all the projects on the instance is not updated automatically.
To update the adherence status for these projects, the group-level or the project-level setting must be updated.
@@ -110,7 +110,7 @@ To comply with the SOC 2 standard, you must:
[Prevent approvals by users who add commits](../../project/merge_requests/approvals/settings.md#prevent-approvals-by-users-who-add-commits).
- At least one approval is required, see [Merge request approval rules](../../project/merge_requests/approvals/rules.md).
-These settings are available for an entire self-managed GitLab instance. However, when these settings are updated at the instance level,
+These settings are available for an entire GitLab Self-Managed instance. However, when these settings are updated at the instance level,
the adherence status for all the projects on the instance is not updated automatically. To update the adherence status
for these projects, you must update the group-level or project-level setting. For more information on the instance-level settings, see:
diff --git a/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md b/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md
index a63923dcae6b..555a4ab9de17 100644
--- a/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md
+++ b/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md
@@ -206,7 +206,7 @@ Users can require approval for merge requests based on the licenses that are det
## Running in an offline environment
-For self-managed GitLab instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required to successfully scan
+For GitLab Self-Managed instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required to successfully scan
CycloneDX reports for licenses. For more information, see the offline [quick start guide](../../../topics/offline/quick_start_guide.md#enabling-the-package-metadata-database).
## Use CycloneDX report as a source of license information
diff --git a/doc/user/custom_roles.md b/doc/user/custom_roles.md
index b3ddcad9a074..cdb3f460532e 100644
--- a/doc/user/custom_roles.md
+++ b/doc/user/custom_roles.md
@@ -263,7 +263,7 @@ the user also has `Manage CI/CD variables` permission in Subgroup B and Project
When you assign a custom role to a user with the Guest role, that user has
access to elevated permissions over the base role, and therefore:
-- Is considered a [billable user](../subscriptions/self_managed/index.md#billable-users) on self-managed GitLab.
+- Is considered a [billable user](../subscriptions/self_managed/index.md#billable-users) on GitLab Self-Managed.
- [Uses a seat](../subscriptions/gitlab_com/index.md#how-seat-usage-is-determined) on GitLab.com.
This does not apply when the user's custom role only has the `read_code` permission
diff --git a/doc/user/get_started/getting_started_gitlab_duo.md b/doc/user/get_started/getting_started_gitlab_duo.md
index 27717d2c9e8e..6fc77e838896 100644
--- a/doc/user/get_started/getting_started_gitlab_duo.md
+++ b/doc/user/get_started/getting_started_gitlab_duo.md
@@ -20,7 +20,7 @@ After your organization purchases a subscription, an administrator must assign s
You likely received an email that notified you of your seat.
The AI-powered features you have access to use language models to help streamline
-your workflow. If you're on self-managed GitLab, your administrator can choose to use
+your workflow. If you're on GitLab Self-Managed, your administrator can choose to use
GitLab models, or self-host their own models.
If you have issues accessing GitLab Duo features, ask your administrator.
diff --git a/doc/user/gitlab_duo/use_cases.md b/doc/user/gitlab_duo/use_cases.md
index 2b9879c41e2b..441829f699ef 100644
--- a/doc/user/gitlab_duo/use_cases.md
+++ b/doc/user/gitlab_duo/use_cases.md
@@ -15,7 +15,7 @@ Learn how to:
- Solve security vulnerabilities.
NOTE:
-If you have self-managed GitLab: GitLab Duo requires GitLab 17.2 and later for the best user experience and results. Earlier versions may continue to work, however the experience may be degraded.
+If you have GitLab Self-Managed: GitLab Duo requires GitLab 17.2 and later for the best user experience and results. Earlier versions may continue to work, however the experience may be degraded.
## Use GitLab Duo to solve development challenges
diff --git a/doc/user/gitlab_duo_chat/index.md b/doc/user/gitlab_duo_chat/index.md
index a080f0beada3..d3dea2577d0e 100644
--- a/doc/user/gitlab_duo_chat/index.md
+++ b/doc/user/gitlab_duo_chat/index.md
@@ -32,7 +32,7 @@ You can use GitLab Duo Chat in:
- Visual Studio for Windows, with the [GitLab Extension for Visual Studio](https://marketplace.visualstudio.com/items?itemName=GitLab.GitLabExtensionForVisualStudio)
NOTE:
-If you have self-managed GitLab: GitLab Duo requires GitLab 17.2 and later for the best user experience and results. Earlier versions may continue to work, however the experience may be degraded.
+If you have GitLab Self-Managed: GitLab Duo requires GitLab 17.2 and later for the best user experience and results. Earlier versions may continue to work, however the experience may be degraded.
## The context Chat is aware of
diff --git a/doc/user/group/import/index.md b/doc/user/group/import/index.md
index e4df9790827c..067a758859d6 100644
--- a/doc/user/group/import/index.md
+++ b/doc/user/group/import/index.md
@@ -16,9 +16,9 @@ DETAILS:
You can migrate GitLab groups:
-- From self-managed GitLab to GitLab.com.
-- From GitLab.com to self-managed GitLab.
-- From one self-managed GitLab instance to another.
+- From GitLab Self-Managed to GitLab.com.
+- From GitLab.com to GitLab Self-Managed.
+- From one GitLab Self-Managed instance to another.
- Between groups in the same GitLab instance.
Migration by direct transfer creates a new copy of the group. If you want to move groups instead of copying groups, you
@@ -30,9 +30,9 @@ You can migrate groups in two ways:
- By direct transfer (recommended).
- By [uploading an export file](../../project/settings/import_export.md).
-If you migrate from GitLab.com to self-managed GitLab, an administrator can create users on the self-managed GitLab instance.
+If you migrate from GitLab.com to GitLab Self-Managed, an administrator can create users on the GitLab Self-Managed instance.
-On self-managed GitLab, by default [migrating group items](migrated_items.md#migrated-group-items) is not available. To show the
+On GitLab Self-Managed, by default [migrating group items](migrated_items.md#migrated-group-items) is not available. To show the
feature, an administrator can [enable it in application settings](../../../administration/settings/import_and_export_settings.md#enable-migration-of-groups-and-projects-by-direct-transfer).
Migrating groups by direct transfer copies the groups from one place to another. You can:
diff --git a/doc/user/group/index.md b/doc/user/group/index.md
index ad6323985725..a086e4ee0ae2 100644
--- a/doc/user/group/index.md
+++ b/doc/user/group/index.md
@@ -67,7 +67,7 @@ The following table describes the most common models of structuring groups.
<!-- vale gitlab_base.Simplicity = YES -->
NOTE:
-On self-managed GitLab, if you want to see an overview of your entire organization, you should create one top-level group.
+On GitLab Self-Managed, if you want to see an overview of your entire organization, you should create one top-level group.
For more information about efforts to create an organization view of all groups,
[see epic 9266](https://gitlab.com/groups/gitlab-org/-/epics/9266).
A top-level group offers insights in your entire organization through a complete
diff --git a/doc/user/group/manage.md b/doc/user/group/manage.md
index a3bea949db59..f5ea2289d338 100644
--- a/doc/user/group/manage.md
+++ b/doc/user/group/manage.md
@@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
Use groups to manage one or more related projects at the same time.
NOTE:
-On self-managed GitLab, if you want to see an overview of your entire organization, you should create one top-level group.
+On GitLab Self-Managed, if you want to see an overview of your entire organization, you should create one top-level group.
For more information about efforts to create an organization view of all groups,
[see epic 9266](https://gitlab.com/groups/gitlab-org/-/epics/9266).
A top-level group offers insights in your entire organization through a complete
diff --git a/doc/user/group/saml_sso/group_sync.md b/doc/user/group/saml_sso/group_sync.md
index 0dc8cb580504..a60087745994 100644
--- a/doc/user/group/saml_sso/group_sync.md
+++ b/doc/user/group/saml_sso/group_sync.md
@@ -30,7 +30,7 @@ SAML Group Sync only manages a group if that group has one or more SAML group li
Prerequisites:
-- Self-managed GitLab instances must have configured [SAML Group Sync](#configure-saml-group-sync). GitLab.com
+- GitLab Self-Managed instances must have configured [SAML Group Sync](#configure-saml-group-sync). GitLab.com
instances are already configured for SAML Group Sync, and require no extra configuration.
When SAML is enabled, users with the Owner role see a new menu
@@ -77,7 +77,7 @@ SAML Group Sync can manage GitLab Duo seat assignment and removal based on IdP g
The checkbox does not appear for groups without an active GitLab Duo add-on subscription.
-### Self-managed GitLab with multiple SAML IdPs
+### GitLab Self-Managed with multiple SAML IdPs
When a user signs in, GitLab:
@@ -139,7 +139,7 @@ WARNING:
To prevent users being accidentally removed from the GitLab group, follow these instructions closely before
enabling Group Sync in GitLab.
-To configure SAML Group Sync for **self-managed GitLab instances**:
+To configure SAML Group Sync for GitLab Self-Managed:
1. Configure the [SAML OmniAuth Provider](../../../integration/saml.md).
1. Ensure your SAML identity provider sends an attribute statement with the same name as the value of the `groups_attribute` setting. See the following provider configuration example in `/etc/gitlab/gitlab.rb` for reference:
diff --git a/doc/user/group/saml_sso/index.md b/doc/user/group/saml_sso/index.md
index 17ef734fd6e4..bd15170b6e52 100644
--- a/doc/user/group/saml_sso/index.md
+++ b/doc/user/group/saml_sso/index.md
@@ -194,7 +194,7 @@ Optionally, you can pass user information to GitLab as attributes in the SAML as
- The username can be either a **username** or **nickname** attribute. You should specify only
one of these.
-For more information, see the [attributes available for self-managed GitLab instances](../../../integration/saml.md#configure-assertions).
+For more information, see the [attributes available for GitLab Self-Managed instances](../../../integration/saml.md#configure-assertions).
### Use metadata
@@ -582,7 +582,7 @@ For example:
## Related topics
-- [SAML SSO for self-managed GitLab instances](../../../integration/saml.md)
+- [SAML SSO for GitLab Self-Managed](../../../integration/saml.md)
- [Glossary](../../../integration/saml.md#glossary)
- [Blog post: The ultimate guide to enabling SAML and SSO on GitLab.com](https://about.gitlab.com/blog/2023/09/14/the-ultimate-guide-to-enabling-saml/)
- [Authentication comparison between SaaS and self-managed](../../../administration/auth/index.md#gitlabcom-compared-to-self-managed)
@@ -596,8 +596,8 @@ identity provider:
1. Check your identity provider's documentation. Look at their example SAML
configurations for information on the terms they use.
-1. Check the [SAML SSO for self-managed GitLab instances documentation](../../../integration/saml.md).
- The self-managed GitLab instance SAML configuration file supports more options
+1. Check the [SAML SSO for GitLab Self-Managed documentation](../../../integration/saml.md).
+ The GitLab Self-Managed SAML configuration file supports more options
than the GitLab.com file. You can find information on the self-managed instance
file in the:
- External [OmniAuth SAML documentation](https://github.com/omniauth/omniauth-saml/).
diff --git a/doc/user/group/saml_sso/scim_setup.md b/doc/user/group/saml_sso/scim_setup.md
index 803babfcce0b..7c94d6624971 100644
--- a/doc/user/group/saml_sso/scim_setup.md
+++ b/doc/user/group/saml_sso/scim_setup.md
@@ -23,7 +23,7 @@ When SCIM is enabled for a GitLab group, membership of that group is synchronize
The [internal GitLab group SCIM API](../../../development/internal_api/index.md#group-scim-api) implements part of [the RFC7644 protocol](https://www.rfc-editor.org/rfc/rfc7644).
Identity providers can use the [internal GitLab group SCIM API](../../../development/internal_api/index.md#group-scim-api) to develop a SCIM app.
-To set up SCIM on GitLab self-managed, see [Configure SCIM for self-managed GitLab instances](../../../administration/settings/scim_setup.md).
+To set up SCIM on GitLab self-managed, see [Configure SCIM for GitLab Self-Managed](../../../administration/settings/scim_setup.md).
## Configure GitLab
diff --git a/doc/user/group/saml_sso/troubleshooting_scim.md b/doc/user/group/saml_sso/troubleshooting_scim.md
index 1d04858fc28d..6cd4fef3c80b 100644
--- a/doc/user/group/saml_sso/troubleshooting_scim.md
+++ b/doc/user/group/saml_sso/troubleshooting_scim.md
@@ -30,7 +30,7 @@ When that user is added back to the SCIM app:
For users de-provisioned by SCIM before that date, their SAML identity is destroyed.
To solve this problem, the user must [link SAML to their existing GitLab.com account](index.md#link-saml-to-your-existing-gitlabcom-account).
-### Self-managed GitLab
+### GitLab Self-Managed
For GitLab Self-Managed, administrators of that instance can instead [add the user identity themselves](../../../administration/admin_area.md#user-identities). This might save time if administrators need to re-add multiple identities.
@@ -291,8 +291,8 @@ In your Okta SCIM application, check that the SCIM **Base URL** is correct and p
SCIM API endpoint URL. Check the following documentation to find information on this URL for:
- [GitLab.com groups](scim_setup.md#configure-gitlab).
-- [Self-managed GitLab instances](../../../administration/settings/scim_setup.md#configure-gitlab).
+- [GitLab Self-Managed instances](../../../administration/settings/scim_setup.md#configure-gitlab).
-For self-managed GitLab instances, ensure that GitLab is publicly available so Okta can connect to it. If needed,
+For GitLab Self-Managed instances, ensure that GitLab is publicly available so Okta can connect to it. If needed,
you can [allow access to Okta IP addresses](https://help.okta.com/en-us/Content/Topics/Security/ip-address-allow-listing.htm)
on your firewall.
diff --git a/doc/user/group/value_stream_analytics/index.md b/doc/user/group/value_stream_analytics/index.md
index 1874f6cb88f4..ea0e765a0730 100644
--- a/doc/user/group/value_stream_analytics/index.md
+++ b/doc/user/group/value_stream_analytics/index.md
@@ -226,7 +226,7 @@ When you upgrade your GitLab version to 16.10 (or to a higher version), existing
DETAILS:
**Offering:** GitLab Self-Managed
-On large self-managed GitLab instances, when you upgrade the GitLab version and especially if several minor versions are skipped, the background aggregation processes might last longer. This delay can result in outdated data on the Value Stream Analytics page.
+On large GitLab Self-Managed instances, when you upgrade the GitLab version and especially if several minor versions are skipped, the background aggregation processes might last longer. This delay can result in outdated data on the Value Stream Analytics page.
To speed up the aggregation process and avoid outdated data, in the [rails console](../../../administration/operations/rails_console.md#starting-a-rails-console-session) you can invoke the synchronous aggregation snippet for a given group:
```ruby
diff --git a/doc/user/infrastructure/clusters/index.md b/doc/user/infrastructure/clusters/index.md
index 2a246912b044..39d24db70826 100644
--- a/doc/user/infrastructure/clusters/index.md
+++ b/doc/user/infrastructure/clusters/index.md
@@ -17,7 +17,7 @@ To connect clusters to GitLab, use the [GitLab agent](../../clusters/agent/index
WARNING:
In GitLab 14.5, the certificate-based method to connect Kubernetes clusters
to GitLab was [deprecated](https://gitlab.com/groups/gitlab-org/configure/-/epics/8),
-as well as its related [features](#deprecated-features). In self-managed GitLab 17.0 and later,
+as well as its related [features](#deprecated-features). In GitLab Self-Managed 17.0 and later,
this feature is disabled by default. For GitLab SaaS users, this feature is available until
GitLab 15.9 for users who have at least one certificate-based cluster enabled in their namespace hierarchy.
For GitLab SaaS users that never used this feature previously, it is no longer available.
diff --git a/doc/user/infrastructure/iac/terraform_state.md b/doc/user/infrastructure/iac/terraform_state.md
index 909694a69e17..8d37f10e2f34 100644
--- a/doc/user/infrastructure/iac/terraform_state.md
+++ b/doc/user/infrastructure/iac/terraform_state.md
@@ -33,7 +33,7 @@ or consider using a separate GitLab instance with no shared points of failure.
## Prerequisites
-For self-managed GitLab, before you can use GitLab for your OpenTofu state files:
+For GitLab Self-Managed, before you can use GitLab for your OpenTofu state files:
- An administrator must [set up Terraform/OpenTofu state storage](../../../administration/terraform_state.md).
- You must turn on the **Infrastructure** menu for your project:
diff --git a/doc/user/okrs.md b/doc/user/okrs.md
index 596f033e6d3a..c80d7c689bb6 100644
--- a/doc/user/okrs.md
+++ b/doc/user/okrs.md
@@ -590,7 +590,7 @@ DETAILS:
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/446064) to feature flag named `work_items_beta` in GitLab 16.10. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available per group, an administrator can [enable the feature flag](../administration/feature_flags.md) named `work_items_beta`.
+On GitLab Self-Managed, by default this feature is not available. To make it available per group, an administrator can [enable the feature flag](../administration/feature_flags.md) named `work_items_beta`.
On GitLab.com and GitLab Dedicated, this feature is not available.
This feature is not ready for production use.
diff --git a/doc/user/organization/index.md b/doc/user/organization/index.md
index 671d50cb8f66..584987c2169b 100644
--- a/doc/user/organization/index.md
+++ b/doc/user/organization/index.md
@@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/409913) in GitLab 16.1 [with a flag](../../administration/feature_flags.md) named `ui_for_organizations`. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `ui_for_organizations`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `ui_for_organizations`.
On GitLab.com and GitLab Dedicated, this feature is not available.
This feature is not ready for production use.
diff --git a/doc/user/packages/container_registry/authenticate_with_container_registry.md b/doc/user/packages/container_registry/authenticate_with_container_registry.md
index 334cf9d4a9ab..f8b74543f196 100644
--- a/doc/user/packages/container_registry/authenticate_with_container_registry.md
+++ b/doc/user/packages/container_registry/authenticate_with_container_registry.md
@@ -115,5 +115,5 @@ unauthorized: authentication required
```
This error happens when your authentication token expires before the image push is complete.
-By default, tokens for the container registry on self-managed GitLab instances expire after five minutes.
+By default, tokens for the container registry on GitLab Self-Managed instances expire after five minutes.
On GitLab.com, the token expiration time is 15 minutes.
diff --git a/doc/user/packages/container_registry/cosign_tutorial.md b/doc/user/packages/container_registry/cosign_tutorial.md
index 2a2b191d5d59..c50b51d6f99c 100644
--- a/doc/user/packages/container_registry/cosign_tutorial.md
+++ b/doc/user/packages/container_registry/cosign_tutorial.md
@@ -28,7 +28,7 @@ When you put it all together, your `.gitlab-ci.yml` should look similar to the [
You must have:
- Cosign v2.0 or later installed.
-- For self-managed GitLab instances, the GitLab container registry [configured with a metadata database](../../../administration/packages/container_registry_metadata_database.md)
+- For GitLab Self-Managed, the GitLab container registry [configured with a metadata database](../../../administration/packages/container_registry_metadata_database.md)
to display signatures.
## Set image and service image
diff --git a/doc/user/packages/container_registry/index.md b/doc/user/packages/container_registry/index.md
index 96c6ac0f2342..f8dafee9841c 100644
--- a/doc/user/packages/container_registry/index.md
+++ b/doc/user/packages/container_registry/index.md
@@ -103,7 +103,7 @@ On a self-managed instance, you can delete all container images before moving or
a group or project. Alternatively, [issue 18383](https://gitlab.com/gitlab-org/gitlab/-/issues/18383#possible-workaround)
contains community suggestions to work around this limitation. [Epic 9459](https://gitlab.com/groups/gitlab-org/-/epics/9459)
proposes adding support for moving projects and groups with container repositories
-to self-managed GitLab.
+to GitLab Self-Managed.
## Disable the container registry for a project
@@ -185,7 +185,7 @@ next to each tag that has an associated signature. To see the details of the sig
Prerequisites:
- To sign container images, Cosign v2.0 or later.
-- For self-managed GitLab instances, you need a
+- For GitLab Self-Managed, you need a
[GitLab container registry configured with a metadata database](../../../administration/packages/container_registry_metadata_database.md)
to display signatures.
diff --git a/doc/user/packages/nuget_repository/index.md b/doc/user/packages/nuget_repository/index.md
index 4431322428d9..c939a78a36a3 100644
--- a/doc/user/packages/nuget_repository/index.md
+++ b/doc/user/packages/nuget_repository/index.md
@@ -306,7 +306,7 @@ Prerequisites:
When publishing packages:
- The package registry on GitLab.com can store up to 5 GB of content.
- This limit is [configurable for self-managed GitLab instances](../../../administration/instance_limits.md#package-registry-limits).
+ This limit is [configurable for GitLab Self-Managed](../../../administration/instance_limits.md#package-registry-limits).
- If you publish the same package with the same version multiple times, each
consecutive upload is saved as a separate file. When installing a package,
GitLab serves the most recent file.
diff --git a/doc/user/permissions.md b/doc/user/permissions.md
index 0397e5a85acc..3608ad12684a 100644
--- a/doc/user/permissions.md
+++ b/doc/user/permissions.md
@@ -179,7 +179,7 @@ Project permissions for [compliance](compliance/index.md) features including com
| Action | Guest | Planner | Reporter | Developer | Maintainer | Owner | Notes |
| ------------------------------------------------------------------------------------------------- | :---: | :-----: | :------: | :-------: | :--------: | :---: | ----- |
-| View [allowed and denied licenses in MR](compliance/license_scanning_of_cyclonedx_files/index.md) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On self-managed GitLab instances, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be have at least the Reporter role, even if the project is internal. Users with the Guest role on GitLab.com are able to perform this action only on public projects because internal visibility is not available. |
+| View [allowed and denied licenses in MR](compliance/license_scanning_of_cyclonedx_files/index.md) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On GitLab Self-Managed, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be have at least the Reporter role, even if the project is internal. Users with the Guest role on GitLab.com are able to perform this action only on public projects because internal visibility is not available. |
| View [audit events](compliance/audit_events.md) | | | | ✓ | ✓ | ✓ | Users can only view events based on their individual actions. For more details, see the [prerequisites](compliance/audit_events.md#prerequisites). |
| View licenses in [dependency list](application_security/dependency_list/index.md) | | | | ✓ | ✓ | ✓ | |
| Manage [audit streams](compliance/audit_event_streaming.md) | | | | | | ✓ | |
@@ -296,7 +296,7 @@ Project permissions for [package registry](../user/packages/index.md):
| Action | Guest | Planner | Reporter | Developer | Maintainer | Owner | Notes |
| --------------------------------------- | :---: | :-----: | :------: | :-------: | :--------: | :---: | ----- |
-| Pull a package | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On self-managed GitLab instances, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
+| Pull a package | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On GitLab Self-Managed, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
| Publish a package | | | | ✓ | ✓ | ✓ | |
| Delete a package | | | | | ✓ | ✓ | |
| Delete a file associated with a package | | | | | ✓ | ✓ | |
@@ -307,19 +307,19 @@ Project permissions for [project features](project/organize_work_with_projects.m
| Action | Guest | Planner | Reporter | Developer | Maintainer | Owner | Notes |
| ------------------------------------------------------------------------- | :---: | :-----: | :------: | :-------: | :--------: | :---: | ----- |
-| Download project | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On self-managed GitLab instances, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
+| Download project | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On GitLab Self-Managed, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
| Leave comments | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
| Reposition comments on images (posted by any user) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | Applies only to comments on [Design Management](project/issues/design_management.md) designs. |
| View [Insights](project/insights/index.md) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
| View [Requirements](project/requirements/index.md) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
-| View [time tracking](project/time_tracking.md) reports | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On self-managed GitLab instances, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
+| View [time tracking](project/time_tracking.md) reports | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On GitLab Self-Managed, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
| View [snippets](snippets.md) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
| View [project traffic statistics](../api/project_statistics.md) | | | ✓ | ✓ | ✓ | ✓ | |
| Create [snippets](snippets.md) | | | ✓ | ✓ | ✓ | ✓ | |
| View [releases](project/releases/index.md) | | ✓ | | ✓ | ✓ | ✓ | Guest users can access GitLab [**Releases**](project/releases/index.md) for downloading assets but are not allowed to download the source code nor see [repository information like commits and release evidence](project/releases/index.md#view-a-release-and-download-assets). |
| Manage [releases](project/releases/index.md) | | | | | ✓ | ✓ | If the [tag is protected](project/protected_tags.md), this depends on the access given to Developers and Maintainers. |
| Configure [webhooks](project/integrations/webhooks.md) | | | | | ✓ | ✓ | |
-| Manage [project access tokens](project/settings/project_access_tokens.md) | | | | | ✓ | ✓ | For self-managed GitLab, project access tokens are available in all tiers. For GitLab.com, project access tokens are supported in the Premium and Ultimate tier (excluding [trial licenses](https://about.gitlab.com/free-trial/)). |
+| Manage [project access tokens](project/settings/project_access_tokens.md) | | | | | ✓ | ✓ | For GitLab Self-Managed, project access tokens are available in all tiers. For GitLab.com, project access tokens are supported in the Premium and Ultimate tier (excluding [trial licenses](https://about.gitlab.com/free-trial/)). |
| [Export project](project/settings/import_export.md) | | | | | ✓ | ✓ | |
| Rename project | | | | | ✓ | ✓ | |
| Edit project badges | | | | | ✓ | ✓ | |
@@ -353,8 +353,8 @@ Project permissions for [repository](project/repository/index.md) features inclu
| Action | Guest | Planner | Reporter | Developer | Maintainer | Owner | Notes |
| --------------------------------------------------------------------- | :---: | :-----: | :------: | :-------: | :--------: | :---: | ----- |
-| View project code | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On self-managed GitLab instances, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. In GitLab 15.9 and later, users with the Guest role and an Ultimate license can view private repository content if an administrator (on self-managed or GitLab Dedicated) or group owner (on GitLab.com) gives those users permission. The administrator or group owner can create a [custom role](custom_roles.md) through the API or UI and assign that role to the users. |
-| Pull project code | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On self-managed GitLab instances, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
+| View project code | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On GitLab Self-Managed, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. In GitLab 15.9 and later, users with the Guest role and an Ultimate license can view private repository content if an administrator (on self-managed or GitLab Dedicated) or group owner (on GitLab.com) gives those users permission. The administrator or group owner can create a [custom role](custom_roles.md) through the API or UI and assign that role to the users. |
+| Pull project code | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On GitLab Self-Managed, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
| View commit status | | | ✓ | ✓ | ✓ | ✓ | |
| Create commit status | | | | ✓ | ✓ | ✓ | If the [branch is protected](project/repository/branches/protected.md), this depends on the access given to Developers and Maintainers. |
| Update commit status | | | | ✓ | ✓ | ✓ | If the [branch is protected](project/repository/branches/protected.md), this depends on the access given to Developers and Maintainers. |
@@ -376,7 +376,7 @@ Project permissions for [merge requests](project/merge_requests/index.md):
| Action | Guest | Planner | Reporter | Developer | Maintainer | Owner | Notes |
| ---------------------------------------------------------------------------------------------------------- | :---: | :-----: | :------: | :-------: | :--------: | :---: | ----- |
-| [View](project/merge_requests/index.md#view-merge-requests) a merge request | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On self-managed GitLab instances, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
+| [View](project/merge_requests/index.md#view-merge-requests) a merge request | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On GitLab Self-Managed, users with the Guest role are able to perform this action only on public and internal projects (not on private projects). [External users](../administration/external_users.md) must be given explicit access (at least the **Reporter** role) even if the project is internal. Users with the Guest role on GitLab.com are only able to perform this action on public projects because internal visibility is not available. |
| Create [snippets](snippets.md) | | | ✓ | ✓ | ✓ | ✓ | |
| Create [merge request](project/merge_requests/creating_merge_requests.md) | | | | ✓ | ✓ | ✓ | In projects that accept contributions from external members, users can create, edit, and close their own merge requests. For **private** projects, this excludes the Guest role as those users [cannot clone private projects](public_access.md#private-projects-and-groups). For **internal** projects, includes users with read-only access to the project, as [they can clone internal projects](public_access.md#internal-projects-and-groups). |
| Update merge request including assign, review, Code Suggestions, approve, labels, lock and resolve threads | | | | ✓ | ✓ | ✓ | For information on eligible approvers for merge requests, see [Eligible approvers](project/merge_requests/approvals/rules.md#eligible-approvers). |
diff --git a/doc/user/profile/account/delete_account.md b/doc/user/profile/account/delete_account.md
index 6c4815327f35..b4751a569f5e 100644
--- a/doc/user/profile/account/delete_account.md
+++ b/doc/user/profile/account/delete_account.md
@@ -23,7 +23,7 @@ Deleting a user deletes all projects in that user namespace.
> - Delay between a user deleting their own account and deletion of the user record introduced in GitLab 16.0 [with a flag](../../../administration/feature_flags.md) named `delay_delete_own_user`. Enabled by default on GitLab.com.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `delay_delete_own_user`. On GitLab.com, this feature is available. On GitLab Dedicated, this feature is not available.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `delay_delete_own_user`. On GitLab.com, this feature is available. On GitLab Dedicated, this feature is not available.
On GitLab.com, it takes seven days from when you delete your own account to when your account is deleted. During this time:
diff --git a/doc/user/profile/account/two_factor_authentication.md b/doc/user/profile/account/two_factor_authentication.md
index 869c5a01353f..2ac583d0de35 100644
--- a/doc/user/profile/account/two_factor_authentication.md
+++ b/doc/user/profile/account/two_factor_authentication.md
@@ -34,7 +34,7 @@ The following Git credential helpers authenticate to GitLab using OAuth. This is
### Git Credential Manager
-[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) authenticates by default using OAuth. GCM supports GitLab.com without any manual configuration. To use GCM with self-managed GitLab, see [GitLab support](https://github.com/GitCredentialManager/git-credential-manager/blob/main/docs/gitlab.md).
+[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) authenticates by default using OAuth. GCM supports GitLab.com without any manual configuration. To use GCM with GitLab Self-Managed, see [GitLab support](https://github.com/GitCredentialManager/git-credential-manager/blob/main/docs/gitlab.md).
So you do not need to re-authenticate on every push, GCM supports caching as well as a variety of platform-specific credential stores that persist between sessions. This feature is useful whether you use personal access tokens or OAuth.
@@ -44,7 +44,7 @@ Git Credential Manager is developed primarily by GitHub, Inc. It is an open-sour
### git-credential-oauth
-[git-credential-oauth](https://github.com/hickford/git-credential-oauth) supports GitLab.com and several popular public hosts without any manual configuration needed. To use with self-managed GitLab, see the [git-credential-oauth custom hosts documentation](https://github.com/hickford/git-credential-oauth#custom-hosts).
+[git-credential-oauth](https://github.com/hickford/git-credential-oauth) supports GitLab.com and several popular public hosts without any manual configuration needed. To use with GitLab Self-Managed, see the [git-credential-oauth custom hosts documentation](https://github.com/hickford/git-credential-oauth#custom-hosts).
Many Linux distributions include git-credential-oauth as a package.
@@ -95,7 +95,7 @@ DETAILS:
**Offering:** GitLab Self-Managed
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available per user, an administrator can
+On GitLab Self-Managed, by default this feature is not available. To make it available per user, an administrator can
[enable the feature flag](../../../administration/feature_flags.md) named `forti_authenticator`.
On GitLab.com and GitLab Dedicated, this feature is not available.
@@ -226,7 +226,7 @@ DETAILS:
**Offering:** GitLab Self-Managed
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available per user, an administrator can
+On GitLab Self-Managed, by default this feature is not available. To make it available per user, an administrator can
[enable the feature flag](../../../administration/feature_flags.md) named `forti_token_cloud`.
On GitLab.com and GitLab Dedicated, this feature is not available.
This feature is not ready for production use.
diff --git a/doc/user/profile/achievements.md b/doc/user/profile/achievements.md
index 92a92ce661c3..53e3081fbce8 100644
--- a/doc/user/profile/achievements.md
+++ b/doc/user/profile/achievements.md
@@ -14,7 +14,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/113156) in GitLab 15.10 [with a flag](../../administration/feature_flags.md) named `achievements`. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available,
+On GitLab Self-Managed, by default this feature is not available. To make it available,
an administrator can [enable the feature flag](../../administration/feature_flags.md) named `achievements`.
Achievements are a way to reward users for their activity on GitLab.
diff --git a/doc/user/profile/personal_access_tokens.md b/doc/user/profile/personal_access_tokens.md
index 783ad8570e5c..86d8e4e82f3c 100644
--- a/doc/user/profile/personal_access_tokens.md
+++ b/doc/user/profile/personal_access_tokens.md
@@ -294,7 +294,7 @@ Prerequisites:
You can now create personal access tokens for a service account user with no expiry date.
-#### Self-managed GitLab
+#### GitLab Self-Managed
Prerequisites:
diff --git a/doc/user/profile/service_accounts.md b/doc/user/profile/service_accounts.md
index eba8c8d1f7ca..9ce79e4ce77d 100644
--- a/doc/user/profile/service_accounts.md
+++ b/doc/user/profile/service_accounts.md
@@ -34,7 +34,7 @@ token for [Git operations](personal_access_tokens.md#clone-repository-using-pers
[Rate limits](../../security/rate_limits.md) apply to service accounts:
- On GitLab.com, there are [GitLab.com-specific rate limits](../gitlab_com/index.md#gitlabcom-specific-rate-limits).
-- On self-managed GitLab and GitLab Dedicated, there are both:
+- On GitLab Self-Managed and GitLab Dedicated, there are both:
- [Configurable rate limits](../../security/rate_limits.md#configurable-limits).
- [Non-configurable rate limits](../../security/rate_limits.md#non-configurable-limits).
diff --git a/doc/user/project/clusters/gitlab_managed_clusters.md b/doc/user/project/clusters/gitlab_managed_clusters.md
index a830df85f3a0..adb9b96c806a 100644
--- a/doc/user/project/clusters/gitlab_managed_clusters.md
+++ b/doc/user/project/clusters/gitlab_managed_clusters.md
@@ -18,7 +18,7 @@ To connect your cluster to GitLab, use the [GitLab agent](../../../user/clusters
To manage applications, use the [Cluster Project Management Template](../../../user/clusters/management_project_template.md).
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `certificate_based_clusters`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `certificate_based_clusters`.
You can choose to allow GitLab to manage your cluster for you. If your cluster
is managed by GitLab, resources for your projects are automatically created. See
diff --git a/doc/user/project/deploy_boards.md b/doc/user/project/deploy_boards.md
index fcb230a0fb50..edae5b696ae6 100644
--- a/doc/user/project/deploy_boards.md
+++ b/doc/user/project/deploy_boards.md
@@ -18,7 +18,7 @@ This feature was [deprecated](https://gitlab.com/groups/gitlab-org/configure/-/e
to add this functionality to the [agent](../clusters/agent/index.md).
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `certificate_based_clusters`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `certificate_based_clusters`.
GitLab deploy boards offer a consolidated view of the current health and
status of each CI [environment](../../ci/environments/index.md) running on [Kubernetes](https://kubernetes.io), displaying the status
diff --git a/doc/user/project/import/github.md b/doc/user/project/import/github.md
index 33a6498dc33a..1b40fb3ead9e 100644
--- a/doc/user/project/import/github.md
+++ b/doc/user/project/import/github.md
@@ -108,7 +108,7 @@ If importing from `github.com` you can use any method to import. Self-hosted Git
### Use GitHub OAuth
-If you are importing to GitLab.com or to a self-managed GitLab that has GitHub OAuth [configured](../../../integration/github.md), you can use GitHub OAuth to import your repository.
+If you are importing to GitLab.com or to a GitLab Self-Managed that has GitHub OAuth [configured](../../../integration/github.md), you can use GitHub OAuth to import your repository.
This method has an advantage over using a [personal access token (PAT)](#use-a-github-personal-access-token)
because the backend exchanges the access token with the appropriate permissions.
diff --git a/doc/user/project/import/index.md b/doc/user/project/import/index.md
index ba1e413e57d1..0cb18f0d3b99 100644
--- a/doc/user/project/import/index.md
+++ b/doc/user/project/import/index.md
@@ -223,7 +223,7 @@ For Premium customers trying out Ultimate (Ultimate trial paid customer plan), P
If these limits are not sufficient for your import, [contact GitLab Support](https://about.gitlab.com/support/).
-The above limits are for GitLab.com. Self-managed GitLab has no placeholder limits by default. A self-managed instance administrator can [set a placeholder limit](../../../administration/instance_limits.md#import-placeholder-user-limits) for their installation.
+The above limits are for GitLab.com. GitLab Self-Managed has no placeholder limits by default. A self-managed instance administrator can [set a placeholder limit](../../../administration/instance_limits.md#import-placeholder-user-limits) for their installation.
### Reassign contributions and memberships
diff --git a/doc/user/project/integrations/gitlab_slack_application.md b/doc/user/project/integrations/gitlab_slack_application.md
index 4505b556e353..e567abb3a24d 100644
--- a/doc/user/project/integrations/gitlab_slack_application.md
+++ b/doc/user/project/integrations/gitlab_slack_application.md
@@ -24,7 +24,7 @@ you run in Slack is run by your linked GitLab user.
Prerequisites:
- You must have the [appropriate permissions to add apps to your Slack workspace](https://slack.com/help/articles/202035138-Add-apps-to-your-Slack-workspace).
-- On self-managed GitLab, an administrator must [enable the integration](../../../administration/settings/slack_app.md).
+- On GitLab Self-Managed, an administrator must [enable the integration](../../../administration/settings/slack_app.md).
In GitLab 15.0 and later, the GitLab for Slack app uses
[granular permissions](https://medium.com/slack-developer-blog/more-precision-less-restrictions-a3550006f9c3).
diff --git a/doc/user/project/integrations/index.md b/doc/user/project/integrations/index.md
index 374f4adc06df..70212a51f94e 100644
--- a/doc/user/project/integrations/index.md
+++ b/doc/user/project/integrations/index.md
@@ -17,7 +17,7 @@ You can integrate with external applications to add functionality to GitLab.
You can view and manage integrations for the:
-- [Instance](../../../administration/settings/project_integration_management.md#configure-default-settings-for-an-integration) (self-managed GitLab)
+- [Instance](../../../administration/settings/project_integration_management.md#configure-default-settings-for-an-integration) (GitLab Self-Managed)
- [Group](#manage-group-default-settings-for-a-project-integration)
You can use:
diff --git a/doc/user/project/integrations/slack_slash_commands.md b/doc/user/project/integrations/slack_slash_commands.md
index 305fc637a7fc..d2d5997235f7 100644
--- a/doc/user/project/integrations/slack_slash_commands.md
+++ b/doc/user/project/integrations/slack_slash_commands.md
@@ -11,7 +11,7 @@ DETAILS:
**Offering:** GitLab Self-Managed, GitLab Dedicated
NOTE:
-This feature is only configurable on self-managed GitLab instances.
+This feature is only configurable on GitLab Self-Managed.
For GitLab.com, use the [GitLab for Slack app](gitlab_slack_application.md) instead.
You can use [slash commands](gitlab_slack_application.md#slash-commands) to run common GitLab operations,
diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md
index 2775c6dd9288..af6f927292b0 100644
--- a/doc/user/project/issue_board.md
+++ b/doc/user/project/issue_board.md
@@ -676,7 +676,7 @@ and the target list.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61955) behind a [feature flag](../feature_flags.md) named `board_multi_select` in GitLab 14.0. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, ask an
+On GitLab Self-Managed, by default this feature is not available. To make it available, ask an
administrator to [enable the feature flag](../../administration/feature_flags.md) named `board_multi_select`.
On GitLab.com and GitLab Dedicated, this feature is not available.
This feature is not ready for production use.
diff --git a/doc/user/project/issues/managing_issues.md b/doc/user/project/issues/managing_issues.md
index eb23dc6f6a3a..541f248af74d 100644
--- a/doc/user/project/issues/managing_issues.md
+++ b/doc/user/project/issues/managing_issues.md
@@ -306,7 +306,7 @@ You can also use the `/reopen` [quick action](../quick_actions.md) in a comment
### Closing issues automatically
You can close issues automatically by using certain words, called a _closing pattern_,
-in a commit message or merge request description. Administrators of self-managed GitLab instances
+in a commit message or merge request description. Administrators of GitLab Self-Managed instances
can [change the default closing pattern](../../../administration/issue_closing_pattern.md).
If a commit message or merge request description contains text matching the [closing pattern](#default-closing-pattern),
diff --git a/doc/user/project/merge_requests/approvals/settings.md b/doc/user/project/merge_requests/approvals/settings.md
index c622074adb34..123516a2152e 100644
--- a/doc/user/project/merge_requests/approvals/settings.md
+++ b/doc/user/project/merge_requests/approvals/settings.md
@@ -130,7 +130,7 @@ When you change this field, it can affect all open merge requests depending on t
> - [Enabled `ff_require_saml_auth_to_approve` by default](https://gitlab.com/gitlab-org/gitlab/-/issues/431714) in GitLab 16.8 for GitLab.com and self-managed instances.
FLAG:
-On self-managed GitLab, by default requiring re-authentication by using SAML authentication is available. To hide the feature, an administrator can
+On GitLab Self-Managed, by default requiring re-authentication by using SAML authentication is available. To hide the feature, an administrator can
[disable the feature flag](../../../../administration/feature_flags.md) named `ff_require_saml_auth_to_approve`. On GitLab.com and GitLab Dedicated, this feature is available.
You can force potential approvers to first authenticate with SAML or a password.
@@ -147,7 +147,7 @@ Prerequisites:
[sign-in restrictions documentation](../../../../administration/settings/sign_in_restrictions.md#password-authentication-enabled).
- SAML authentication for GitLab.com groups, see
[SAML SSO for GitLab.com groups documentation](../../../../user/group/saml_sso/index.md).
- - SAML authentication for self-managed instances, see [SAML SSO for self-managed GitLab instances](../../../../integration/saml.md).
+ - SAML authentication for self-managed instances, see [SAML SSO for GitLab Self-Managed](../../../../integration/saml.md).
1. On the left sidebar, select **Settings > Merge requests**.
1. In the **Merge request approvals** section, scroll to **Approval settings** and
select **Require user re-authentication (password or SAML) to approve**.
diff --git a/doc/user/project/merge_requests/index.md b/doc/user/project/merge_requests/index.md
index 32656e0e9597..f2a8d6d47df6 100644
--- a/doc/user/project/merge_requests/index.md
+++ b/doc/user/project/merge_requests/index.md
@@ -392,7 +392,7 @@ DETAILS:
> - [Issues, incidents](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133474), and [epics](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133881) also updated.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `notifications_todos_buttons`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `notifications_todos_buttons`.
On GitLab.com and GitLab Dedicated, this feature is not available.
Enabling this feature flag moves the notifications and to-do item buttons to the upper right corner of the page.
diff --git a/doc/user/project/milestones/burndown_and_burnup_charts.md b/doc/user/project/milestones/burndown_and_burnup_charts.md
index ad5d31aa074e..a4511c6bbd59 100644
--- a/doc/user/project/milestones/burndown_and_burnup_charts.md
+++ b/doc/user/project/milestones/burndown_and_burnup_charts.md
@@ -144,7 +144,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/381879) in GitLab 17.1 [with a flag](../../../administration/feature_flags.md) named `rollup_timebox_chart`. Disabled by default.
FLAG:
-On self-managed GitLab, by default this feature is not available. For more information, see the history.
+On GitLab Self-Managed, by default this feature is not available. For more information, see the history.
This feature is available for testing, but not ready for production use.
With [tasks](../../tasks.md), a more granular planning is possible.
diff --git a/doc/user/project/pages/index.md b/doc/user/project/pages/index.md
index 74f255b34fde..afcd713836c2 100644
--- a/doc/user/project/pages/index.md
+++ b/doc/user/project/pages/index.md
@@ -298,7 +298,7 @@ The number of parallel deployments is limited by the root-level namespace. For
specific limits for:
- GitLab.com, see [Other limits](../../gitlab_com/index.md#other-limits).
-- Self-managed GitLab instances, see
+- GitLab Self-Managed, see
[Number of parallel Pages deployments](../../../administration/instance_limits.md#number-of-parallel-pages-deployments).
To immediately reduce the number of active deployments in your namespace,
diff --git a/doc/user/project/repository/mirror/index.md b/doc/user/project/repository/mirror/index.md
index 9b105281a24b..d15d3c9b7a4e 100644
--- a/doc/user/project/repository/mirror/index.md
+++ b/doc/user/project/repository/mirror/index.md
@@ -222,7 +222,7 @@ for you to check:
Other providers vary. You can securely gather key fingerprints with the following
command if you:
-- Run self-managed GitLab.
+- Run GitLab Self-Managed.
- Have access to the server for the other repository.
```shell
diff --git a/doc/user/project/settings/import_export.md b/doc/user/project/settings/import_export.md
index 34a832fbe413..d1b8b72d2251 100644
--- a/doc/user/project/settings/import_export.md
+++ b/doc/user/project/settings/import_export.md
@@ -24,7 +24,7 @@ situations, you might need to migrate groups and project by using file exports.
## Migrate projects by uploading an export file
-Existing projects on any self-managed GitLab instance or GitLab.com can be exported to a file and
+Existing projects on any GitLab Self-Managed instance or GitLab.com can be exported to a file and
then imported into another GitLab instance.
### Preserving user contributions
diff --git a/doc/user/project/time_tracking.md b/doc/user/project/time_tracking.md
index b2678f438efb..5b7248433f73 100644
--- a/doc/user/project/time_tracking.md
+++ b/doc/user/project/time_tracking.md
@@ -192,7 +192,7 @@ DETAILS:
> - Enabled on GitLab.com in GitLab 16.5.
FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `global_time_tracking_report`.
+On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `global_time_tracking_report`.
On GitLab.com, this feature is available. On GitLab Dedicated, this feature is not available.
This feature is not ready for production use.
diff --git a/doc/user/project/web_ide/index.md b/doc/user/project/web_ide/index.md
index a137ee92bcf5..934e85693245 100644
--- a/doc/user/project/web_ide/index.md
+++ b/doc/user/project/web_ide/index.md
@@ -319,7 +319,7 @@ To update the OAuth callback URL:
DETAILS:
**Offering:** GitLab Self-Managed
-On self-managed GitLab, [Workhorse](../../../development/workhorse/index.md) must be installed
+On GitLab Self-Managed, [Workhorse](../../../development/workhorse/index.md) must be installed
and running in front of the GitLab Rails server.
Otherwise, you might encounter issues when you open the Web IDE or
use certain features like Markdown preview.
diff --git a/doc/user/project/wiki/index.md b/doc/user/project/wiki/index.md
index 7a1c7d2ae58a..b2561d47df5a 100644
--- a/doc/user/project/wiki/index.md
+++ b/doc/user/project/wiki/index.md
@@ -346,7 +346,7 @@ Wikis are enabled by default in GitLab. Project [administrators](../../permissio
can enable or disable a project wiki by following the instructions in
[Sharing and permissions](../settings/index.md#configure-project-features-and-permissions).
-Administrators for self-managed GitLab installs can
+Administrators for GitLab Self-Managed can
[configure additional wiki settings](../../../administration/wikis/index.md).
You can disable group wikis from the [group settings](group.md#configure-group-wiki-visibility)
diff --git a/doc/user/search/advanced_search.md b/doc/user/search/advanced_search.md
index 7c5655315d01..6a1882ed8890 100644
--- a/doc/user/search/advanced_search.md
+++ b/doc/user/search/advanced_search.md
@@ -90,7 +90,7 @@ You can refine user search with `simple_query_string`.
- You can only search files smaller than 1 MB.
For more information, see [issue 195764](https://gitlab.com/gitlab-org/gitlab/-/issues/195764).
- For self-managed GitLab instances, an administrator can
+ For GitLab Self-Managed, an administrator can
[configure the **Maximum file size indexed** setting](../../integration/advanced_search/elasticsearch.md#advanced-search-configuration).
- You can use advanced search on the default branch of a project only.
For more information, see [issue 229966](https://gitlab.com/gitlab-org/gitlab/-/issues/229966).
diff --git a/doc/user/snippets.md b/doc/user/snippets.md
index 23516812009a..5763bf585d6a 100644
--- a/doc/user/snippets.md
+++ b/doc/user/snippets.md
@@ -229,7 +229,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated
-Administrators on self-managed GitLab instances can mark snippets as spam.
+Administrators on GitLab Self-Managed instances can mark snippets as spam.
Prerequisites:
diff --git a/doc/user/version.md b/doc/user/version.md
index 53702f5231ba..5a65c8035edc 100644
--- a/doc/user/version.md
+++ b/doc/user/version.md
@@ -13,7 +13,7 @@ DETAILS:
Find the version of GitLab you're running.
-## For self-managed GitLab and GitLab Dedicated
+## For GitLab Self-Managed and GitLab Dedicated
Prerequisites:
--
GitLab