diff --git a/data/deprecations/15-9-deprecate-option-to-remove-project-immediately.yml b/data/deprecations/15-9-deprecate-option-to-remove-project-immediately.yml
index edce84880119114eb012b32acb50d96191640a89..fba5e2d2c28eca7021e00c00f0ff785451c6e101 100644
--- a/data/deprecations/15-9-deprecate-option-to-remove-project-immediately.yml
+++ b/data/deprecations/15-9-deprecate-option-to-remove-project-immediately.yml
@@ -6,7 +6,7 @@
stage: manage # (required) String value of the stage that the feature was created in. e.g., Growth
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/389557 # (required) Link to the deprecation issue in GitLab
body: | # (required) Do not modify this line, instead modify the lines below.
- The group and project deletion protection setting in the Admin area had an option to delete groups and projects immediately. Starting with 16.0, this option will no longer be available, and delayed group and project deletion will become the default behavior.
+ The group and project deletion protection setting in the **Admin** area had an option to delete groups and projects immediately. Starting with 16.0, this option will no longer be available, and delayed group and project deletion will become the default behavior.
The option will no longer appear as a group setting. Self-managed users will still have the option to define the deletion delay period, and SaaS users have a non-adjustable default retention period of 7 days. Users can still immediately delete the project from the project settings, and the group from the group settings.
diff --git a/doc/administration/admin_area.md b/doc/administration/admin_area.md
index 31a5bea1bf8ce72f5de81790a90366a5733a0329..8a8afb56b15e374c2f19825923e5a4bde3937df1 100644
--- a/doc/administration/admin_area.md
+++ b/doc/administration/admin_area.md
@@ -10,10 +10,11 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed, GitLab Dedicated
-The Admin area provides a web UI to manage and configure features of GitLab
-self-managed instances. If you are an administrator, to access the Admin area:
+The **Admin** area provides a web UI to manage and configure features of GitLab
+self-managed instances. If you are an administrator, to access the **Admin** area:
-- In GitLab 16.7 and later: on the left sidebar, at the bottom, select **Admin**.
+- In GitLab 17.3 and later: on the left sidebar, at the bottom, select **Admin**.
+- In GitLab 16.7 and later: on the left sidebar, at the bottom, select **Admin area**.
- In GitLab 16.1 and later: on the left sidebar, select **Search or go to**, then select **Admin**.
- In GitLab 16.0 and earlier: on the top bar, select **Main menu > Admin**.
@@ -21,7 +22,7 @@ If the GitLab instance uses Admin Mode, you must [enable Admin Mode for your ses
the **Admin** button is visible.
NOTE:
-Only administrators on GitLab self-managed or GitLab Dedicated can access the Admin area. On GitLab.com the Admin area feature is not available.
+Only administrators on GitLab self-managed or GitLab Dedicated can access the **Admin** area. On GitLab.com the **Admin** area feature is not available.
## Administering organizations
@@ -32,7 +33,7 @@ On self-managed GitLab, by default this feature is not available. To make it ava
On GitLab.com and GitLab Dedicated, this feature is not available.
This feature is not ready for production use.
-You can administer all organizations in the GitLab instance from the Admin area's Organizations page.
+You can administer all organizations in the GitLab instance from the **Admin** area's Organizations page.
To access the Organizations page:
@@ -41,7 +42,7 @@ To access the Organizations page:
## Administering projects
-You can administer all projects in the GitLab instance from the Admin area's Projects page.
+You can administer all projects in the GitLab instance from the **Admin** area's Projects page.
To access the Projects page:
@@ -96,7 +97,7 @@ You can combine the filter options. For example, to list only public projects wi
> - Filtering users [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/238183) in GitLab 17.0.
-You can administer all users in the GitLab instance from the Admin area's Users page:
+You can administer all users in the GitLab instance from the **Admin** area's Users page:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
@@ -168,7 +169,7 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** Self-managed, GitLab Dedicated
-An administrator can export user permissions for all users in the GitLab instance from the Admin area's Users page.
+An administrator can export user permissions for all users in the GitLab instance from the **Admin** area's Users page.
The export lists direct membership the users have in groups and projects.
The following data is included in the export:
@@ -228,7 +229,7 @@ It is also possible to [limit which roles can create a subgroup within a group](
## Administering groups
-You can administer all groups in the GitLab instance from the Admin area's Groups page.
+You can administer all groups in the GitLab instance from the **Admin** area's Groups page.
To access the Groups page:
@@ -323,7 +324,7 @@ To merge topics:
## Administering Gitaly servers
-You can list all Gitaly servers in the GitLab instance from the Admin area's **Gitaly servers**
+You can list all Gitaly servers in the GitLab instance from the **Admin** area's **Gitaly servers**
page. For more details, see [Gitaly](gitaly/index.md).
To access the **Gitaly servers** page:
@@ -347,7 +348,7 @@ For each Gitaly server, the following details are listed:
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/340859) from **Overview > Runners** to **CI/CD > Runners** in GitLab 15.8.
-You can administer all runners in the GitLab instance from the Admin area's **Runners** page. See
+You can administer all runners in the GitLab instance from the **Admin** area's **Runners** page. See
[GitLab Runner](https://docs.gitlab.com/runner/) for more information.
To access the **Runners** page:
@@ -404,7 +405,7 @@ You can also edit, pause, or remove each runner.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/386311) from **Overview > Jobs** to **CI/CD > Jobs** in GitLab 15.8.
-You can administer all jobs in the GitLab instance from the Admin area's Jobs page.
+You can administer all jobs in the GitLab instance from the **Admin** area's Jobs page.
To access the Jobs page:
@@ -429,7 +430,7 @@ For each job, the following details are listed:
## Monitoring section
-The following topics document the **Monitoring** section of the Admin area.
+The following topics document the **Monitoring** section of the **Admin** area.
### System information
@@ -466,7 +467,7 @@ The Sidekiq dashboard consists of the following elements:
### Logs
-**Log** view has been removed from the Admin area dashboard since the logging does not work in multi-node setups and could cause confusion for administrators by displaying partial information.
+**Log** view has been removed from the **Admin** area dashboard since the logging does not work in multi-node setups and could cause confusion for administrators by displaying partial information.
For multi-node systems we recommend ingesting the logs into services like Elasticsearch and Splunk.
diff --git a/doc/administration/auditor_users.md b/doc/administration/auditor_users.md
index b9264751bd65a42f5b81fd5467ebca315b656acb..6827411ab11a5200e8877178d589767c0d9992d9 100644
--- a/doc/administration/auditor_users.md
+++ b/doc/administration/auditor_users.md
@@ -12,7 +12,7 @@ DETAILS:
Users with auditor access have read-only access to all groups, projects, and other resources except:
-- The [Admin area](../administration/admin_area.md).
+- The [**Admin** area](../administration/admin_area.md).
- Project and group settings.
For more information, see [Auditor user permissions and restrictions](#auditor-user-permissions-and-restrictions)
@@ -49,7 +49,7 @@ You can also give users auditor access using [SAML groups](../integration/saml.m
## Auditor user permissions and restrictions
-Auditor access is _not_ a read-only version of administrator access because it doesn't permit access to the Admin area.
+Auditor access is _not_ a read-only version of administrator access because it doesn't permit access to the **Admin** area.
For access to their own resources and resources within a group or project where they are a member,
users with auditor access have the same [permissions](../user/permissions.md) as regular users.
@@ -61,7 +61,7 @@ If you are signed in with auditor access, you:
- Have [permissions](../user/permissions.md) based on your role to projects and groups you are a member of. For example, if you have the Developer role,
you can push commits or comment on issues.
- Can access the same resources using the GitLab UI or API.
-- Can't view the Admin area, or perform any administration actions.
+- Can't view the **Admin** area, or perform any administration actions.
- Can't view job logs when [debug logging](../ci/variables/index.md#enable-debug-logging) is enabled.
## Maintain auditor users using API
diff --git a/doc/administration/cicd.md b/doc/administration/cicd.md
index 0753d7c62d923046a693fbf25da5084567356b34..694b59ef32565d78bae8d94a10730a7510a073c3 100644
--- a/doc/administration/cicd.md
+++ b/doc/administration/cicd.md
@@ -175,7 +175,7 @@ in GitLab 18.0. Runner authentication tokens should be used instead. For more in
Prerequisites:
-- Runner registration tokens must be [enabled](../administration/settings/continuous_integration.md#enable-runner-registrations-tokens) in the Admin area.
+- Runner registration tokens must be [enabled](../administration/settings/continuous_integration.md#enable-runner-registrations-tokens) in the **Admin** area.
```ruby
Gitlab::CurrentSettings.current_application_settings.runners_registration_token
diff --git a/doc/administration/dedicated/configure_instance.md b/doc/administration/dedicated/configure_instance.md
index 4d31447274ef72795039981e117cdce33cc57616..e04315ee24a23f7fbb9d73ca9d141f199fcd81fe 100644
--- a/doc/administration/dedicated/configure_instance.md
+++ b/doc/administration/dedicated/configure_instance.md
@@ -13,7 +13,7 @@ DETAILS:
The instructions on this page guide you through configuring your GitLab Dedicated instance, including enabling and updating the settings for [available functionality](../../subscriptions/gitlab_dedicated/index.md#available-features).
-Any functionality in the GitLab application that is not controlled by the SaaS environment can be configured by using the [Admin area](../../administration/admin_area.md).
+Any functionality in the GitLab application that is not controlled by the SaaS environment can be configured by using the [**Admin** area](../../administration/admin_area.md).
Examples of SaaS environment settings include `gitlab.rb` configurations and access to shell, Rails console, and PostgreSQL console.
These environment settings cannot be changed by tenants.
diff --git a/doc/administration/geo/index.md b/doc/administration/geo/index.md
index 2212ea237128e211b8a5bd406137ded0849c5235..fc43359d29ba748f9c13ce681db50c6e920dd3b6 100644
--- a/doc/administration/geo/index.md
+++ b/doc/administration/geo/index.md
@@ -166,7 +166,7 @@ If you are only using `HTTPS` for external/internal URLs, it is not necessary to
#### Internal URL
HTTP requests from any Geo secondary site to the primary Geo site use the Internal URL of the primary
-Geo site. If this is not explicitly defined in the primary Geo site settings in the Admin area, the
+Geo site. If this is not explicitly defined in the primary Geo site settings in the **Admin** area, the
public URL of the primary site is used.
To update the internal URL of the primary Geo site:
diff --git a/doc/administration/geo/replication/datatypes.md b/doc/administration/geo/replication/datatypes.md
index 08fd480669e578a5751e09c11aadedb63eafc188..0802df4241c0a51628cf7cc3c818ebb5ac85508d 100644
--- a/doc/administration/geo/replication/datatypes.md
+++ b/doc/administration/geo/replication/datatypes.md
@@ -95,7 +95,7 @@ The Gitaly gRPC API does the communication, with three possible ways of synchron
- Using regular Git clone/fetch from one Geo site to another (with special authentication).
- Using repository snapshots (for when the first method fails or repository is corrupt).
-- Manual trigger from the Admin area (a combination of both of the above).
+- Manual trigger from the **Admin** area (a combination of both of the above).
Each project can have at most 3 different repositories:
diff --git a/doc/administration/geo/replication/troubleshooting/client_http.md b/doc/administration/geo/replication/troubleshooting/client_http.md
index 93dbd60625601a41fc68a6233c3605c3253a7be0..1da27de945f66c356b3f4a3ae37176b829a5dba2 100644
--- a/doc/administration/geo/replication/troubleshooting/client_http.md
+++ b/doc/administration/geo/replication/troubleshooting/client_http.md
@@ -74,7 +74,7 @@ To resolve this issue:
If you still get this error, you can further increase the buffer size by repeating the steps above
and changing the `8k` size, for example by doubling it to `16k`.
-### Geo Admin area shows 'Unknown' for health status and 'Request failed with status code 401'
+### Geo Admin area shows `Unknown` for health status and 'Request failed with status code 401'
If using a load balancer, ensure that the load balancer's URL is set as the `external_url` in the
`/etc/gitlab/gitlab.rb` of the nodes behind the load balancer.
@@ -142,7 +142,7 @@ You can have only one wildcard domain in the `no_proxy` list.
### Geo Admin area returns 404 error for a secondary site
Sometimes `sudo gitlab-rake gitlab:geo:check` indicates that **Rails nodes of the secondary** sites are
-healthy, but a 404 Not Found error message for the **secondary** site is returned in the Geo Admin area on the web interface for
+healthy, but a 404 Not Found error message for the **secondary** site is returned in the Geo **Admin** area on the web interface for
the **primary** site.
To resolve this issue:
diff --git a/doc/administration/geo/replication/troubleshooting/common.md b/doc/administration/geo/replication/troubleshooting/common.md
index 49e8af17331e8728091670078bf7be9271fd9e99..9991876eed9778126519bb686848ff72c2b14cf6 100644
--- a/doc/administration/geo/replication/troubleshooting/common.md
+++ b/doc/administration/geo/replication/troubleshooting/common.md
@@ -282,9 +282,9 @@ sudo gitlab-rake gitlab:geo:check
Checking Geo ... Finished
```
- Ensure you have added the secondary site in the Admin area under **Geo > Sites** on the web interface for the **primary** site.
+ Ensure you have added the secondary site in the **Admin** area under **Geo > Sites** on the web interface for the **primary** site.
Also ensure you entered the `gitlab_rails['geo_node_name']`
- when adding the secondary site in the Admin area of the **primary** site.
+ when adding the secondary site in the **Admin** area of the **primary** site.
- Check returns `Exception: PG::UndefinedTable: ERROR: relation "geo_nodes" does not exist`.
@@ -457,7 +457,7 @@ This machine's Geo node name matches a database record ... no
```
For more information about recommended site names in the description of the Name field, see
-[Geo Admin area Common Settings](../../../../administration/geo_sites.md#common-settings).
+[Geo **Admin** area Common Settings](../../../../administration/geo_sites.md#common-settings).
### Check OS locale data compatibility
@@ -472,7 +472,7 @@ See the [PostgreSQL wiki for more details](https://wiki.postgresql.org/wiki/Loca
## Fixing common errors
-This section documents common error messages reported in the Admin area on the web interface, and how to fix them.
+This section documents common error messages reported in the **Admin** area on the web interface, and how to fix them.
### Geo database configuration file is missing
diff --git a/doc/administration/geo/replication/troubleshooting/replication.md b/doc/administration/geo/replication/troubleshooting/replication.md
index 5bbc0e8fa4f01824a090af3f8d80bbd09ab873e4..b1976c11b68934b84a761ac2aac3bfe1c8b237de 100644
--- a/doc/administration/geo/replication/troubleshooting/replication.md
+++ b/doc/administration/geo/replication/troubleshooting/replication.md
@@ -353,7 +353,7 @@ to enact the following, basic troubleshooting steps:
#### Resync and reverify multiple components
NOTE:
-There is an [issue to implement this functionality in the Admin area UI](https://gitlab.com/gitlab-org/gitlab/-/issues/364729).
+There is an [issue to implement this functionality in the **Admin** area UI](https://gitlab.com/gitlab-org/gitlab/-/issues/364729).
WARNING:
Commands that change data can cause damage if not run correctly or under the right conditions. Always run commands in a test environment first and have a backup instance ready to restore.
diff --git a/doc/administration/geo/replication/troubleshooting/synchronization.md b/doc/administration/geo/replication/troubleshooting/synchronization.md
index bade06fc6efa7fe19b5bbe3344c2359b343159be..a043b5dc1fb5df33a6417cbbde58894bdb5ad8b0 100644
--- a/doc/administration/geo/replication/troubleshooting/synchronization.md
+++ b/doc/administration/geo/replication/troubleshooting/synchronization.md
@@ -57,7 +57,7 @@ You can perform a similar operation with other the Models handled by the [Geo Se
NOTE:
`GroupWikiRepository` is not in the previous list since verification is not implemented.
-There is an [issue to implement this functionality in the Admin area UI](https://gitlab.com/gitlab-org/gitlab/-/issues/364729).
+There is an [issue to implement this functionality in the **Admin** area UI](https://gitlab.com/gitlab-org/gitlab/-/issues/364729).
## Message: `Synchronization failed - Error syncing repository`
diff --git a/doc/administration/geo/secondary_proxy/runners.md b/doc/administration/geo/secondary_proxy/runners.md
index 557c7152728cc4dc5a97ed2ec5ef58709dbd7f9a..43d319abe61ff49d9232b4dd2686b3edfd18981a 100644
--- a/doc/administration/geo/secondary_proxy/runners.md
+++ b/doc/administration/geo/secondary_proxy/runners.md
@@ -57,7 +57,7 @@ If you are not concerned about these issues, there is nothing to do here.
You must have administrator access to use any of the following methods:
-- Through the Admin area:
+- Through the **Admin** area:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Runners**.
1. Identify the runners you would like to pause.
diff --git a/doc/administration/geo/setup/two_single_node_external_services.md b/doc/administration/geo/setup/two_single_node_external_services.md
index 9f6f48e3e1f200c981c2bbe0443b94bec5640bca..6894fe5c498a817e40e3446dde6fafac797fc4d2 100644
--- a/doc/administration/geo/setup/two_single_node_external_services.md
+++ b/doc/administration/geo/setup/two_single_node_external_services.md
@@ -283,7 +283,7 @@ Fast lookup is [required for Geo](../../operations/fast_ssh_key_lookup.md#fast-l
NOTE:
Authentication is handled by the primary site. Don't set up custom authentication for the secondary site.
-Any change that requires access to the Admin area should be made in the primary site, because the
+Any change that requires access to the **Admin** area should be made in the primary site, because the
secondary site is a read-only copy.
#### Add the secondary site
diff --git a/doc/administration/geo/setup/two_single_node_sites.md b/doc/administration/geo/setup/two_single_node_sites.md
index c007eca6bf8f7aa3f58ca63a50eb67e66251f1b6..2ec86c9306384604ab1a1cbed3b7ee672955ecee 100644
--- a/doc/administration/geo/setup/two_single_node_sites.md
+++ b/doc/administration/geo/setup/two_single_node_sites.md
@@ -403,7 +403,7 @@ Fast lookup is [required for Geo](../../operations/fast_ssh_key_lookup.md#fast-l
NOTE:
Authentication is handled by the primary site. Don't set up custom authentication for the secondary site.
-Any change that requires access to the Admin area should be made in the primary site, because the
+Any change that requires access to the **Admin** area should be made in the primary site, because the
secondary site is a read-only copy.
### Manually replicate secret GitLab values
diff --git a/doc/administration/geo_sites.md b/doc/administration/geo_sites.md
index 3ab41866182e12d8f8018fba34f57af08305af36..0ee3923f653302962eabd8693991b1aad85f583a 100644
--- a/doc/administration/geo_sites.md
+++ b/doc/administration/geo_sites.md
@@ -79,7 +79,7 @@ The internal URL defaults to external URL. To change it:
1. Edit the internal URL.
1. Select **Save changes**.
-When enabled, the Admin area for Geo shows replication details for each site directly
+When enabled, the **Admin** area for Geo shows replication details for each site directly
from the primary site's UI, and through the Geo secondary proxy, if enabled.
WARNING:
diff --git a/doc/administration/get_started.md b/doc/administration/get_started.md
index 36d1e2df15a5194f87922f32d9f57165aa815007..cfc96292150ad5d6f8694f6d97f7b54808a84a63 100644
--- a/doc/administration/get_started.md
+++ b/doc/administration/get_started.md
@@ -249,7 +249,7 @@ Rate limits also improve the security of your application.
### Configure rate limits for self-managed GitLab
-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).
+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).
- Define [issues rate limits](settings/rate_limit_on_issues_creation.md) to set a maximum number of issue creation requests per minute, per user.
- Enforce [user and IP rate limits](settings/user_and_ip_rate_limits.md) for unauthenticated web requests.
@@ -267,7 +267,7 @@ Rate limits also improve the security of your application.
### Configure rate limits for GitLab SaaS
-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).
+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).
- Review the rate limit page.
- Read our [API page](../api/rest/index.md) for more information about API and rate limiting.
diff --git a/doc/administration/gitaly/configure_gitaly.md b/doc/administration/gitaly/configure_gitaly.md
index 4451e64070ece6dff06fa67ed1ec01777849385e..c8e7ce4d006c57efbbdca3845843ae378e8f9f49 100644
--- a/doc/administration/gitaly/configure_gitaly.md
+++ b/doc/administration/gitaly/configure_gitaly.md
@@ -531,7 +531,7 @@ reconfigure the GitLab application servers to remove the `default` entry from `g
To work around the limitation:
1. Define an additional storage location on the new Gitaly service and configure the additional storage to be `default`.
-1. In the [Admin area](../repository_storage_paths.md#configure-where-new-repositories-are-stored), set `default` to a weight of zero
+1. In the [**Admin** area](../repository_storage_paths.md#configure-where-new-repositories-are-stored), set `default` to a weight of zero
to prevent repositories being stored there.
### Disable Gitaly where not required (optional)
diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md
index 333de105fbfd855358303aea29af2115a8e24f68..55042649092279f1ab5b033cd3a0bd9e9d03248d 100644
--- a/doc/administration/instance_limits.md
+++ b/doc/administration/instance_limits.md
@@ -665,7 +665,7 @@ The total number of custom domains per GitLab Pages website is limited to `150`
The default limit for [GitLab self-managed](../subscriptions/self_managed/index.md) is `0` (unlimited).
To set a limit on your self-managed instance, use the
-[Admin area](pages/index.md#set-maximum-number-of-gitlab-pages-custom-domains-for-a-project).
+[**Admin** area](pages/index.md#set-maximum-number-of-gitlab-pages-custom-domains-for-a-project).
### Number of extra Pages deployments when using multiple deployments
@@ -1037,7 +1037,7 @@ The default maximum file size for a package that's uploaded to the [GitLab packa
The [maximum file sizes on GitLab.com](../user/gitlab_com/index.md#package-registry-limits)
might be different.
-To set these limits for a self-managed installation, you can do it [through the Admin area](settings/continuous_integration.md#package-file-size-limits)
+To set these limits for a self-managed installation, you can do it [through the **Admin** area](settings/continuous_integration.md#package-file-size-limits)
or run the following in the
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
diff --git a/doc/administration/integration/kroki.md b/doc/administration/integration/kroki.md
index 210a4e09ed3075bbf11f6d97e923dac6de6ee99b..f7242ba88d6396300b31d373e40be4fc3d01b87f 100644
--- a/doc/administration/integration/kroki.md
+++ b/doc/administration/integration/kroki.md
@@ -15,7 +15,7 @@ you can create diagrams-as-code within AsciiDoc, Markdown, reStructuredText, and
## Enable Kroki in GitLab
-You need to enable Kroki integration from Settings under Admin area.
+You need to enable Kroki integration from Settings under **Admin** area.
To do that, sign in with an administrator account and follow these steps:
1. On the left sidebar, at the bottom, select **Admin**.
diff --git a/doc/administration/job_artifacts.md b/doc/administration/job_artifacts.md
index 65e33c10f3c321efa89a5d1a006a04a1c3ac607f..422ef74303aa32a063542a610968964fa05fd12a 100644
--- a/doc/administration/job_artifacts.md
+++ b/doc/administration/job_artifacts.md
@@ -382,13 +382,13 @@ To change the default schedule on which expired artifacts are deleted:
## Set the maximum file size of the artifacts
If artifacts are enabled, you can change the maximum file size of the
-artifacts through the [Admin area settings](../administration/settings/continuous_integration.md#maximum-artifacts-size).
+artifacts through the [**Admin** area settings](../administration/settings/continuous_integration.md#maximum-artifacts-size).
## Storage statistics
You can see the total storage used for job artifacts for groups and projects in:
-- The Admin area
+- The **Admin** area
- The [groups](../api/groups.md) and [projects](../api/projects.md) APIs
## Implementation details
diff --git a/doc/administration/labels.md b/doc/administration/labels.md
index f681dc1eb68e3837501e92e6db8241920da5461a..7c71affe91f70b70bfd2a37ef65b03d72d1d2282 100644
--- a/doc/administration/labels.md
+++ b/doc/administration/labels.md
@@ -17,9 +17,9 @@ To manage labels for the GitLab instance:
For more details on how to manage labels, see [Labels](../user/project/labels.md).
-Labels created in the Admin area are automatically added to new projects.
+Labels created in the **Admin** area are automatically added to new projects.
They are not available to new groups.
-Updating or adding labels in the Admin area does not modify labels in existing projects.
+Updating or adding labels in the **Admin** area does not modify labels in existing projects.
diff --git a/doc/administration/lfs/index.md b/doc/administration/lfs/index.md
index 5aaa52c4cff0d9d417a97f14c758daf557a8826b..07d7c45a3913fba31f78859065d698d695346fd1 100644
--- a/doc/administration/lfs/index.md
+++ b/doc/administration/lfs/index.md
@@ -442,7 +442,7 @@ To switch Git LFS to use pure SSH protocol:
You can see the total storage used for LFS objects for groups and projects in:
-- The Admin area
+- The **Admin** area
- The [groups](../../api/groups.md) and [projects](../../api/projects.md) APIs
## Related topics
diff --git a/doc/administration/maintenance_mode/index.md b/doc/administration/maintenance_mode/index.md
index e6e6e9f742d58d4744724180ea7c9b4ba54c366c..8f5dc6a5db0d2d964964e55996fa1876a6d44d16 100644
--- a/doc/administration/maintenance_mode/index.md
+++ b/doc/administration/maintenance_mode/index.md
@@ -122,7 +122,7 @@ For most JSON requests, `POST`, `PUT`, `PATCH`, and `DELETE` are blocked, and th
| `POST` | Paths ending with `/compare`| Git revision routes. |
| `POST` | `.git/git-upload-pack` | To allow Git pull/clone. |
| `POST` | `/api/v4/internal` | [internal API routes](../../development/internal_api/index.md) |
-| `POST` | `/admin/sidekiq` | To allow management of background jobs in the Admin area |
+| `POST` | `/admin/sidekiq` | To allow management of background jobs in the **Admin** area |
| `POST` | `/admin/geo` | To allow updating Geo Nodes in the administrator UI |
| `POST` | `/api/v4/geo_replication`| To allow certain Geo-specific administrator UI actions on secondary sites |
diff --git a/doc/administration/moderate_users.md b/doc/administration/moderate_users.md
index c3d18c6a2b46e751f7c259c891834fe47fdacdd7..aafd800fe41b85eb725c0072d00929f6aeb6581c 100644
--- a/doc/administration/moderate_users.md
+++ b/doc/administration/moderate_users.md
@@ -55,7 +55,7 @@ To view user sign ups pending approval:
> - Ability to filter a user by state [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/238183) in GitLab 17.0.
-A user sign up pending approval can be approved or rejected from the Admin area.
+A user sign up pending approval can be approved or rejected from the **Admin** area.
To approve or reject a user sign up:
@@ -102,13 +102,13 @@ To block a user:
The user receives an email notification that their account has been blocked. After this email, they no longer receive notifications.
-To report abuse from other users, see [report abuse](../user/report_abuse.md). For more information on abuse reports in the Admin area, see [resolving abuse reports](../administration/review_abuse_reports.md#resolving-abuse-reports).
+To report abuse from other users, see [report abuse](../user/report_abuse.md). For more information on abuse reports in the **Admin** area, see [resolving abuse reports](../administration/review_abuse_reports.md#resolving-abuse-reports).
### Unblock a user
> - Ability to filter a user by state [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/238183) in GitLab 17.0.
-A blocked user can be unblocked from the Admin area. To do this:
+A blocked user can be unblocked from the **Admin** area. To do this:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
@@ -226,7 +226,7 @@ A maximum of 240,000 users can be deleted per day.
> - Ability to filter a user by state [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/238183) in GitLab 17.0.
-A deactivated user can be activated from the Admin area.
+A deactivated user can be activated from the **Admin** area.
To do this:
@@ -260,7 +260,7 @@ A banned user:
To block a user and hide their contributions, administrators can ban the user.
-Users can be banned using the Admin area. To do this:
+Users can be banned using the **Admin** area. To do this:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
@@ -270,7 +270,7 @@ Users can be banned using the Admin area. To do this:
> - Ability to filter a user by state [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/238183) in GitLab 17.0.
-A banned user can be unbanned using the Admin area. To do this:
+A banned user can be unbanned using the **Admin** area. To do this:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
@@ -282,7 +282,7 @@ The user's state is set to active and they consume a
## Delete a user
-Use the Admin area to delete users.
+Use the **Admin** area to delete users.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
@@ -309,7 +309,7 @@ Before 15.1, additionally groups of which deleted user were the only owner among
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/132402) in GitLab 16.5.
> - Ability to filter a user by state [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/238183) in GitLab 17.0.
-You can trust and untrust users from the Admin area.
+You can trust and untrust users from the **Admin** area.
By default, a user is not trusted and is blocked from creating issues, notes, and snippets considered to be spam. When you trust a user, they can create issues, notes, and snippets without being blocked.
diff --git a/doc/administration/monitoring/performance/grafana_configuration.md b/doc/administration/monitoring/performance/grafana_configuration.md
index 1d613f5a34992809835ecaf4a27b26e8b1ce53d1..89dc59642dc8485cf5d40d7363859037f07cf38c 100644
--- a/doc/administration/monitoring/performance/grafana_configuration.md
+++ b/doc/administration/monitoring/performance/grafana_configuration.md
@@ -29,12 +29,12 @@ GitLab sidebar:
1. Configure the **Grafana URL**. Enter the full URL of the Grafana instance.
1. Select **Save changes**.
-GitLab displays your link in the Admin area under **Monitoring > Metrics Dashboard**.
+GitLab displays your link in the **Admin** area under **Monitoring > Metrics Dashboard**.
## Required Scopes
When setting up Grafana through the process above, no scope shows in the screen in
-the Admin area under **Applications > GitLab Grafana**. However, the `read_user` scope is
+the **Admin** area under **Applications > GitLab Grafana**. However, the `read_user` scope is
required and is provided to the application automatically. Setting any scope other than
`read_user` without also including `read_user` leads to this error when you try to sign in using
GitLab as the OAuth provider:
diff --git a/doc/administration/pages/index.md b/doc/administration/pages/index.md
index d57ca09975ccf39563d19c36d589cc8936afdba0..29bbfe97839a8e9fad5d17377ffc8a624b3bfb97 100644
--- a/doc/administration/pages/index.md
+++ b/doc/administration/pages/index.md
@@ -660,7 +660,7 @@ To do that:
1. Select **Save changes**.
NOTE:
-You must enable [Access Control](#access-control) first for the setting to show in the Admin area.
+You must enable [Access Control](#access-control) first for the setting to show in the **Admin** area.
### Running behind a proxy
diff --git a/doc/administration/reporting/spamcheck.md b/doc/administration/reporting/spamcheck.md
index 1378696499ba950ea81b2089f58f2c9d64cbd130..58515ab429a1fa1dda1c9896ecb4d2c6df519198 100644
--- a/doc/administration/reporting/spamcheck.md
+++ b/doc/administration/reporting/spamcheck.md
@@ -67,4 +67,4 @@ Spamcheck service on its own cannot communicate directly over TLS with GitLab.
However, Spamcheck can be deployed behind a reverse proxy which performs TLS
termination. In such a scenario, GitLab can be made to communicate with
Spamcheck over TLS by specifying `tls://` scheme for the external Spamcheck URL
-instead of `grpc://` in the Admin area settings.
+instead of `grpc://` in the **Admin** area settings.
diff --git a/doc/administration/repository_checks.md b/doc/administration/repository_checks.md
index 0ef1a5cc561f875a0702eb8cc8bdc1a189e7ad6e..87154962f5d5f61735229a865908ef65b598e8ef 100644
--- a/doc/administration/repository_checks.md
+++ b/doc/administration/repository_checks.md
@@ -34,7 +34,7 @@ To check a project's repository using GitLab UI:
1. In the **Repository check** section, select **Trigger repository check**.
The checks run asynchronously so it may take a few minutes before the check result is visible on the
-project page in the Admin area. If the checks fail, see [what to do](#what-to-do-if-a-check-failed).
+project page in the **Admin** area. If the checks fail, see [what to do](#what-to-do-if-a-check-failed).
## Enable repository checks for all projects
diff --git a/doc/administration/repository_storage_paths.md b/doc/administration/repository_storage_paths.md
index 8cd632e9ae30d4f1ba278226bcce3c6276f4abc1..62dca60fb9611406cb1916f239b4d7d7d9a0d7f2 100644
--- a/doc/administration/repository_storage_paths.md
+++ b/doc/administration/repository_storage_paths.md
@@ -65,10 +65,10 @@ translate between the human-readable project name and the hashed storage path. Y
Administrators can look up a project's hashed path from its name or ID using:
-- The [Admin area](../administration/admin_area.md#administering-projects).
+- The [**Admin** area](../administration/admin_area.md#administering-projects).
- A Rails console.
-To look up a project's hash path in the Admin area:
+To look up a project's hash path in the **Admin** area:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Projects** and select the project.
diff --git a/doc/administration/review_abuse_reports.md b/doc/administration/review_abuse_reports.md
index fd33346b7ba3b813e5d08f2f3d128d00880191ed..005f34f68ef15c9063c6e349b822f012842df1bc 100644
--- a/doc/administration/review_abuse_reports.md
+++ b/doc/administration/review_abuse_reports.md
@@ -13,7 +13,7 @@ DETAILS:
View and resolve abuse reports from GitLab users.
GitLab administrators can view and [resolve](#resolving-abuse-reports) abuse
-reports in the Admin area.
+reports in the **Admin** area.
## Receive notification of abuse reports by email
diff --git a/doc/administration/review_spam_logs.md b/doc/administration/review_spam_logs.md
index b4e5de13868dec783be6c1e5e64ebbbe57ad7f56..ce640f4745549e579a68f7e94c61ba17b52ad2a5 100644
--- a/doc/administration/review_spam_logs.md
+++ b/doc/administration/review_spam_logs.md
@@ -12,7 +12,7 @@ DETAILS:
GitLab tracks user activity and flags certain behavior for potential spam.
-In the Admin area, a GitLab administrator can view and resolve spam logs.
+In the **Admin** area, a GitLab administrator can view and resolve spam logs.
## Manage spam logs
diff --git a/doc/administration/settings/account_and_limit_settings.md b/doc/administration/settings/account_and_limit_settings.md
index 372f0af8b976a9ab23f471bc95ba9dd691f68e76..a3f7652e16de5513d1831adc5305544de3b38a3a 100644
--- a/doc/administration/settings/account_and_limit_settings.md
+++ b/doc/administration/settings/account_and_limit_settings.md
@@ -294,7 +294,7 @@ To do this:
NOTE:
When this ability is disabled, GitLab administrators can still use the
-[Admin area](../../administration/admin_area.md#administering-users) or the
+[**Admin** area](../../administration/admin_area.md#administering-users) or the
[API](../../api/users.md#user-modification) to update usernames.
## Prevent users from creating organizations
diff --git a/doc/administration/settings/continuous_integration.md b/doc/administration/settings/continuous_integration.md
index 8dd1516ea8bf4d51f65ec5d3e7e450f4d90b3271..55fad6f88a3337c60a0a6d27325f8c0da743e32a 100644
--- a/doc/administration/settings/continuous_integration.md
+++ b/doc/administration/settings/continuous_integration.md
@@ -10,7 +10,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed
-The [Admin area](index.md) has the instance settings for Auto DevOps, runners, and
+The [**Admin** area](index.md) has the instance settings for Auto DevOps, runners, and
job artifacts.
## Auto DevOps
@@ -132,7 +132,7 @@ The value is in MB, and the default value is 100 MB per job. An administrator ca
## Default artifacts expiration
The default expiration time of the [job artifacts](../../administration/job_artifacts.md)
-can be set in the Admin area of your GitLab instance. The syntax of duration is
+can be set in the **Admin** area of your GitLab instance. The syntax of duration is
described in [`artifacts:expire_in`](../../ci/yaml/index.md#artifactsexpire_in)
and the default value is `30 days`.
@@ -232,7 +232,7 @@ The default value is `0` (no restriction).
## Default CI/CD configuration file
-The default CI/CD configuration file and path for new projects can be set in the Admin area
+The default CI/CD configuration file and path for new projects can be set in the **Admin** area
of your GitLab instance (`.gitlab-ci.yml` if not set):
1. On the left sidebar, at the bottom, select **Admin**.
@@ -247,7 +247,7 @@ It is also possible to specify a [custom CI/CD configuration file for a specific
> - **Maximum number of active pipelines per project** setting [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/368195) in GitLab 16.0.
You can configure some [CI/CD limits](../../administration/instance_limits.md#cicd-limits)
-from the Admin area:
+from the **Admin** area:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
diff --git a/doc/administration/settings/push_event_activities_limit.md b/doc/administration/settings/push_event_activities_limit.md
index 26523560d41ea0deedeafce79ec35e9ad966590b..8d89a57659ea22013590abfe7ee51a9aea5abaf7 100644
--- a/doc/administration/settings/push_event_activities_limit.md
+++ b/doc/administration/settings/push_event_activities_limit.md
@@ -27,7 +27,7 @@ the activity feed.
To modify this setting:
-- In the Admin area:
+- In the **Admin** area:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Network**.
1. Expand **Performance optimization**.
diff --git a/doc/administration/settings/scim_setup.md b/doc/administration/settings/scim_setup.md
index 7cfbe9cc42206efc8cd8001ddeeec7b7ce63792f..a68b3fb98491a4def5edb1c729c6e3cdbaf40201 100644
--- a/doc/administration/settings/scim_setup.md
+++ b/doc/administration/settings/scim_setup.md
@@ -62,7 +62,7 @@ Prerequisites:
To configure Okta for SCIM:
1. Sign in to Okta.
-1. In the upper-right corner, select **Admin**. The button is not visible from the Admin area.
+1. In the upper-right corner, select **Admin**. The button is not visible from the **Admin** area.
1. In the **Application** tab, select **Browse App Catalog**.
1. Find and select the **GitLab** application.
1. On the GitLab application overview page, select **Add Integration**.
diff --git a/doc/administration/settings/security_and_compliance.md b/doc/administration/settings/security_and_compliance.md
index 071e92bb07900586d85331e1bdcd86c5e1b12869..41cafd31f03b36849e22a27e7020e83b524105a0 100644
--- a/doc/administration/settings/security_and_compliance.md
+++ b/doc/administration/settings/security_and_compliance.md
@@ -10,7 +10,7 @@ DETAILS:
**Tier:** Ultimate
**Offering:** Self-managed
-The settings for package metadata synchronization are located in the [Admin area](index.md).
+The settings for package metadata synchronization are located in the [**Admin** area](index.md).
## Choose package registry metadata to sync
diff --git a/doc/administration/settings/usage_statistics.md b/doc/administration/settings/usage_statistics.md
index d65dae4b91c4cf82650b3b88d49ada738c98448f..f3d9b5dd9839fc75ef0d4797948a832b76919861 100644
--- a/doc/administration/settings/usage_statistics.md
+++ b/doc/administration/settings/usage_statistics.md
@@ -95,7 +95,7 @@ In the following table, you can see:
If enabled, version check informs you if a new version is available and the
importance of it through a status. The status displays on the help pages (`/help`)
-for all authenticated users, and on the Admin area pages. The statuses are:
+for all authenticated users, and on the **Admin** area pages. The statuses are:
- Green: You are running the latest version of GitLab.
- Orange: An updated version of GitLab is available.
@@ -155,7 +155,7 @@ To enable or disable Service Ping:
### Through the configuration file
To disable Service Ping and prevent it from being configured in the future through
-the Admin area.
+the **Admin** area.
::Tabs
@@ -248,7 +248,7 @@ To enable or disable optional data in Service Ping:
## Access the Service Ping payload
-You can access the exact JSON payload sent to GitLab Inc. in the Admin area or through the API.
+You can access the exact JSON payload sent to GitLab Inc. in the **Admin** area or through the API.
See an [example Service Ping payload](../../development/internal_analytics/service_ping/index.md#example-service-ping-payload).
### In the UI
diff --git a/doc/administration/settings/user_and_ip_rate_limits.md b/doc/administration/settings/user_and_ip_rate_limits.md
index c9e116740d45e4cb234b99d72216e4d4ed92b244..b08883fbfd75f55a0d06fa99a6e9360f6d0c1d58 100644
--- a/doc/administration/settings/user_and_ip_rate_limits.md
+++ b/doc/administration/settings/user_and_ip_rate_limits.md
@@ -120,7 +120,7 @@ attached into the response headers.
| Header | Example | Description |
|:----------------------|:--------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `RateLimit-Limit` | `60` | The request quota for the client **each minute**. If the rate limit period set in the Admin area is different from 1 minute, the value of this header is adjusted to approximately the nearest 60-minute period. |
+| `RateLimit-Limit` | `60` | The request quota for the client **each minute**. If the rate limit period set in the **Admin** area is different from 1 minute, the value of this header is adjusted to approximately the nearest 60-minute period. |
| `RateLimit-Name` | `throttle_authenticated_web` | Name of the throttle blocking the requests. |
| `RateLimit-Observed` | `67` | Number of requests associated to the client in the time window. |
| `RateLimit-Remaining` | `0` | Remaining quota in the time window. The result of `RateLimit-Limit` - `RateLimit-Observed`. |
@@ -223,7 +223,7 @@ request continue. The log message contains an `env` field set to `track`. The `m
field contains the name of throttle that was hit.
It is important to set the environment variable **before** enabling
-the rate limiting in the settings. The settings in the Admin area
+the rate limiting in the settings. The settings in the **Admin** area
take effect immediately, while setting the environment variable
requires a restart of all the Puma processes.
diff --git a/doc/administration/sidekiq/sidekiq_troubleshooting.md b/doc/administration/sidekiq/sidekiq_troubleshooting.md
index 7319e2738178d0cf727d74d4982f90f7ad57d080..c7d5c316c7b12b2145e5ccb7fc22a65d6fdfa454 100644
--- a/doc/administration/sidekiq/sidekiq_troubleshooting.md
+++ b/doc/administration/sidekiq/sidekiq_troubleshooting.md
@@ -570,7 +570,7 @@ For more information about Sidekiq jobs, see the [Sidekiq-cron](https://github.c
## Disabling cron jobs
-You can disable any Sidekiq cron jobs by visiting the [Monitoring section in the Admin area](../admin_area.md#monitoring-section). You can also perform the same action using the command line and [Rails Runner](../operations/rails_console.md#using-the-rails-runner).
+You can disable any Sidekiq cron jobs by visiting the [Monitoring section in the **Admin** area](../admin_area.md#monitoring-section). You can also perform the same action using the command line and [Rails Runner](../operations/rails_console.md#using-the-rails-runner).
To disable all cron jobs:
diff --git a/doc/administration/snippets/index.md b/doc/administration/snippets/index.md
index ae2862334f2bcd4e32656f42215a4c2a93493ad4..fe4e2447bd8ed0c4221f2f75fbb6bff7466fba73 100644
--- a/doc/administration/snippets/index.md
+++ b/doc/administration/snippets/index.md
@@ -24,7 +24,7 @@ or the [Application settings API](../../api/settings.md).
The limit **must** be in bytes.
-This setting is not available in the [Admin area settings](../settings/index.md).
+This setting is not available in the [**Admin** area settings](../settings/index.md).
### Use the Rails console
diff --git a/doc/administration/static_objects_external_storage.md b/doc/administration/static_objects_external_storage.md
index f4ff901eb1fe28d964d2f2a43906ead84052f34b..d2e97d6b18f9ca14b838ac4378f1eb2078dccc07 100644
--- a/doc/administration/static_objects_external_storage.md
+++ b/doc/administration/static_objects_external_storage.md
@@ -82,7 +82,7 @@ other CDNs or Function as a Service (FaaS) systems should work using the same pr
- `ORIGIN_HOSTNAME`: the hostname of your GitLab installation.
- `STORAGE_TOKEN`: any arbitrary secure token. You can get a token by running
- `pwgen -cn1 64` on a UNIX machine. Save this token for the Admin area, as
+ `pwgen -cn1 64` on a UNIX machine. Save this token for the **Admin** area, as
described in the [configuring](#configure-external-storage) section.
```javascript
diff --git a/doc/administration/user_settings.md b/doc/administration/user_settings.md
index 963afce4b2fb484493fcd029551385f4a771c613..44aded3bbdeb4cddd4f36a3db7a0b1267d8f8a49 100644
--- a/doc/administration/user_settings.md
+++ b/doc/administration/user_settings.md
@@ -48,7 +48,7 @@ For self-compiled installations:
Administrators can:
-- Use the Admin area to [prevent an existing user from creating top-level groups](../administration/admin_area.md#prevent-a-user-from-creating-top-level-groups).
+- Use the **Admin** area to [prevent an existing user from creating top-level groups](../administration/admin_area.md#prevent-a-user-from-creating-top-level-groups).
- Use the [modify an existing user API endpoint](../api/users.md#user-modification) to change the `can_create_group` setting.
## Prevent users from changing their usernames
diff --git a/doc/administration/wikis/index.md b/doc/administration/wikis/index.md
index aefc3a44278c16bd291dc6fce818b7e808d0933b..3fce9424d660b0a67dc66cbcd3e93eb09f01a37b 100644
--- a/doc/administration/wikis/index.md
+++ b/doc/administration/wikis/index.md
@@ -27,7 +27,7 @@ is edited again and the content changes.
### Wiki page content size limit configuration
-This setting is not available through the [Admin area settings](../settings/index.md).
+This setting is not available through the [**Admin** area settings](../settings/index.md).
To configure this setting, use either the Rails console
or the [Application settings API](../../api/settings.md).
diff --git a/doc/api/group_import_export.md b/doc/api/group_import_export.md
index 27b317abd18d885bfecfa4e69858f50507442c19..eb8f6ee5539921a6c6661414c8ee90a4e5a26296 100644
--- a/doc/api/group_import_export.md
+++ b/doc/api/group_import_export.md
@@ -97,7 +97,7 @@ returns either:
The maximum import file size can be set by the Administrator on self-managed instances (default is `0` (unlimited)).
As an administrator, you can modify the maximum import file size either:
-- In the [Admin area](../administration/settings/import_and_export_settings.md).
+- In the [**Admin** area](../administration/settings/import_and_export_settings.md).
- By using the `max_import_size` option in the [Application settings API](settings.md#change-application-settings).
For information on the maximum import file size on GitLab.com, see
diff --git a/doc/api/project_import_export.md b/doc/api/project_import_export.md
index 25feee1bee2f5d68906f23d6a9698b78832e44db..4086fe3fe42b4e84a74e9d0c11738f63223c0951 100644
--- a/doc/api/project_import_export.md
+++ b/doc/api/project_import_export.md
@@ -213,7 +213,7 @@ requests.post(url, headers=headers, data=data, files=files)
NOTE:
The maximum import file size can be set by the Administrator. It defaults to `0` (unlimited).
-As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the [Application settings API](settings.md#change-application-settings) or the [Admin area](../administration/settings/account_and_limit_settings.md).
+As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the [Application settings API](settings.md#change-application-settings) or the [**Admin** area](../administration/settings/account_and_limit_settings.md).
## Import a file from a remote object storage
diff --git a/doc/api/projects.md b/doc/api/projects.md
index 547adf361227573f0d9148d8e73ad10d17fccd65..be466215578fd0a63466f08990277a7bbf027c5a 100644
--- a/doc/api/projects.md
+++ b/doc/api/projects.md
@@ -2571,7 +2571,7 @@ This endpoint:
[default deletion delay](../administration/settings/visibility_and_access_controls.md#deletion-protection).
WARNING:
-The option to delete projects immediately from deletion protection settings in the Admin area was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/389557) in GitLab 15.9 and removed in GitLab 16.0.
+The option to delete projects immediately from deletion protection settings in the **Admin** area was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/389557) in GitLab 15.9 and removed in GitLab 16.0.
```plaintext
DELETE /projects/:id
diff --git a/doc/api/runners.md b/doc/api/runners.md
index a01f8d65f03556d43905ae47fef98829363147a6..cff5a05f66981c8761a57c30ca1442d8a036be54 100644
--- a/doc/api/runners.md
+++ b/doc/api/runners.md
@@ -841,7 +841,7 @@ POST /runners
|--------------------|--------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `token` | string | yes | [Registration token](#registration-and-authentication-tokens) |
| `description` | string | no | Description of the runner |
-| `info` | hash | no | Runner's metadata. You can include `name`, `version`, `revision`, `platform`, and `architecture`, but only `version`, `platform`, and `architecture` are displayed in the Admin area of the UI |
+| `info` | hash | no | Runner's metadata. You can include `name`, `version`, `revision`, `platform`, and `architecture`, but only `version`, `platform`, and `architecture` are displayed in the **Admin** area of the UI |
| `active` | boolean | no | Deprecated: Use `paused` instead. Specifies if the runner is allowed to receive new jobs |
| `paused` | boolean | no | Specifies if the runner should ignore new jobs |
| `locked` | boolean | no | Specifies if the runner should be locked for the current project |
diff --git a/doc/api/settings.md b/doc/api/settings.md
index ec474cccb948b016c1fe326cb4e009fcc3813b83..65b001bbe2dd2084ad2a47aa9fb422da077bcf34 100644
--- a/doc/api/settings.md
+++ b/doc/api/settings.md
@@ -368,8 +368,8 @@ listed in the descriptions of the relevant settings.
| Attribute | Type | Required | Description |
|------------------------------------------|------------------|:------------------------------------:|-------------|
| `admin_mode` | boolean | no | Require administrators to enable Admin Mode by re-authenticating for administrative tasks. |
-| `admin_notification_email` | string | no | Deprecated: Use `abuse_notification_email` instead. If set, [abuse reports](../administration/review_abuse_reports.md) are sent to this address. Abuse reports are always available in the Admin area. |
-| `abuse_notification_email` | string | no | If set, [abuse reports](../administration/review_abuse_reports.md) are sent to this address. Abuse reports are always available in the Admin area. |
+| `admin_notification_email` | string | no | Deprecated: Use `abuse_notification_email` instead. If set, [abuse reports](../administration/review_abuse_reports.md) are sent to this address. Abuse reports are always available in the **Admin** area. |
+| `abuse_notification_email` | string | no | If set, [abuse reports](../administration/review_abuse_reports.md) are sent to this address. Abuse reports are always available in the **Admin** area. |
| `notify_on_unknown_sign_in` | boolean | no | Enable sending notification if sign in from unknown IP address happens. |
| `after_sign_out_path` | string | no | Where to redirect users after logout. |
| `email_restrictions_enabled` | boolean | no | Enable restriction for sign-up by email. |
@@ -394,7 +394,7 @@ listed in the descriptions of the relevant settings.
| `auto_devops_domain` | string | no | Specify a domain to use by default for every project's Auto Review Apps and Auto Deploy stages. |
| `auto_devops_enabled` | boolean | no | Enable Auto DevOps for projects by default. It automatically builds, tests, and deploys applications based on a predefined CI/CD configuration. |
| `automatic_purchased_storage_allocation` | boolean | no | Enabling this permits automatic allocation of purchased storage in a namespace. Relevant only to EE distributions. |
-| `bulk_import_enabled` | boolean | no | Enable migrating GitLab groups by direct transfer. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/383268) in GitLab 15.8. Setting also [available](../administration/settings/import_and_export_settings.md#enable-migration-of-groups-and-projects-by-direct-transfer) in the Admin area. |
+| `bulk_import_enabled` | boolean | no | Enable migrating GitLab groups by direct transfer. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/383268) in GitLab 15.8. Setting also [available](../administration/settings/import_and_export_settings.md#enable-migration-of-groups-and-projects-by-direct-transfer) in the **Admin** area. |
| `bulk_import_max_download_file_size` | integer | no | Maximum download file size when importing from source GitLab instances by direct transfer. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/384976) in GitLab 16.3. |
| `can_create_group` | boolean | no | Indicates whether users can create top-level groups. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/367754) in GitLab 15.5. Defaults to `true`. |
| `check_namespace_plan` | boolean | no | Enabling this makes only licensed EE features available to projects if the project namespace's plan includes the feature or if the project is public. Premium and Ultimate only. |
diff --git a/doc/api/templates/dockerfiles.md b/doc/api/templates/dockerfiles.md
index f6c707288220653b02115f8df30849b6fdf89c93..8c83190528c0679a79117aef4c2c5b49811bb9c4 100644
--- a/doc/api/templates/dockerfiles.md
+++ b/doc/api/templates/dockerfiles.md
@@ -23,7 +23,7 @@ DETAILS:
In [GitLab Premium and Ultimate](https://about.gitlab.com/pricing/) tiers, GitLab instance
administrators can override templates in the
-[Admin area](../../administration/settings/instance_template_repository.md).
+[**Admin** area](../../administration/settings/instance_template_repository.md).
## List Dockerfile templates
diff --git a/doc/ci/pipelines/compute_minutes.md b/doc/ci/pipelines/compute_minutes.md
index 9f5a9196323b6bef2d52a1b23db38f1c4ba9dce4..548bf45ba0869ece37c521ce114c952333bd6432 100644
--- a/doc/ci/pipelines/compute_minutes.md
+++ b/doc/ci/pipelines/compute_minutes.md
@@ -406,12 +406,12 @@ An administrator can reset the compute usage for a namespace for the current mon
### Reset usage for a personal namespace
-1. Find the [user in the Admin area](../../administration/admin_area.md#administering-users).
+1. Find the [user in the **Admin** area](../../administration/admin_area.md#administering-users).
1. Select **Edit**.
1. In **Limits**, select **Reset compute usage**.
### Reset usage for a group namespace
-1. Find the [group in the Admin area](../../administration/admin_area.md#administering-groups).
+1. Find the [group in the **Admin** area](../../administration/admin_area.md#administering-groups).
1. Select **Edit**.
1. In **Permissions and group features**, select **Reset compute usage**.
diff --git a/doc/ci/runners/new_creation_workflow.md b/doc/ci/runners/new_creation_workflow.md
index 27aa76cad6f439b03e86126b43f833b7f4a94010..f21e2ff0eb161c0bea51baea0f44402ddb9209cf 100644
--- a/doc/ci/runners/new_creation_workflow.md
+++ b/doc/ci/runners/new_creation_workflow.md
@@ -78,7 +78,7 @@ To continue using registration tokens after GitLab 17.0:
- On GitLab.com, you can manually [enable the legacy runner registration process](runners_scope.md#enable-use-of-runner-registration-tokens-in-projects-and-groups)
in the top-level group settings until GitLab 18.0.
- On GitLab self-managed, you can manually [enable the legacy runner registration process](../../administration/settings/continuous_integration.md#enable-runner-registrations-tokens)
- in the Admin area settings until GitLab 18.0.
+ in the **Admin** area settings until GitLab 18.0.
## Impact on existing runners
diff --git a/doc/ci/runners/runner_fleet_dashboard_groups.md b/doc/ci/runners/runner_fleet_dashboard_groups.md
index 26e69c0835957ea03d4d43ae128fb0f01bd61dfa..4f2d2a7355280112f110fefb6a67ac975dce3922 100644
--- a/doc/ci/runners/runner_fleet_dashboard_groups.md
+++ b/doc/ci/runners/runner_fleet_dashboard_groups.md
@@ -24,7 +24,7 @@ The following metrics are available in the runner fleet dashboard:
| Metric | Description |
|-------------------------------|-------------|
-| Online | Number of online runners. In the Admin area, this metric displays the number of runners for the entire instance. In a group, this metric displays the number of runners for the group and its subgroups. |
+| Online | Number of online runners. In the **Admin** area, this metric displays the number of runners for the entire instance. In a group, this metric displays the number of runners for the group and its subgroups. |
| Offline | Number of offline runners. |
| Active runners | Number of active runners. |
| Runner usage (previous month) | Number of compute minutes used by each project on group runners. Includes the option to export as CSV for cost analysis. |
diff --git a/doc/ci/runners/runners_scope.md b/doc/ci/runners/runners_scope.md
index b8ecaaf30009048754ed0a0eb42d2776288d2711..8c397cccbd5ebc0f82a7ff20ac9a3a496eb33ee7 100644
--- a/doc/ci/runners/runners_scope.md
+++ b/doc/ci/runners/runners_scope.md
@@ -81,7 +81,7 @@ should be used instead. For more information, see [Migrating to the new runner r
Prerequisites:
-- Runner registration tokens must be [enabled](../../administration/settings/continuous_integration.md#enable-runner-registrations-tokens) in the Admin area.
+- Runner registration tokens must be [enabled](../../administration/settings/continuous_integration.md#enable-runner-registrations-tokens) in the **Admin** area.
- You must be an administrator.
To create an instance runner:
@@ -689,7 +689,7 @@ you can enable runner registration tokens for projects and groups. This setting
Prerequisites:
-- Runner registration tokens must be [enabled](../../administration/settings/continuous_integration.md#enable-runner-registrations-tokens) in the Admin area.
+- Runner registration tokens must be [enabled](../../administration/settings/continuous_integration.md#enable-runner-registrations-tokens) in the **Admin** area.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Settings > CI/CD**.
diff --git a/doc/ci/variables/index.md b/doc/ci/variables/index.md
index 0fcef7ebb35d4cb90d388aeeabd6f4c7f9de1ecd..abdc445933d757bff525860db74ad73cce7c722d 100644
--- a/doc/ci/variables/index.md
+++ b/doc/ci/variables/index.md
@@ -292,7 +292,7 @@ Prerequisites:
To mask a variable:
-1. For the group, project, or in the Admin area, select **Settings > CI/CD**.
+1. For the group, project, or in the **Admin** area, select **Settings > CI/CD**.
1. Expand **Variables**.
1. Next to the variable you want to protect, select **Edit**.
1. Select the **Mask variable** checkbox.
diff --git a/doc/development/application_limits.md b/doc/development/application_limits.md
index b90076718b89101e25eac39356d79a14ad427f3b..c90b7095616387c78ecd0d1448e2f2fecb4d6102 100644
--- a/doc/development/application_limits.md
+++ b/doc/development/application_limits.md
@@ -170,7 +170,7 @@ The process for adding a new throttle is loosely:
1. Update the JSON schema validator for the [rate_limits column](https://gitlab.com/gitlab-org/gitlab/-/blob/63b37287ae028842fcdcf56d311e6bb0c7e09e79/app/validators/json_schemas/application_setting_rate_limits.json).
1. Extend `Gitlab::RackAttack` and `Gitlab::RackAttack::Request` to configure the new rate limit,
and apply it to the desired requests.
-1. Add the new settings to the Admin area form in `app/views/admin/application_settings/_ip_limits.html.haml`.
+1. Add the new settings to the **Admin** area form in `app/views/admin/application_settings/_ip_limits.html.haml`.
1. Document the new settings in [User and IP rate limits](../administration/settings/user_and_ip_rate_limits.md) and [Application settings API](../api/settings.md).
1. Configure the rate limit for GitLab.com and document it in [GitLab.com-specific rate limits](../user/gitlab_com/index.md#gitlabcom-specific-rate-limits).
diff --git a/doc/development/documentation/styleguide/availability_details.md b/doc/development/documentation/styleguide/availability_details.md
index 748797ed68b252b5d1db5912f7148507ae626db2..0dc958f2d4e10856e140116ff996c6746ca6e8bc 100644
--- a/doc/development/documentation/styleguide/availability_details.md
+++ b/doc/development/documentation/styleguide/availability_details.md
@@ -154,7 +154,7 @@ Instance administrator documentation often includes sections that mention:
- Changing the `gitlab.rb` or `gitlab.yml` files.
- Accessing the rails console or running Rake tasks.
-- Doing things in the Admin area.
+- Doing things in the **Admin** area.
These pages should also mention if the tasks can only be accomplished by an
instance administrator.
diff --git a/doc/development/documentation/styleguide/index.md b/doc/development/documentation/styleguide/index.md
index c71372274da48afe884906016b08e308c8cfa3d5..fd50d0e74276c793b0521c9794d18e259a06a56e 100644
--- a/doc/development/documentation/styleguide/index.md
+++ b/doc/development/documentation/styleguide/index.md
@@ -1038,7 +1038,7 @@ To create a group:
1. On the left sidebar, at the top, select **Create new** (**{plus}**) and **New group**.
```
-To open the Admin area:
+To open the **Admin** area:
```markdown
1. On the left sidebar, at the bottom, select **Admin**.
diff --git a/doc/development/documentation/styleguide/word_list.md b/doc/development/documentation/styleguide/word_list.md
index 3e966d37d07e37c4382fb8effaf00373e55ec2c3..27a54de0ffe7d0b8203984a653fcd330707fd8e8 100644
--- a/doc/development/documentation/styleguide/word_list.md
+++ b/doc/development/documentation/styleguide/word_list.md
@@ -216,7 +216,7 @@ Do not use **and so on**. Instead, be more specific. For more information, see t
## area
-Use [**section**](#section) instead of **area**. The only exception is [the Admin area](#admin-area).
+Use [**section**](#section) instead of **area**. The only exception is [the **Admin** area](#admin-area).
## as
diff --git a/doc/development/geo.md b/doc/development/geo.md
index bafb11f7d7192cb2e60bd65c6e5e0ffbbbff2ec0..dc935fb63b0211a752bbb28808de2e3f330240ee 100644
--- a/doc/development/geo.md
+++ b/doc/development/geo.md
@@ -110,7 +110,7 @@ projects that need updating. Those projects can be:
timestamp that is more recent than the `last_repository_successful_sync_at`
timestamp in the `Geo::ProjectRegistry` model.
- Manual: The administrator can manually flag a repository to resync in the
- [Geo Admin area](../administration/geo_sites.md).
+ [Geo **Admin** area](../administration/geo_sites.md).
When we fail to fetch a repository on the secondary `RETRIES_BEFORE_REDOWNLOAD`
times, Geo does a so-called _re-download_. It will do a clean clone
@@ -465,7 +465,7 @@ basically hashes all Git refs together and stores that hash in the
The **secondary** site does the same to calculate the hash of its
clone, and compares the hash with the value the **primary** site
calculated. If there is a mismatch, Geo will mark this as a mismatch
-and the administrator can see this in the [Geo Admin area](../administration/geo_sites.md).
+and the administrator can see this in the [Geo **Admin** area](../administration/geo_sites.md).
## Geo proxying
diff --git a/doc/development/internal_analytics/metrics/metrics_dictionary.md b/doc/development/internal_analytics/metrics/metrics_dictionary.md
index 71eb8bc6ffc39813f7ae33408b3f160e6a0217e8..11495c7a5230716f28ad4b1d42cf461b4c8fbdbe 100644
--- a/doc/development/internal_analytics/metrics/metrics_dictionary.md
+++ b/doc/development/internal_analytics/metrics/metrics_dictionary.md
@@ -102,7 +102,7 @@ A metric's time frame is calculated based on the `time_frame` field and the `dat
We use the following categories to classify a metric:
- `operational`: Required data for operational purposes.
-- `optional`: Default value for a metric. Data that is optional to collect. This can be [enabled or disabled](../../../administration/settings/usage_statistics.md#enable-or-disable-service-ping) in the Admin area.
+- `optional`: Default value for a metric. Data that is optional to collect. This can be [enabled or disabled](../../../administration/settings/usage_statistics.md#enable-or-disable-service-ping) in the **Admin** area.
- `subscription`: Data related to licensing.
- `standard`: Standard set of identifiers that are included when collecting data.
diff --git a/doc/development/internal_analytics/service_ping/troubleshooting.md b/doc/development/internal_analytics/service_ping/troubleshooting.md
index 05a847c9c802b51e9fdc933038c9ce946601e717..a5a20a598bfa44c723eb728e8bd7b25b9fab63d3 100644
--- a/doc/development/internal_analytics/service_ping/troubleshooting.md
+++ b/doc/development/internal_analytics/service_ping/troubleshooting.md
@@ -104,7 +104,7 @@ Gitlab::Usage::ServicePingReport.for(output: :all_metrics_values, cached: true)
Use the following method in the [rails console](../../../administration/operations/rails_console.md#starting-a-rails-console-session).
-This also refreshes the cached Service Ping displayed in the Admin area.
+This also refreshes the cached Service Ping displayed in the **Admin** area.
```ruby
Gitlab::Usage::ServicePingReport.for(output: :all_metrics_values)
diff --git a/doc/development/internal_api/index.md b/doc/development/internal_api/index.md
index ef05efd12ccf17183341b1a361ed7b9e6a8f7060..44374404e71b0f5f6c66b7bebf86e1deb5e7b14f 100644
--- a/doc/development/internal_api/index.md
+++ b/doc/development/internal_api/index.md
@@ -1112,7 +1112,7 @@ Example response:
## Storage limit exclusions
The namespace storage limit exclusion endpoints manage storage limit exclusions on top-level namespaces on GitLab.com.
-These endpoints can only be consumed in the Admin area of GitLab.com.
+These endpoints can only be consumed in the **Admin** area of GitLab.com.
### Retrieve storage limit exclusions
@@ -1208,7 +1208,7 @@ Example response:
### Known consumers
-- GitLab.com Admin area
+- GitLab.com **Admin** area
## Compute quota provisioning
@@ -1603,7 +1603,7 @@ Example response:
Returns a `201` status code if successful.
NOTE:
-After you create a group SCIM identity for a user, you can see that SCIM identity in the Admin area.
+After you create a group SCIM identity for a user, you can see that SCIM identity in the **Admin** area.
### Update a single SCIM provisioned user
diff --git a/doc/development/permissions/predefined_roles.md b/doc/development/permissions/predefined_roles.md
index 2ca2e23041fb7d44e7cef9ac17b2dc98b2d55d07..b96ed64057fd570bbb14a12f4bb531b161866e56 100644
--- a/doc/development/permissions/predefined_roles.md
+++ b/doc/development/permissions/predefined_roles.md
@@ -17,7 +17,7 @@ Each user can be one of the following types:
- [Internal users](../internal_users.md) - system created.
- [Auditor](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/policies/ee/base_policy.rb#L9):
- No access to projects or groups settings menu.
- - No access to Admin area.
+ - No access to **Admin** area.
- Read-only access to everything else.
- [Administrator](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/policies/base_policy.rb#L6) - read-write access.
diff --git a/doc/development/spam_protection_and_captcha/exploratory_testing.md b/doc/development/spam_protection_and_captcha/exploratory_testing.md
index 3711f3f3641a45af0bc6445cc6eca50a89b60874..63315d762397b4856ea9026ae731c0487af30d0a 100644
--- a/doc/development/spam_protection_and_captcha/exploratory_testing.md
+++ b/doc/development/spam_protection_and_captcha/exploratory_testing.md
@@ -273,7 +273,7 @@ GraphQL response:
### Scenario: Akismet enabled, CAPTCHA disabled
-For this scenario, ensure you clear **Enable reCAPTCHA** in the Admin area settings as described above.
+For this scenario, ensure you clear **Enable reCAPTCHA** in the **Admin** area settings as described above.
If CAPTCHA is not enabled, any request flagged as potential spam fails with no chance to resubmit,
even if it could otherwise be resubmitted if CAPTCHA were enabled and successfully solved.
diff --git a/doc/development/spam_protection_and_captcha/model_and_services.md b/doc/development/spam_protection_and_captcha/model_and_services.md
index acebad56d805c08338f0d0011791d4c7493dcd56..e8944a8dc3963a0df58b2b71891074b290e6f224 100644
--- a/doc/development/spam_protection_and_captcha/model_and_services.md
+++ b/doc/development/spam_protection_and_captcha/model_and_services.md
@@ -57,7 +57,7 @@ To do this:
The `SpammableActions::AkismetMarkAsSpamAction` module adds support for a `#mark_as_spam` action
to a controller. This controller allows administrators to manage spam for the associated
-`Spammable` model in the [**Spam log** section](../../integration/akismet.md) of the Admin area page.
+`Spammable` model in the [**Spam log** section](../../integration/akismet.md) of the **Admin** area.
1. Include the `SpammableActions::AkismetMarkAsSpamAction` module in the controller.
diff --git a/doc/development/testing_guide/end_to_end/rspec_metadata_tests.md b/doc/development/testing_guide/end_to_end/rspec_metadata_tests.md
index e17103eaf460c4dc76cbe87974125c755e3a6eb4..7007d09f4ec607ab19f220dcaedcf3cad2f80e94 100644
--- a/doc/development/testing_guide/end_to_end/rspec_metadata_tests.md
+++ b/doc/development/testing_guide/end_to_end/rspec_metadata_tests.md
@@ -25,7 +25,7 @@ This is a partial list of the [RSpec metadata](https://rspec.info/features/3-12/
| `:instance_saml` | The test requires a GitLab instance that has SAML SSO enabled for the instance. Interacts with an external SAML identity provider. Paired with the `:orchestrated` tag. |
| `:integrations` | This aims to test the available [integrations](../../../user/project/integrations/index.md#available-integrations). The test requires Docker to be installed in the run context. It will provision the containers and can be run against a local instance or using the `gitlab-qa` scenario `Test::Integration::Integrations`. |
| `:issue`, `:issue_${num}` | Optional links to issues which might be related to the spec. Helps keep track of related issues and can also be used by tools that create test reports. Currently added automatically to `Allure` test report. Multiple tags can be used by adding an optional numeric suffix like `issue_1`, `issue_2` etc. |
-| `:service_ping_disabled` | The test interacts with the GitLab configuration service ping at the instance level to turn Admin area setting service ping checkbox on or off. This tag will have the test run only in the `service_ping_disabled` job and must be paired with the `:orchestrated` and `:requires_admin` tags. |
+| `:service_ping_disabled` | The test interacts with the GitLab configuration service ping at the instance level to turn **Admin** area setting service ping checkbox on or off. This tag will have the test run only in the `service_ping_disabled` job and must be paired with the `:orchestrated` and `:requires_admin` tags. |
| `:jira` | The test requires a Jira Server. [GitLab-QA](https://gitlab.com/gitlab-org/gitlab-qa) provisions the Jira Server in a Docker container when the `Test::Integration::Jira` test scenario is run. |
| `:kubernetes` | The test includes a GitLab instance that is configured to be run behind an SSH tunnel, allowing a TLS-accessible GitLab. This test also includes provisioning of at least one Kubernetes cluster to test against. _This tag is often be paired with `:orchestrated`._ |
| `:ldap_no_server` | The test requires a GitLab instance to be configured to use LDAP. To be used with the `:orchestrated` tag. It does not spin up an LDAP server at orchestration time. Instead, it creates the LDAP server at runtime. |
diff --git a/doc/install/azure/index.md b/doc/install/azure/index.md
index a8eaae31ddbaa9c4747557c12cf0d3913feed9a4..7eea9ec999312715e94b4dc46e0d5b4825b5b2e7 100644
--- a/doc/install/azure/index.md
+++ b/doc/install/azure/index.md
@@ -291,7 +291,7 @@ To update GitLab to the latest version:
before anything else.
```
-Refresh your GitLab instance in the browser and go to the Admin area. You should now have an
+Refresh your GitLab instance in the browser and go to the **Admin** area. You should now have an
up-to-date GitLab instance.
## Next steps and further configuration
diff --git a/doc/install/docker_troubleshooting.md b/doc/install/docker_troubleshooting.md
index b07a05d4d159f003dfc4ee69155f684dd032fdbd..978e3df9721d9184638b57994d6b011bb415293e 100644
--- a/doc/install/docker_troubleshooting.md
+++ b/doc/install/docker_troubleshooting.md
@@ -125,7 +125,7 @@ writing value to /dev/shm/gitlab/sidekiq/histogram_sidekiq_0-0.db failed with un
writing value to /dev/shm/gitlab/sidekiq/histogram_sidekiq_0-0.db failed with unmapped file
```
-Other than disabling the Prometheus Metrics from the Admin area, the recommended
+Other than disabling the Prometheus Metrics from the **Admin** area, the recommended
solution to fix this problem is to [install](docker.md#pre-configure-docker-container) with shared memory set to at least 256 MB.
If using `docker run`, this can be done by passing the flag `--shm-size 256m`.
If using a `docker-compose.yml` file, the `shm_size` key can be used for this
diff --git a/doc/integration/advanced_search/elasticsearch.md b/doc/integration/advanced_search/elasticsearch.md
index f8b14b9dd4eb02868b87e7d87159165503154bd3..1289986b8a3da5a9f1e82a8f3ce7b04fbb1e63a2 100644
--- a/doc/integration/advanced_search/elasticsearch.md
+++ b/doc/integration/advanced_search/elasticsearch.md
@@ -64,7 +64,7 @@ For a single node search cluster, the functional cluster health status is always
The search index updates after you:
- Add data to the database or repository.
-- [Enable advanced search](#enable-advanced-search) in the Admin area.
+- [Enable advanced search](#enable-advanced-search) in the **Admin** area.
NOTE:
Before you use a new Elasticsearch cluster in production, see the
@@ -978,7 +978,7 @@ due to large volumes of data being indexed, follow these steps:
```
This enqueues a Sidekiq job for each project that needs to be indexed.
- You can view the jobs in the Admin area under **Monitoring > Background jobs > Queues Tab**
+ You can view the jobs in the **Admin** area under **Monitoring > Background jobs > Queues Tab**
and select `elastic_commit_indexer`, or you can query indexing status using a Rake task:
```shell
diff --git a/doc/integration/advanced_search/elasticsearch_troubleshooting.md b/doc/integration/advanced_search/elasticsearch_troubleshooting.md
index b3e276d77300fa910a49962293b555f15920c23d..8bad01bfbd9ed8039493a5fc22a5514473e7ba07 100644
--- a/doc/integration/advanced_search/elasticsearch_troubleshooting.md
+++ b/doc/integration/advanced_search/elasticsearch_troubleshooting.md
@@ -108,7 +108,7 @@ There are a couple of ways to achieve that:
This is always correctly identifying whether the current project/namespace
being searched is using Elasticsearch.
-- From the Admin area under **Settings > Search** check that the
+- From the **Admin** area under **Settings > Search** check that the
advanced search settings are checked.
Those same settings there can be obtained from the Rails console if necessary:
diff --git a/doc/integration/akismet.md b/doc/integration/akismet.md
index 2eb33d48bcac1bc38ed97706bb8d7ca9ac63323a..4a9ce85d840f5be8d5c4b130949717a1aedf0f3f 100644
--- a/doc/integration/akismet.md
+++ b/doc/integration/akismet.md
@@ -16,7 +16,7 @@ Akismet for review, and instance administrators can
[mark snippets as spam](../user/snippets.md#mark-snippet-as-spam).
Detected spam is rejected, and an entry is added in the **Spam log** section of the
-Admin area.
+**Admin** area.
Privacy note: GitLab submits the user's IP and user agent to Akismet.
diff --git a/doc/integration/bitbucket.md b/doc/integration/bitbucket.md
index 1046a774f993f0b4484e30ecefc62324700df8d5..720ff23d460dd82af86d85373a1ba75134eee6ee 100644
--- a/doc/integration/bitbucket.md
+++ b/doc/integration/bitbucket.md
@@ -129,4 +129,4 @@ After the above configuration is set up, you can use Bitbucket to sign in to
GitLab and [start importing your projects](../user/project/import/bitbucket.md).
If you want to import projects from Bitbucket, but don't want to enable signing in,
-you can [disable Sign-Ins in the Admin area](omniauth.md#enable-or-disable-sign-in-with-an-omniauth-provider-without-disabling-import-sources).
+you can [disable Sign-Ins in the **Admin** area](omniauth.md#enable-or-disable-sign-in-with-an-omniauth-provider-without-disabling-import-sources).
diff --git a/doc/integration/sourcegraph.md b/doc/integration/sourcegraph.md
index e14648407e746cf0412a74edf6f33dd879fbf010..9b5cd4dc7a93c05a7fbafd88eebf4e024663cea5 100644
--- a/doc/integration/sourcegraph.md
+++ b/doc/integration/sourcegraph.md
@@ -51,8 +51,8 @@ Prerequisites:
In Sourcegraph:
-1. Go to the site Admin area.
-1. Optional. [Configure your GitLab external service](https://docs.sourcegraph.com/admin/external_service/gitlab).
+1. Go to the **Site admin** area.
+1. Optional. [Configure your GitLab external service](https://sourcegraph.com/docs/admin/code_hosts/gitlab).
If your GitLab repositories are already searchable in Sourcegraph, you can skip this step.
1. Confirm that you can search your repositories from GitLab in your Sourcegraph instance by running a test query.
1. Add your GitLab instance URL to the [`corsOrigin` setting](https://docs.sourcegraph.com/admin/config/site_config#corsOrigin)
diff --git a/doc/raketasks/user_management.md b/doc/raketasks/user_management.md
index 838c80989946f01c227c92ab3af8e3d900c34444..fc10bf2441a72472b0c98e1bbd188714130887ae 100644
--- a/doc/raketasks/user_management.md
+++ b/doc/raketasks/user_management.md
@@ -10,7 +10,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed
-GitLab provides Rake tasks for managing users. Administrators can also use the Admin area to
+GitLab provides Rake tasks for managing users. Administrators can also use the **Admin** area to
[manage users](../administration/admin_area.md#administering-users).
## Add user as a developer to all projects
diff --git a/doc/security/hardening_nist_800_53.md b/doc/security/hardening_nist_800_53.md
index 10bf64d59804ef498598c7b9a1355d53d999a856..143ed152ee6e11400e39b180cfb06b80b5f9ce4d 100644
--- a/doc/security/hardening_nist_800_53.md
+++ b/doc/security/hardening_nist_800_53.md
@@ -124,7 +124,7 @@ for customers that have unique permission requirements.
GitLab also supports the following user types for unique use cases:
-- [Auditor Users](../administration/auditor_users.md) - The auditor role provides read-only access to all groups, projects and other resources except for the Admin area and project/group settings. You can use the auditor role when engaging with third-party auditors that require access to certain projects to validate processes.
+- [Auditor Users](../administration/auditor_users.md) - The auditor role provides read-only access to all groups, projects and other resources except for the **Admin** area and project/group settings. You can use the auditor role when engaging with third-party auditors that require access to certain projects to validate processes.
- [External Users](../administration/external_users.md) -
External users can be set to provide limited access for users that
@@ -140,7 +140,7 @@ GitLab also supports the following user types for unique use cases:
Service accounts may be added to accommodate automated tasks.
Service accounts do not use a seat under the license.
-**Admin area** - In the Admin area, administrators can [export permissions](../administration/admin_area.md#user-permission-export),
+**Admin** area - In the **Admin** area, administrators can [export permissions](../administration/admin_area.md#user-permission-export),
[review user identities](../administration/admin_area.md#user-identities), [administer groups](../administration/admin_area.md#administering-groups),
and much more. Functions that can be used to meet FedRAMP / NIST 800-53
requirements:
@@ -161,7 +161,7 @@ requirements:
FedRAMP requires organizations to monitor accounts for atypical use
(AC-2(12)). GitLab empowers users to flag abuse in abuse reports,
where administrators can remove access pending investigation. Spam
- logs are consolidated in the **Spam logs** section of the Admin area.
+ logs are consolidated in the **Spam logs** section of the **Admin** area.
Administrators can remove, block, or trust users flagged in that
area.
@@ -183,7 +183,7 @@ requirements:
with the GitLab UI, which organizations interested
in enforcing longer passwords can use. Additionally, self-managed customers
may [configure complexity requirements](../administration/settings/sign_up_restrictions.md#password-complexity-requirements)
- through the Admin area UI.
+ through the **Admin** area UI.
- [Default session durations](../administration/settings/account_and_limit_settings.md#customize-the-default-session-duration) -
FedRAMP establishes that users that have been inactive for a set
@@ -194,10 +194,10 @@ requirements:
- [Provisioning New Users](../user/profile/account/create_accounts.md) -
Administrators can create new users for their GitLab account with the
- Admin area UI. In compliance with IA-5, GitLab requires new users to
+ **Admin** area UI. In compliance with IA-5, GitLab requires new users to
change their passwords on first login.
-- Deprovisioning Users - Administrators are able to [remove users with the Admin area UI](../user/profile/account/delete_account.md#delete-users-and-user-contributions).
+- Deprovisioning Users - Administrators are able to [remove users with the **Admin** area UI](../user/profile/account/delete_account.md#delete-users-and-user-contributions).
An alternative to deleting users is to [block a user](../administration/moderate_users.md#block-a-user)
and remove all access. Blocking a user maintains their data in
repositories while removing all access. Blocked users do not impact
diff --git a/doc/security/rate_limits.md b/doc/security/rate_limits.md
index 77d307fe3590f14986c7f3ec2640efad1b435015..01f28ce93ce087ce3d2ed45f862c18130bb2c23b 100644
--- a/doc/security/rate_limits.md
+++ b/doc/security/rate_limits.md
@@ -35,7 +35,7 @@ The rate limits for API requests do not affect requests made by the frontend, be
## Configurable limits
-You can set these rate limits in the Admin area of your instance:
+You can set these rate limits in the **Admin** area of your instance:
- [Import/Export rate limits](../administration/settings/import_export_rate_limits.md)
- [Issue rate limits](../administration/settings/rate_limit_on_issues_creation.md)
diff --git a/doc/security/ssh_keys_restrictions.md b/doc/security/ssh_keys_restrictions.md
index d339b6f075acab649aa3efc3bb373f42a1eade2f..5ad1d4dcb22dfebe788d4f1c2b99364528a7f5cf 100644
--- a/doc/security/ssh_keys_restrictions.md
+++ b/doc/security/ssh_keys_restrictions.md
@@ -27,7 +27,7 @@ the minimum key length for each technology:
1. Select **Settings > General** .
1. Expand **Visibility and access controls**:
- 
+ 
If a restriction is imposed on any key type, users cannot upload new SSH keys that don't meet the
requirement. Any existing keys that don't meet it are disabled but not removed and users cannot
diff --git a/doc/security/unlock_user.md b/doc/security/unlock_user.md
index 9f8c58be808f1514bfa215d3d99f734e4e7d1422..c90b75dca38763c7140f0f94e3d7f4c91223ff62 100644
--- a/doc/security/unlock_user.md
+++ b/doc/security/unlock_user.md
@@ -17,7 +17,7 @@ DETAILS:
By default, users are locked after 10 failed sign-in attempts. These users remain locked:
- For 10 minutes, after which time they are automatically unlocked.
-- Until an administrator unlocks them from the [Admin area](../administration/admin_area.md) or the command line in under 10 minutes.
+- Until an administrator unlocks them from the [**Admin** area](../administration/admin_area.md) or the command line in under 10 minutes.
In GitLab 16.5 and later, administrators can [use the API](../api/settings.md#list-of-settings-that-can-be-accessed-via-api-calls) to configure:
diff --git a/doc/subscriptions/self_managed/index.md b/doc/subscriptions/self_managed/index.md
index 579c4f4c8b8bb78ccbb81a009b3a920cd83e3e4c..aadbd00499480a3e05244ef99d697fc2f4e5e34a 100644
--- a/doc/subscriptions/self_managed/index.md
+++ b/doc/subscriptions/self_managed/index.md
@@ -63,7 +63,7 @@ A user is not counted as a billable user if:
- [Bot users for groups](../../user/group/settings/group_access_tokens.md#bot-users-for-groups).
- Other [internal users](../../development/internal_users.md#internal-users).
-The amount of **Billable users** is reported once a day in the Admin area.
+The amount of **Billable users** is reported once a day in the **Admin** area.
### Maximum users
@@ -466,7 +466,7 @@ For example, if a license has a start date of January 1, 2024 and an end date of
## Activate a license file or key
-If you have a license file or key, you can activate it [in the Admin area](../../administration/license_file.md#activate-gitlab-ee-with-a-license-file-or-key).
+If you have a license file or key, you can activate it [in the **Admin** area](../../administration/license_file.md#activate-gitlab-ee-with-a-license-file-or-key).
## Contact Support
diff --git a/doc/topics/autodevops/index.md b/doc/topics/autodevops/index.md
index 11cb265adc53996fe5f6ea241253853a68b0bc26..e16d2bcffe87fdd715a0b290e06a5afdd182d310 100644
--- a/doc/topics/autodevops/index.md
+++ b/doc/topics/autodevops/index.md
@@ -77,7 +77,7 @@ Auto DevOps runs pipelines automatically only if a [`Dockerfile` or matching bui
Depending on your instance type, you can enable or disable Auto DevOps at the
following levels:
-| Instance type | [Project](#per-project) | [Group](#per-group) | [Instance](#per-instance) (Admin area) |
+| Instance type | [Project](#per-project) | [Group](#per-group) | [Instance](#per-instance) (**Admin** area) |
|---------------------|------------------------|------------------------|------------------------|
| GitLab SaaS | **{check-circle}** Yes | **{check-circle}** Yes | **{dotted-circle}** No |
| GitLab self-managed | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
diff --git a/doc/topics/autodevops/prepare_deployment.md b/doc/topics/autodevops/prepare_deployment.md
index 44ad68821edbf95e562a16c76aa1d2c756a3a43d..459f8d5d6949307f8ba8a7914f67f1f3156649b7 100644
--- a/doc/topics/autodevops/prepare_deployment.md
+++ b/doc/topics/autodevops/prepare_deployment.md
@@ -45,7 +45,7 @@ To define the base domain, either:
- In the project, group, or instance: go to your cluster settings and add it there.
- In the project or group: add it as an environment variable: `KUBE_INGRESS_BASE_DOMAIN`.
-- In the instance: go to the Admin area, then **Settings > CI/CD > Continuous Integration and Delivery** and add it there.
+- In the instance: go to the **Admin** area, then **Settings > CI/CD > Continuous Integration and Delivery** and add it there.
The base domain variable `KUBE_INGRESS_BASE_DOMAIN` follows the same order of precedence
as other environment [variables](../../ci/variables/index.md#cicd-variable-precedence).
diff --git a/doc/topics/autodevops/requirements.md b/doc/topics/autodevops/requirements.md
index be2a593c2273e2d11483c0ec312e9c6ddf3d1b90..98234926460d9acd1a6b640e9893a6a179231588 100644
--- a/doc/topics/autodevops/requirements.md
+++ b/doc/topics/autodevops/requirements.md
@@ -62,7 +62,7 @@ To define the base domain, either:
- In the project, group, or instance level: go to your cluster settings and add it there.
- In the project or group level: add it as an environment variable: `KUBE_INGRESS_BASE_DOMAIN`.
-- In the instance level: go to the Admin area, then **Settings > CI/CD > Continuous Integration and Delivery** and add it there.
+- In the instance level: go to the **Admin** area, then **Settings > CI/CD > Continuous Integration and Delivery** and add it there.
The base domain variable `KUBE_INGRESS_BASE_DOMAIN` follows the same order of
[precedence as other environment variables](../../ci/variables/index.md#cicd-variable-precedence).
diff --git a/doc/tutorials/install_gitlab_single_node/index.md b/doc/tutorials/install_gitlab_single_node/index.md
index fc8231255538358a196faf192ce337be92b5e65e..dfb64fdf4aabaf7c362130dfef9152edb6d5f7f9 100644
--- a/doc/tutorials/install_gitlab_single_node/index.md
+++ b/doc/tutorials/install_gitlab_single_node/index.md
@@ -273,7 +273,7 @@ Now it's time to configure GitLab!
GitLab comes with some sane default configuration options. In this section,
we will change them to add more functionality, and make GitLab more secure.
-For some of the options you'll use the Admin area UI, and for some of them you'll
+For some of the options you'll use the **Admin** area UI, and for some of them you'll
edit `/etc/gitlab/gitlab.rb`, the GitLab configuration file.
### Configure NGINX
diff --git a/doc/tutorials/left_sidebar/index.md b/doc/tutorials/left_sidebar/index.md
index 20332eff909fd3bc69fda59c6b6913998b36f1dc..b9fd6a13d38dcfde8db6a047c5534e6650e07990 100644
--- a/doc/tutorials/left_sidebar/index.md
+++ b/doc/tutorials/left_sidebar/index.md
@@ -78,6 +78,6 @@ Then, on the left sidebar, **Your work** is displayed.
## Go to the Admin area
-The Admin area is also available on the left sidebar at the bottom:
+The **Admin** area is also available on the left sidebar at the bottom:
-
+
diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md
index 51170250d54230ff276aef9bd339a447d9886ac6..d9db452ec9117fabdd40667a1d2ffbefd333b86b 100644
--- a/doc/update/deprecations.md
+++ b/doc/update/deprecations.md
@@ -3539,7 +3539,7 @@ and `config/redis.shared_state.yml` files.
- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/389557).
</div>
-The group and project deletion protection setting in the Admin area had an option to delete groups and projects immediately. Starting with 16.0, this option will no longer be available, and delayed group and project deletion will become the default behavior.
+The group and project deletion protection setting in the **Admin** area had an option to delete groups and projects immediately. Starting with 16.0, this option will no longer be available, and delayed group and project deletion will become the default behavior.
The option will no longer appear as a group setting. Self-managed users will still have the option to define the deletion delay period, and SaaS users have a non-adjustable default retention period of 7 days. Users can still immediately delete the project from the project settings, and the group from the group settings.
diff --git a/doc/update/versions/gitlab_16_changes.md b/doc/update/versions/gitlab_16_changes.md
index 23630da172f7a1195a8e50cdb09cffe88cb37483..8872e79e6ac925c68963542d620044494c7ea14b 100644
--- a/doc/update/versions/gitlab_16_changes.md
+++ b/doc/update/versions/gitlab_16_changes.md
@@ -426,7 +426,7 @@ Specific information applies to Linux package installations:
Workarounds:
- - Pause the running migration in the [Admin area](../background_migrations.md#from-the-gitlab-ui).
+ - Pause the running migration in the [**Admin** area](../background_migrations.md#from-the-gitlab-ui).
- Recreate table statistics manually on the
[database console](../../administration/troubleshooting/postgresql.md#start-a-database-console)
to ensure the right query plan is selected:
diff --git a/doc/user/application_security/continuous_vulnerability_scanning/index.md b/doc/user/application_security/continuous_vulnerability_scanning/index.md
index 5d954418d764e4116b006e07cd54554206a67d43..98aac50325b28ce0f75de7b550581de7c61d264c 100644
--- a/doc/user/application_security/continuous_vulnerability_scanning/index.md
+++ b/doc/user/application_security/continuous_vulnerability_scanning/index.md
@@ -91,7 +91,7 @@ Continuous Vulnerability Scanning uses the Package Metadata Database, a service
On GitLab.com, the synchronization is managed by GitLab and is available to all projects.
-On GitLab self-managed, you can [choose package registry metadata to synchronize](../../../administration/settings/security_and_compliance.md#choose-package-registry-metadata-to-sync) in the Admin area for the GitLab instance.
+On GitLab self-managed, you can [choose package registry metadata to synchronize](../../../administration/settings/security_and_compliance.md#choose-package-registry-metadata-to-sync) in the **Admin** area for the GitLab instance.
### Data sources
diff --git a/doc/user/compliance/audit_events.md b/doc/user/compliance/audit_events.md
index dcf4e336e5538ae1bd806d701f30ff8b4ca3884b..f348446bf94181e317360ad53cf5e8caf0921c63 100644
--- a/doc/user/compliance/audit_events.md
+++ b/doc/user/compliance/audit_events.md
@@ -105,4 +105,4 @@ If you don't see the event you want in any of the epics, you can either:
## Administer topics
-Instance administrators can [administer audit events](../../administration/audit_event_reports.md) from the Admin area.
+Instance administrators can [administer audit events](../../administration/audit_event_reports.md) from the **Admin** area.
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 583b42e74508503c4e693ec79b9c04a89b4cbf81..cf16e7eac061d5a15ca1268437cea06f0923ebd2 100644
--- a/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md
+++ b/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md
@@ -34,7 +34,7 @@ To enable License scanning of CycloneDX files:
- Using the Dependency Scanning template
- Enable [Dependency Scanning](../../application_security/dependency_scanning/index.md#enabling-the-analyzer)
and ensure that its prerequisites are met.
- - On GitLab self-managed only, you can [choose package registry metadata to synchronize](../../../administration/settings/security_and_compliance.md#choose-package-registry-metadata-to-sync) in the Admin area for the GitLab instance. For this data synchronization to work, you must allow outbound network traffic from your GitLab instance to the domain `storage.googleapis.com`. If you have limited or no network connectivity then refer to the documentation section [running in an offline environment](#running-in-an-offline-environment) for further guidance.
+ - On GitLab self-managed only, you can [choose package registry metadata to synchronize](../../../administration/settings/security_and_compliance.md#choose-package-registry-metadata-to-sync) in the **Admin** area for the GitLab instance. For this data synchronization to work, you must allow outbound network traffic from your GitLab instance to the domain `storage.googleapis.com`. If you have limited or no network connectivity then refer to the documentation section [running in an offline environment](#running-in-an-offline-environment) for further guidance.
- Or use the [CI/CD component](../../../ci/components/index.md) for applicable package registries.
## Supported languages and package managers
diff --git a/doc/user/group/saml_sso/scim_setup.md b/doc/user/group/saml_sso/scim_setup.md
index 1d8c54cf024a616eb442c2d8e592bec62c7a31fa..c75284f0d9f506b265fc4a204e39bc237af356c6 100644
--- a/doc/user/group/saml_sso/scim_setup.md
+++ b/doc/user/group/saml_sso/scim_setup.md
@@ -195,7 +195,7 @@ Prerequisites:
To configure Okta for SCIM:
1. Sign in to Okta.
-1. In the upper-right corner, select **Admin**. The button is not visible from the Admin area.
+1. In the upper-right corner, select **Admin**. The button is not visible from the **Admin** area.
1. In the **Application** tab, select **Browse App Catalog**.
1. Search for **GitLab**, find and select the **GitLab** application.
1. On the GitLab application overview page, select **Add**.
diff --git a/doc/user/group/saml_sso/troubleshooting_scim.md b/doc/user/group/saml_sso/troubleshooting_scim.md
index 1111dc1b6d44faa28b14f76833979507b8d55bba..c47c17b52f640fd1b1b4a6deddef93aa36b882bf 100644
--- a/doc/user/group/saml_sso/troubleshooting_scim.md
+++ b/doc/user/group/saml_sso/troubleshooting_scim.md
@@ -53,7 +53,7 @@ The following are possible solutions for problems where users cannot sign in:
To check if a user's SAML `NameId` matches their SCIM `externalId`:
-- Administrators can use the Admin area to [list SCIM identities for a user](../../../administration/admin_area.md#user-identities).
+- Administrators can use the **Admin** area to [list SCIM identities for a user](../../../administration/admin_area.md#user-identities).
- Group owners can see the list of users and the identifier stored for each user in the group SAML SSO Settings page.
- You can use the [SCIM API](../../../api/scim.md) to manually retrieve the `extern_uid` GitLab has stored for users and compare the value for each user from the [SAML API](../../../api/saml.md) .
- Have the user use a [SAML Tracer](troubleshooting.md#saml-debugging-tools) and compare the `extern_uid` to
diff --git a/doc/user/packages/container_registry/reduce_container_registry_storage.md b/doc/user/packages/container_registry/reduce_container_registry_storage.md
index 25399c86aeea0f70de90c67454ce5dba4e02aaac..f246c00c6d211526a54364e0ccaaef5c3bc37f49 100644
--- a/doc/user/packages/container_registry/reduce_container_registry_storage.md
+++ b/doc/user/packages/container_registry/reduce_container_registry_storage.md
@@ -271,7 +271,7 @@ For self-managed instances, those settings can be updated in the [Rails console]
ApplicationSetting.last.update(container_registry_expiration_policies_worker_capacity: 3)
```
-They are also available in the [Admin area](../../../administration/admin_area.md):
+They are also available in the [**Admin** area](../../../administration/admin_area.md):
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**
diff --git a/doc/user/packages/package_registry/supported_functionality.md b/doc/user/packages/package_registry/supported_functionality.md
index 7197801e70b12df3acaae29d881e3a8154b3ceb7..0c90492d35b69ffad8dc104e8c85ea17a80bb0d2 100644
--- a/doc/user/packages/package_registry/supported_functionality.md
+++ b/doc/user/packages/package_registry/supported_functionality.md
@@ -98,7 +98,7 @@ To reduce the associated security risks, before deleting a package you can:
- Verify the package is not being actively used.
- Disable request forwarding:
- - Instance administrators can disable forwarding in the [**Continuous Integration** section](../../../administration/settings/continuous_integration.md#package-registry-configuration) of the Admin area.
+ - Instance administrators can disable forwarding in the [**Continuous Integration** section](../../../administration/settings/continuous_integration.md#package-registry-configuration) of the **Admin** area.
- Group owners can disable forwarding in the **Packages and Registries** section of the group settings.
## Importing packages from other repositories
diff --git a/doc/user/profile/account/create_accounts.md b/doc/user/profile/account/create_accounts.md
index 7c2322f32680ff2863f51e86b35c06b02a6525b8..7d50e7922de0bde20c87886a1b76753838789159 100644
--- a/doc/user/profile/account/create_accounts.md
+++ b/doc/user/profile/account/create_accounts.md
@@ -14,7 +14,7 @@ DETAILS:
You can create users:
- [Manually through the sign-in page](#create-users-on-sign-in-page).
-- [Manually in the Admin area](#create-users-in-admin-area).
+- [Manually in the **Admin** area](#create-users-in-admin-area).
- [Manually using the API](../../../api/users.md).
- [Automatically through user authentication integrations](#create-users-through-authentication-integrations).
diff --git a/doc/user/profile/account/delete_account.md b/doc/user/profile/account/delete_account.md
index 9d9a7c4d3de00ac8351511e0a119e08ccb3e791b..3ab1d5d9695ed8d44742705c9e3a1079a36bdf41 100644
--- a/doc/user/profile/account/delete_account.md
+++ b/doc/user/profile/account/delete_account.md
@@ -88,7 +88,7 @@ When a user is deleted from an [abuse report](../../../administration/review_abu
records are always removed.
The deleting associated records option can be requested in the [API](../../../api/users.md#user-deletion) as well as
-the Admin area.
+the **Admin** area.
WARNING:
User approvals are associated with a user ID. Other user contributions do not have an associated user ID. When you delete a user and their contributions are moved to a "Ghost User", the approval contributions refer to a missing or invalid user ID. Instead of deleting users, consider [blocking](../../../administration/moderate_users.md#block-a-user), [banning](../../../administration/moderate_users.md#ban-a-user), or [deactivating](../../../administration/moderate_users.md#deactivate-a-user) them.
@@ -99,7 +99,7 @@ DETAILS:
**Offering:** Self-managed
WARNING:
-The root account is the most privileged account on the system. Deleting the root account might result in losing access to the instance [Admin area](../../../administration/admin_area.md) if there is no other administrator available on the instance.
+The root account is the most privileged account on the system. Deleting the root account might result in losing access to the instance [**Admin** area](../../../administration/admin_area.md) if there is no other administrator available on the instance.
You can delete the root account using either the UI or the [GitLab Rails console](../../../administration/operations/rails_console.md).
@@ -117,7 +117,7 @@ Prerequisites:
To delete the root account:
-1. In the Admin area, [create a new user with administrator access](../../profile/account/create_accounts.md#create-users-in-admin-area). This ensures that you maintain administrator access to the instance whilst mitigating the risks associated with deleting the root account.
+1. In the **Admin** area, [create a new user with administrator access](../../profile/account/create_accounts.md#create-users-in-admin-area). This ensures that you maintain administrator access to the instance whilst mitigating the risks associated with deleting the root account.
1. [Delete the root account](#delete-users-and-user-contributions).
### Use the GitLab Rails console
@@ -179,7 +179,7 @@ ERROR: null value in column "user_id" violates not-null constraint
```
The error can be found in the [PostgreSQL log](../../../administration/logs/index.md#postgresql-logs) and
-in the **Retries** section of the [background jobs view](../../../administration/admin_area.md#background-jobs) in the Admin area.
+in the **Retries** section of the [background jobs view](../../../administration/admin_area.md#background-jobs) in the **Admin** area.
If the user being deleted used the [iterations](../../group/iterations/index.md) feature, such
as adding an issue to an iteration, you must use
diff --git a/doc/user/project/clusters/add_eks_clusters.md b/doc/user/project/clusters/add_eks_clusters.md
index e6f76a7a7e3322b404db39d1c016408eee04b12d..c0b71a8ec8bb97ed026a6c2ae00e6fbd0a23ddfc 100644
--- a/doc/user/project/clusters/add_eks_clusters.md
+++ b/doc/user/project/clusters/add_eks_clusters.md
@@ -57,7 +57,7 @@ cluster certificates:
1. Go to your:
- Project's **Operate > Kubernetes clusters** page, for a project-level cluster.
- Group's **Kubernetes** page, for a group-level cluster.
- - The Admin area's **Kubernetes** page, for an instance-level cluster.
+ - The **Admin** area's **Kubernetes** page, for an instance-level cluster.
1. Select **Integrate with a cluster certificate**.
1. Under the **Create new cluster** tab, select **Amazon EKS** to display an
`Account ID` and `External ID` needed for later steps.
diff --git a/doc/user/project/clusters/add_existing_cluster.md b/doc/user/project/clusters/add_existing_cluster.md
index b9eeb080b062cbbe2f27d2c9d23062b2e188fb6e..fe7a7c0b0da62ee780bf7e0ce074c089e485ccd8 100644
--- a/doc/user/project/clusters/add_existing_cluster.md
+++ b/doc/user/project/clusters/add_existing_cluster.md
@@ -30,7 +30,7 @@ To add any cluster to GitLab, you need:
- Either a GitLab.com account or an account for a self-managed installation
- The Maintainer role for group-level and project-level clusters.
-- Access to the Admin area for instance-level clusters.
+- Access to the **Admin** area for instance-level clusters.
- A Kubernetes cluster.
- Cluster administration access to the cluster with `kubectl`.
@@ -71,7 +71,7 @@ To add a Kubernetes cluster to your project, group, or instance:
1. Go to your:
1. Project's **{cloud-gear}** **Operate > Kubernetes clusters** page, for a project-level cluster.
1. Group's **{cloud-gear}** **Kubernetes** page, for a group-level cluster.
- 1. The Admin area's **Kubernetes** page, for an instance-level cluster.
+ 1. The **Admin** area's **Kubernetes** page, for an instance-level cluster.
1. On the **Kubernetes clusters** page, select the **Connect with a certificate** option from the **Actions** dropdown list.
1. On the **Connect a cluster** page, fill in the details:
1. **Kubernetes cluster name** (required) - The name you wish to give the cluster.
diff --git a/doc/user/project/clusters/add_gke_clusters.md b/doc/user/project/clusters/add_gke_clusters.md
index ee82b2729edb7c9da88841e17377da9e0d050ded..9303c2ad708fdac0d5b5719b1eb88cadf5821f05 100644
--- a/doc/user/project/clusters/add_gke_clusters.md
+++ b/doc/user/project/clusters/add_gke_clusters.md
@@ -65,7 +65,7 @@ cluster certificates:
- Project's **{cloud-gear}** **Operate > Kubernetes clusters** page, for a project-level
cluster.
- Group's **{cloud-gear}** **Kubernetes** page, for a group-level cluster.
- - The Admin area's **Kubernetes** page, for an instance-level cluster.
+ - The **Admin** area's **Kubernetes** page, for an instance-level cluster.
1. Select **Integrate with a cluster certificate**.
1. Under the **Create new cluster** tab, select **Google GKE**.
1. Connect your Google account if you haven't done already by selecting the
diff --git a/doc/user/project/clusters/add_remove_clusters.md b/doc/user/project/clusters/add_remove_clusters.md
index f3bbf6291e6861b6b0c82c1973797d8e1de0f6f5..98950951746137dcf2e6497b5c1f6db80d20d9c4 100644
--- a/doc/user/project/clusters/add_remove_clusters.md
+++ b/doc/user/project/clusters/add_remove_clusters.md
@@ -23,7 +23,7 @@ When you successfully connect an existing cluster using cluster certificates, th
1. Go to your:
- Project's **{cloud-gear}** **Operate > Kubernetes clusters** page, for a project-level cluster.
- Group's **{cloud-gear}** **Kubernetes** page, for a group-level cluster.
- - The Admin area's **Kubernetes** page, for an instance-level cluster.
+ - The **Admin** area's **Kubernetes** page, for an instance-level cluster.
1. Select the name of the cluster you want to disable.
1. Toggle **GitLab Integration** off (in gray).
1. Select **Save changes**.
diff --git a/doc/user/project/project_topics.md b/doc/user/project/project_topics.md
index 39773559b02d20b7d18bf41213bbf5349b787737..5ca95231489cc4e784eddcc9b2e271700c071f81 100644
--- a/doc/user/project/project_topics.md
+++ b/doc/user/project/project_topics.md
@@ -90,4 +90,4 @@ To assign topics to a project:
## Administer topics
Instance administrators can administer all project topics from the
-[Admin area's Topics page](../../administration/admin_area.md#administering-topics).
+[**Admin** area's Topics page](../../administration/admin_area.md#administering-topics).
diff --git a/doc/user/project/protected_branches.md b/doc/user/project/protected_branches.md
index a867010a0a9ea7e3303ed56eef90863cdfa20146..3fb6c715d0656cd6bd1da4b45b06aff5879843c3 100644
--- a/doc/user/project/protected_branches.md
+++ b/doc/user/project/protected_branches.md
@@ -89,7 +89,7 @@ that matches `v1.x` must set `Allowed to push and merge` to `No one`, like this:
### Set the default branch protection level
Administrators can set a default branch protection level in the
-[Admin area](../project/repository/branches/default.md#instance-level-default-branch-protection).
+[**Admin** area](../project/repository/branches/default.md#instance-level-default-branch-protection).
## Add protection to existing branches
diff --git a/doc/user/project/settings/import_export.md b/doc/user/project/settings/import_export.md
index 9b6194ceb81a31dce18ae8169c9626ff53181501..46b061e73a9da6dc483d1b47adbbb28627ddc310 100644
--- a/doc/user/project/settings/import_export.md
+++ b/doc/user/project/settings/import_export.md
@@ -273,7 +273,7 @@ DETAILS:
Administrators can set the maximum import file size one of two ways:
- With the `max_import_size` option in the [Application settings API](../../../api/settings.md#change-application-settings).
-- In the [Admin area UI](../../../administration/settings/import_and_export_settings.md#max-import-size).
+- In the [**Admin** area UI](../../../administration/settings/import_and_export_settings.md#max-import-size).
The default is `0` (unlimited).
@@ -329,7 +329,7 @@ The maximum import file size depends on whether you import to a GitLab self-mana
- If importing to a GitLab self-managed instance, you can import a import file of any size. Administrators can change
this behavior using either:
- The `max_import_size` option in the [Application settings API](../../../api/settings.md#change-application-settings).
- - The [Admin area](../../../administration/settings/account_and_limit_settings.md).
+ - The [**Admin** area](../../../administration/settings/account_and_limit_settings.md).
- On GitLab.com, you can import groups using import files of no more than
[5 GB](../../gitlab_com/index.md#account-and-limit-settings) in size.
diff --git a/doc/user/project/working_with_projects.md b/doc/user/project/working_with_projects.md
index de6b3b9d4aedb2ebd0b811b6b34c633a1fdc2250..6a16a27bd0c1ca068fdfc0d2719d07ed00561f9b 100644
--- a/doc/user/project/working_with_projects.md
+++ b/doc/user/project/working_with_projects.md
@@ -186,7 +186,7 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - Option to delete projects immediately from the Admin area and as a group setting removed [on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/393622) and [on self-managed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/119606) in GitLab 16.0.
+> - Option to delete projects immediately from the **Admin** area and as a group setting removed [on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/393622) and [on self-managed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/119606) in GitLab 16.0.
Prerequisites: