Changed user/admin to administration path

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/384335

doc/security/rate_limits.md

@@ -31,21 +31,21 @@ similarly mitigated by a rate limit.
 
 You can set these rate limits in the Admin Area of your instance:
 
-- [Import/Export rate limits](../user/admin_area/settings/import_export_rate_limits.md)
-- [Issue rate limits](../user/admin_area/settings/rate_limit_on_issues_creation.md)
-- [Note rate limits](../user/admin_area/settings/rate_limit_on_notes_creation.md)
-- [Protected paths](../user/admin_area/settings/protected_paths.md)
-- [Raw endpoints rate limits](../user/admin_area/settings/rate_limits_on_raw_endpoints.md)
-- [User and IP rate limits](../user/admin_area/settings/user_and_ip_rate_limits.md)
-- [Package registry rate limits](../user/admin_area/settings/package_registry_rate_limits.md)
-- [Git LFS rate limits](../user/admin_area/settings/git_lfs_rate_limits.md)
-- [Rate limits on Git SSH operations](../user/admin_area/settings/rate_limits_on_git_ssh_operations.md)
-- [Files API rate limits](../user/admin_area/settings/files_api_rate_limits.md)
-- [Deprecated API rate limits](../user/admin_area/settings/deprecated_api_rate_limits.md)
+- [Import/Export rate limits](../administration/settings/import_export_rate_limits.md)
+- [Issue rate limits](../administration/settings/rate_limit_on_issues_creation.md)
+- [Note rate limits](../administration/settings/rate_limit_on_notes_creation.md)
+- [Protected paths](../administration/settings/protected_paths.md)
+- [Raw endpoints rate limits](../administration/settings/rate_limits_on_raw_endpoints.md)
+- [User and IP rate limits](../administration/settings/user_and_ip_rate_limits.md)
+- [Package registry rate limits](../administration/settings/package_registry_rate_limits.md)
+- [Git LFS rate limits](../administration/settings/git_lfs_rate_limits.md)
+- [Rate limits on Git SSH operations](../administration/settings/rate_limits_on_git_ssh_operations.md)
+- [Files API rate limits](../administration/settings/files_api_rate_limits.md)
+- [Deprecated API rate limits](../administration/settings/deprecated_api_rate_limits.md)
 - [GitLab Pages rate limits](../administration/pages/index.md#rate-limits)
-- [Pipeline rate limits](../user/admin_area/settings/rate_limit_on_pipelines_creation.md)
-- [Incident management rate limits](../user/admin_area/settings/incident_management_rate_limits.md)
-- [Unauthenticated access to Projects List API rate limits](../user/admin_area/settings/rate_limit_on_projects_api.md)
+- [Pipeline rate limits](../administration/settings/rate_limit_on_pipelines_creation.md)
+- [Incident management rate limits](../administration/settings/incident_management_rate_limits.md)
+- [Unauthenticated access to Projects List API rate limits](../administration/settings/rate_limit_on_projects_api.md)
 
 You can set these rate limits using the Rails console:
 

doc/security/responding_to_security_incidents.md

@@ -45,7 +45,7 @@ If you suspect that your GitLab instance has been compromised, consider taking t
 
 - [Review the audit events](../administration/audit_events.md) available to you for suspicious account behavior.
 - [Review all users](../administration/moderate_users.md) (including the Administrative root user), and follow the steps in [Suspected compromised user account](#suspected-compromised-user-account) if necessary.
-- Review the [Credentials Inventory](../user/admin_area/credentials_inventory.md), if available to you.
+- Review the [Credentials Inventory](../administration/credentials_inventory.md), if available to you.
 - Change any sensitive credentials, variables, tokens, and secrets. For example, those located in instance configuration, database,
   CI/CD pipelines, or elsewhere.
 - Upgrade to the latest version of GitLab and adopt a plan to upgrade after every security patch release.

doc/subscriptions/bronze_starter.md

@@ -21,7 +21,7 @@ the tiers are no longer mentioned in GitLab documentation:
 - [Code owners](../user/project/codeowners/index.md)
 - Description templates:
   - [Setting a default template for merge requests and issues](../user/project/description_templates.md#set-a-default-template-for-merge-requests-and-issues)
-- [Email from GitLab](../user/admin_area/email_from_gitlab.md)
+- [Email from GitLab](../administration/email_from_gitlab.md)
 - Groups:
   - [Creating group memberships via CN](../user/group/access_and_permissions.md#create-group-links-via-cn)
   - [Group push rules](../user/group/access_and_permissions.md#group-push-rules)

doc/subscriptions/self_managed/index.md

@@ -101,7 +101,7 @@ The user must not be assigned any other role, anywhere in the instance.
 NOTE:
 If a user creates a project, they are assigned the Maintainer or Owner role.
 To prevent a user from creating projects, as an administrator, you can mark the user
-as [external](../../user/admin_area/external_users.md).
+as [external](../../administration/external_users.md).
 
 ## Tips for managing users and subscription seats
 
@@ -119,7 +119,7 @@ GitLab has several features which can help you manage the number of users:
 - Enable `block_auto_created_users` for new sign-ups via [LDAP](../../administration/auth/ldap/index.md#basic-configuration-settings) or [OmniAuth](../../integration/omniauth.md#configure-common-settings).
 - Enable the [User cap](../../administration/settings/sign_up_restrictions.md#user-cap)
   option. **Available in GitLab 13.7 and later**.
-- [Disable new sign-ups](../../user/admin_area/settings/sign_up_restrictions.md), and instead manage new
+- [Disable new sign-ups](../../administration/settings/sign_up_restrictions.md), and instead manage new
   users manually.
 - View a breakdown of users by role in the [Users statistics](../../administration/admin_area.md#users-statistics) page.
 
@@ -421,7 +421,7 @@ The following is emailed to you:
   [**View invoices**](https://customers.gitlab.com/receipts).
 - A new activation code for your license.
 
-[Add the activation code](../../user/admin_area/license.md) to your instance.
+[Add the activation code](../../administration/license.md) to your instance.
 The new tier takes effect when the new license is activated.
 
 ## Add or change the contacts for your subscription

doc/user/gitlab_com/index.md

@@ -351,7 +351,7 @@ after the limits change in January, 2021:
 
 More details are available on the rate limits for
 [protected paths](#protected-paths-throttle) and
-[raw endpoints](../../user/admin_area/settings/rate_limits_on_raw_endpoints.md).
+[raw endpoints](../../administration/settings/rate_limits_on_raw_endpoints.md).
 
 GitLab can rate-limit requests at several layers. The rate limits listed here
 are configured in the application. These limits are the most

doc/user/project/index.md

@@ -68,7 +68,7 @@ For this reason, the creation date of imported objects can be older than the cre
 
 Custom project templates are available at:
 
-- The [instance-level](../../user/admin_area/custom_project_templates.md)
+- The [instance-level](../../administration/custom_project_templates.md)
 - The [group-level](../../user/group/custom_project_templates.md)
 
 1. On the left sidebar, at the top, select **Create new** (**{plus}**) and **New project/repository**.

doc/user/snippets.md

@@ -253,7 +253,7 @@ GitLab forwards the spam to Akismet.
 
 ### Reduce snippets repository size
 
-Because versioned snippets are considered as part of the [namespace storage size](../user/admin_area/settings/account_and_limit_settings.md),
+Because versioned snippets are considered as part of the [namespace storage size](../administration/settings/account_and_limit_settings.md),
 it's recommended to keep snippets' repositories as compact as possible.
 
 For more information about tools to compact repositories,