diff options
Diffstat (limited to 'doc')
73 files changed, 143 insertions, 146 deletions
diff --git a/doc/administration/auth/ldap/ldap-troubleshooting.md b/doc/administration/auth/ldap/ldap-troubleshooting.md index c2ff4958681..9dcc9ac68a6 100644 --- a/doc/administration/auth/ldap/ldap-troubleshooting.md +++ b/doc/administration/auth/ldap/ldap-troubleshooting.md @@ -167,7 +167,7 @@ may see the following message: `Access denied for your LDAP account`. We have a workaround, based on toggling the access level of affected users: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Users**. +1. Select **Overview > Users**. 1. Select the name of the affected user. 1. In the upper-right corner, select **Edit**. 1. Change the user's access level from `Regular` to `Administrator` (or vice versa). diff --git a/doc/administration/auth/ldap/ldap_synchronization.md b/doc/administration/auth/ldap/ldap_synchronization.md index 35d9cf1a068..75c257c1009 100644 --- a/doc/administration/auth/ldap/ldap_synchronization.md +++ b/doc/administration/auth/ldap/ldap_synchronization.md @@ -502,8 +502,8 @@ To enable global group memberships lock: 1. [Configure LDAP](index.md#configure-ldap). 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. -1. Expand the **Visibility and access controls** section. +1. Select **Settings > General**. +1. Expand **Visibility and access controls**. 1. Ensure the **Lock memberships to LDAP synchronization** checkbox is selected. ### Change LDAP group synchronization settings management diff --git a/doc/administration/custom_project_templates.md b/doc/administration/custom_project_templates.md index efd95cf8394..3c3319c80f9 100644 --- a/doc/administration/custom_project_templates.md +++ b/doc/administration/custom_project_templates.md @@ -25,7 +25,7 @@ might modify the template projects without understanding the side effects. To select the group to manage the project templates for your instance: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Templates**. +1. Select **Settings > Templates**. 1. Expand **Custom project templates**. 1. Select a group to use. 1. Select **Save changes**. diff --git a/doc/administration/geo/disaster_recovery/background_verification.md b/doc/administration/geo/disaster_recovery/background_verification.md index 6ed3d0e41ac..a927450d80f 100644 --- a/doc/administration/geo/disaster_recovery/background_verification.md +++ b/doc/administration/geo/disaster_recovery/background_verification.md @@ -28,7 +28,7 @@ the site more time before scheduling a planned failover. On the **primary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites**. +1. Select **Geo > Sites**. 1. Expand **Verification information** tab for that site to view automatic checksumming status for repositories and wikis. Successes are shown in green, pending work in gray, and failures in red. @@ -38,7 +38,7 @@ On the **primary** site: On the **secondary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites**. +1. Select **Geo > Sites**. 1. Expand **Verification information** tab for that site to view automatic checksumming status for repositories and wikis. Successes are shown in green, pending work in gray, and failures in red. @@ -66,7 +66,7 @@ increase load and vice versa. On the **primary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites**. +1. Select **Geo > Sites**. 1. Select **Edit** for the **primary** site to customize the minimum re-verification interval: diff --git a/doc/administration/geo/disaster_recovery/planned_failover.md b/doc/administration/geo/disaster_recovery/planned_failover.md index 6c2abf4b906..01e5c33a726 100644 --- a/doc/administration/geo/disaster_recovery/planned_failover.md +++ b/doc/administration/geo/disaster_recovery/planned_failover.md @@ -154,7 +154,7 @@ ensure these processes are close to 100% as possible during active use. On the **secondary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites**. +1. Select **Geo > Sites**. Replicated objects (shown in green) should be close to 100%, and there should be no failures (shown in red). If a large proportion of objects aren't yet replicated (shown in gray), consider giving the site more @@ -182,7 +182,7 @@ This [content was moved to another location](background_verification.md). On the **primary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Messages**. +1. Select **Messages**. 1. Add a message notifying users on the maintenance window. You can check under **Geo > Sites** to estimate how long it takes to finish syncing. @@ -195,7 +195,7 @@ be disabled on the **primary** site: 1. Enable [maintenance mode](../../maintenance_mode/index.md) on the **primary** site. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Monitoring > Background Jobs**. +1. Select **Monitoring > Background Jobs**. 1. On the Sidekiq dashboard, select **Cron**. 1. Select `Disable All` to disable non-Geo periodic background jobs. 1. Select `Enable` for the `geo_sidekiq_cron_config_worker` cron job. diff --git a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md index 4125d7fa1de..f24d2bba2a3 100644 --- a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md +++ b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md @@ -65,7 +65,7 @@ promote a Geo replica and perform a failover. On the **secondary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites** to see its status. +1. Select **Geo > Sites** to see its status. Replicated objects (shown in green) should be close to 100%, and there should be no failures (shown in red). If a large proportion of objects aren't replicated (shown in gray), consider giving the site more diff --git a/doc/administration/geo/index.md b/doc/administration/geo/index.md index c0f3e1f0ba9..3dff40905d8 100644 --- a/doc/administration/geo/index.md +++ b/doc/administration/geo/index.md @@ -160,7 +160,7 @@ public URL of the primary site is used. To update the internal URL of the primary Geo site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites**. +1. Select **Geo > Sites**. 1. Select **Edit** on the primary site. 1. Change the **Internal URL**, then select **Save changes**. diff --git a/doc/administration/geo/replication/container_registry.md b/doc/administration/geo/replication/container_registry.md index ab45531527f..b9bee753089 100644 --- a/doc/administration/geo/replication/container_registry.md +++ b/doc/administration/geo/replication/container_registry.md @@ -166,7 +166,7 @@ For each application and Sidekiq node on the **secondary** site: To verify container registry replication is working, on the **secondary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Nodes**. +1. Select **Geo > Nodes**. The initial replication, or "backfill", is probably still in progress. You can monitor the synchronization process on each Geo site from the **primary** site's **Geo Nodes** dashboard in your browser. diff --git a/doc/administration/geo/replication/disable_geo.md b/doc/administration/geo/replication/disable_geo.md index 9f05179abed..597bb08c188 100644 --- a/doc/administration/geo/replication/disable_geo.md +++ b/doc/administration/geo/replication/disable_geo.md @@ -36,7 +36,7 @@ To remove the **primary** site: 1. [Remove all secondary Geo sites](remove_geo_site.md) 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Nodes**. +1. Select **Geo > Nodes**. 1. Select **Remove** for the **primary** node. 1. Confirm by selecting **Remove** when the prompt appears. diff --git a/doc/administration/geo/replication/object_storage.md b/doc/administration/geo/replication/object_storage.md index 7d54293d436..9d1cb4387a0 100644 --- a/doc/administration/geo/replication/object_storage.md +++ b/doc/administration/geo/replication/object_storage.md @@ -43,7 +43,7 @@ whether they are stored on the local file system or in object storage. To enable GitLab replication: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Nodes**. +1. Select **Geo > Nodes**. 1. Select **Edit** on the **secondary** site. 1. In the **Synchronization Settings** section, find the **Allow this secondary node to replicate content on Object Storage** checkbox to enable it. diff --git a/doc/administration/geo/replication/remove_geo_site.md b/doc/administration/geo/replication/remove_geo_site.md index cf87966da91..4787b949e2e 100644 --- a/doc/administration/geo/replication/remove_geo_site.md +++ b/doc/administration/geo/replication/remove_geo_site.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w **Secondary** sites can be removed from the Geo cluster using the Geo administration page of the **primary** site. To remove a **secondary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Nodes**. +1. Select **Geo > Nodes**. 1. For the **secondary** site you want to remove, select **Remove**. 1. Confirm by selecting **Remove** when the prompt appears. diff --git a/doc/administration/geo/replication/troubleshooting.md b/doc/administration/geo/replication/troubleshooting.md index ae8f640ee8a..aec8de24e1d 100644 --- a/doc/administration/geo/replication/troubleshooting.md +++ b/doc/administration/geo/replication/troubleshooting.md @@ -28,7 +28,7 @@ Before attempting more advanced troubleshooting: On the **primary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites**. +1. Select **Geo > Sites**. We perform the following health checks on each **secondary** site to help identify if something is wrong: @@ -1527,7 +1527,7 @@ If you have updated the value of `external_url` in `/etc/gitlab/gitlab.rb` for t In this case, make sure to update the changed URL on all your sites: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites**. +1. Select **Geo > Sites**. 1. Change the URL and save the change. ### Message: `ERROR: canceling statement due to conflict with recovery` during backup @@ -1632,7 +1632,7 @@ site's URL matches its external URL. On the **primary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites**. +1. Select **Geo > Sites**. 1. Find the affected **secondary** site and select **Edit**. 1. Ensure the **URL** field matches the value found in `/etc/gitlab/gitlab.rb` in `external_url "https://gitlab.example.com"` on the **Rails nodes of the secondary** site. diff --git a/doc/administration/geo/replication/tuning.md b/doc/administration/geo/replication/tuning.md index c15f52737a6..c02571e21a8 100644 --- a/doc/administration/geo/replication/tuning.md +++ b/doc/administration/geo/replication/tuning.md @@ -14,7 +14,7 @@ in the background. On the **primary** site: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Geo > Sites**. +1. Select **Geo > Sites**. 1. Select **Edit** of the secondary site you want to tune. 1. Under **Tuning settings**, there are several variables that can be tuned to improve the performance of Geo: diff --git a/doc/administration/gitaly/troubleshooting.md b/doc/administration/gitaly/troubleshooting.md index 92a5ec4799a..cccec2b9310 100644 --- a/doc/administration/gitaly/troubleshooting.md +++ b/doc/administration/gitaly/troubleshooting.md @@ -21,7 +21,7 @@ When using standalone Gitaly servers, you must make sure they are the same versi as GitLab to ensure full compatibility: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Gitaly Servers**. +1. Select **Overview > Gitaly Servers**. 1. Confirm all Gitaly servers indicate that they are up to date. ### Find storage resource details diff --git a/doc/administration/housekeeping.md b/doc/administration/housekeeping.md index fd349191198..a0ef6a66495 100644 --- a/doc/administration/housekeeping.md +++ b/doc/administration/housekeeping.md @@ -77,7 +77,7 @@ frequently. You can change how often Gitaly is asked to optimize a repository. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Repository**. +1. Select **Settings > Repository**. 1. Expand **Repository maintenance**. 1. In the **Housekeeping** section, configure the housekeeping options. 1. Select **Save changes**. diff --git a/doc/administration/img/email1.png b/doc/administration/img/email1.png Binary files differdeleted file mode 100644 index e79ccc3e9a9..00000000000 --- a/doc/administration/img/email1.png +++ /dev/null diff --git a/doc/administration/img/email2.png b/doc/administration/img/email2.png Binary files differdeleted file mode 100644 index d073c0e42da..00000000000 --- a/doc/administration/img/email2.png +++ /dev/null diff --git a/doc/administration/inactive_project_deletion.md b/doc/administration/inactive_project_deletion.md index d46ef4eb8ca..3c340448cee 100644 --- a/doc/administration/inactive_project_deletion.md +++ b/doc/administration/inactive_project_deletion.md @@ -24,7 +24,7 @@ For the default setting on GitLab.com, see the [GitLab.com settings page](../use To configure deletion of inactive projects: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Repository**. +1. Select **Settings > Repository**. 1. Expand **Repository maintenance**. 1. In the **Inactive project deletion** section, select **Delete inactive projects**. 1. Configure the settings. diff --git a/doc/administration/integration/diagrams_net.md b/doc/administration/integration/diagrams_net.md index 64d4a02b87a..42286428bb1 100644 --- a/doc/administration/integration/diagrams_net.md +++ b/doc/administration/integration/diagrams_net.md @@ -46,7 +46,7 @@ For more information, see [Run your own diagrams.net server with Docker](https:/ 1. Sign in to GitLab as an [Administrator](../../user/permissions.md) user. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **Diagrams.net**. 1. Select the **Enable Diagrams.net** checkbox. 1. Enter the Diagrams.net URL. To connect to: diff --git a/doc/administration/maintenance_mode/index.md b/doc/administration/maintenance_mode/index.md index ae22fdf3ec1..f4823ce9af1 100644 --- a/doc/administration/maintenance_mode/index.md +++ b/doc/administration/maintenance_mode/index.md @@ -180,7 +180,7 @@ you should disable all cron jobs except for those related to Geo. To monitor queues and disable jobs: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Monitoring > Background Jobs**. +1. Select **Monitoring > Background Jobs**. 1. In the Sidekiq dashboard, select **Cron** and disable jobs individually or all at once by selecting **Disable All**. ### Incident management diff --git a/doc/administration/monitoring/performance/gitlab_configuration.md b/doc/administration/monitoring/performance/gitlab_configuration.md index 05742827766..7dc4f34e514 100644 --- a/doc/administration/monitoring/performance/gitlab_configuration.md +++ b/doc/administration/monitoring/performance/gitlab_configuration.md @@ -10,8 +10,7 @@ GitLab Performance Monitoring is disabled by default. To enable it and change an settings: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Metrics and profiling** - (`/admin/application_settings/metrics_and_profiling`). +1. Select **Settings > Metrics and profiling**. 1. Add the necessary configuration changes. 1. Restart all GitLab for the changes to take effect: diff --git a/doc/administration/monitoring/performance/grafana_configuration.md b/doc/administration/monitoring/performance/grafana_configuration.md index 1fcca97734f..0d264972073 100644 --- a/doc/administration/monitoring/performance/grafana_configuration.md +++ b/doc/administration/monitoring/performance/grafana_configuration.md @@ -35,8 +35,8 @@ After setting up Grafana, you can enable a link to access it from the GitLab sidebar: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Metrics and profiling** - and expand **Metrics - Grafana**. +1. Select **Settings > Metrics and profiling**. +1. Expand **Metrics - Grafana**. 1. Select the **Add a link to Grafana** checkbox. 1. Configure the **Grafana URL**. Enter the full URL of the Grafana instance. 1. Select **Save changes**. diff --git a/doc/administration/monitoring/performance/performance_bar.md b/doc/administration/monitoring/performance/performance_bar.md index e107c052260..a8bf39761ed 100644 --- a/doc/administration/monitoring/performance/performance_bar.md +++ b/doc/administration/monitoring/performance/performance_bar.md @@ -108,9 +108,8 @@ for a given group: 1. Sign in as a user with administrator access. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Metrics and profiling** - (`admin/application_settings/metrics_and_profiling`), and expand - **Profiling - Performance bar**. +1. Select **Settings > Metrics and profiling**. +1. Expand **Profiling - Performance bar**. 1. Select **Allow non-administrators access to the performance bar**. 1. In the **Allow access to members of the following group** field, provide the full path of the group allowed to access the performance. diff --git a/doc/administration/monitoring/prometheus/gitlab_metrics.md b/doc/administration/monitoring/prometheus/gitlab_metrics.md index 913a730ee6b..3726924b82c 100644 --- a/doc/administration/monitoring/prometheus/gitlab_metrics.md +++ b/doc/administration/monitoring/prometheus/gitlab_metrics.md @@ -10,7 +10,7 @@ To enable the GitLab Prometheus metrics: 1. Log in to GitLab as a user with administrator access. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Metrics and profiling**. +1. Select **Settings > Metrics and profiling**. 1. Find the **Metrics - Prometheus** section, and select **Enable GitLab Prometheus metrics endpoint**. 1. [Restart GitLab](../../restart_gitlab.md#reconfigure-a-linux-package-installation) for the changes to take effect. diff --git a/doc/administration/operations/fast_ssh_key_lookup.md b/doc/administration/operations/fast_ssh_key_lookup.md index a2ef8a0a573..2170abf8700 100644 --- a/doc/administration/operations/fast_ssh_key_lookup.md +++ b/doc/administration/operations/fast_ssh_key_lookup.md @@ -122,7 +122,7 @@ users as long as a large file exists. To disable writes to the `authorized_keys` file: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Network**. +1. Select **Settings > Network**. 1. Expand **Performance optimization**. 1. Clear the **Use authorized_keys file to authenticate SSH keys** checkbox. 1. Select **Save changes**. diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md index 3377a067e03..bfeca7c56b9 100644 --- a/doc/administration/packages/container_registry.md +++ b/doc/administration/packages/container_registry.md @@ -346,7 +346,7 @@ In GitLab, tokens for the container registry expire every five minutes. To increase the token duration: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > CI/CD**. +1. Select **Settings > CI/CD**. 1. Expand **Container Registry**. 1. For the **Authorization token duration (minutes)**, update the value. 1. Select **Save changes**. diff --git a/doc/administration/pages/index.md b/doc/administration/pages/index.md index ddbaf540dbd..c73de881470 100644 --- a/doc/administration/pages/index.md +++ b/doc/administration/pages/index.md @@ -546,7 +546,7 @@ If your user base is private or otherwise trusted, you can disable the verification requirement: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Preferences**. +1. Select **Settings > Preferences**. 1. Expand **Pages**. 1. Clear the **Require users to prove ownership of custom domains** checkbox. This setting is enabled by default. @@ -563,7 +563,7 @@ To enable it: 1. Choose an email address on which you want to receive notifications about expiring domains. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Preferences**. +1. Select **Settings > Preferences**. 1. Expand **Pages**. 1. Enter the email address for receiving notifications and accept Let's Encrypt's Terms of Service. 1. Select **Save changes**. @@ -616,7 +616,7 @@ this: 1. Enable [access control](#access-control). 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Applications**. +1. Select **Applications**. 1. Expand **GitLab Pages**. 1. Clear the `api` scope's checkbox and select the desired scope's checkbox (for example, `read_api`). @@ -635,7 +635,7 @@ of your instance only. To do that: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Preferences**. +1. Select **Settings > Preferences**. 1. Expand **Pages**. 1. Select the **Disable public access to Pages sites** checkbox. 1. Select **Save changes**. @@ -828,7 +828,7 @@ Prerequisites: To set the global maximum pages size for a project: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Preferences**. +1. Select **Settings > Preferences**. 1. Expand **Pages**. 1. In **Maximum size of pages**, enter a value. The default is `100`. 1. Select **Save changes**. @@ -869,7 +869,8 @@ Prerequisites: To set the maximum number of GitLab Pages custom domains for a project: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Preferences**, and expand **Pages**. +1. Select **Settings > Preferences**. +1. Expand **Pages**. 1. Enter a value for **Maximum number of custom domains per project**. Use `0` for unlimited domains. 1. Select **Save changes**. diff --git a/doc/administration/pages/source.md b/doc/administration/pages/source.md index 545b60ac659..4e88d4aa4f3 100644 --- a/doc/administration/pages/source.md +++ b/doc/administration/pages/source.md @@ -480,7 +480,7 @@ The default for the maximum size of unpacked archives per project is 100 MB. To change this value: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Preferences**. +1. Select **Settings > Preferences**. 1. Expand **Pages**. 1. Update the value for **Maximum size of pages (MB)**. diff --git a/doc/administration/pages/troubleshooting.md b/doc/administration/pages/troubleshooting.md index 1a0aa45abc5..7a93c8a0f76 100644 --- a/doc/administration/pages/troubleshooting.md +++ b/doc/administration/pages/troubleshooting.md @@ -171,7 +171,7 @@ Upgrading to an [officially supported operating system](https://about.gitlab.com This problem comes from the permissions of the GitLab Pages OAuth application. To fix it: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Applications > GitLab Pages**. +1. Select **Applications > GitLab Pages**. 1. Edit the application. 1. Under **Scopes**, ensure that the `api` scope is selected. 1. Save your changes. diff --git a/doc/administration/polling.md b/doc/administration/polling.md index 4317ad1c1d6..5edba91165f 100644 --- a/doc/administration/polling.md +++ b/doc/administration/polling.md @@ -27,7 +27,7 @@ The default value (`1`) is recommended for the majority of GitLab installations. To adjust the polling interval multiplier: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Preferences**. +1. Select **Settings > Preferences**. 1. Expand **Polling interval multiplier**. 1. Set a value for the polling interval multiplier. This multiplier is applied to all resources at once. diff --git a/doc/administration/repository_checks.md b/doc/administration/repository_checks.md index 9d4ff4e47df..85a74199022 100644 --- a/doc/administration/repository_checks.md +++ b/doc/administration/repository_checks.md @@ -21,7 +21,7 @@ committed to a repository. GitLab administrators can: To check a project's repository using GitLab UI: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Projects**. +1. Select **Overview > Projects**. 1. Select the project to check. 1. In the **Repository check** section, select **Trigger repository check**. @@ -33,8 +33,8 @@ project page in the Admin Area. If the checks fail, see [what to do](#what-to-do Instead of checking repositories manually, GitLab can be configured to run the checks periodically: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Repository** (`/admin/application_settings/repository`). -1. Expand the **Repository maintenance** section. +1. Select **Settings > Repository**. +1. Expand **Repository maintenance**. 1. Enable **Enable repository checks**. When enabled, GitLab periodically runs a repository check on all project repositories and wiki @@ -86,8 +86,8 @@ If a repository check fails, locate the error in the [`repocheck.log` file](logs If periodic repository checks cause false alarms, you can clear all repository check states: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Repository** (`/admin/application_settings/repository`). -1. Expand the **Repository maintenance** section. +1. Select **Settings > Repository**. +1. Expand **Repository maintenance**. 1. Select **Clear all repository checks**. ## Troubleshooting diff --git a/doc/administration/repository_storage_paths.md b/doc/administration/repository_storage_paths.md index 6f42cc2f75c..efa719d103b 100644 --- a/doc/administration/repository_storage_paths.md +++ b/doc/administration/repository_storage_paths.md @@ -67,7 +67,7 @@ Administrators can look up a project's hashed path from its name or ID using: To look up a project's hash path in the Admin Area: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Projects** and select the project. +1. Select **Overview > Projects** and select the project. 1. Locate the **Relative path** field. The value is similar to: ```plaintext @@ -205,8 +205,8 @@ LFS objects are also [S3-compatible](lfs/index.md#storing-lfs-objects-in-remote- After you configure multiple repository storages, you can choose where new repositories are stored: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Repository** and expand the **Repository storage** - section. +1. Select **Settings > Repository**. +1. Expand **Repository storage**. 1. Enter values in the **Storage nodes for new repositories** fields. 1. Select **Save changes**. diff --git a/doc/administration/settings/jira_cloud_app.md b/doc/administration/settings/jira_cloud_app.md index c58e9eefdd9..b73d75e52a1 100644 --- a/doc/administration/settings/jira_cloud_app.md +++ b/doc/administration/settings/jira_cloud_app.md @@ -30,7 +30,7 @@ You must set up OAuth authentication to: To create an OAuth application on your self-managed instance: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Applications**. +1. Select **Applications**. 1. Select **New application**. 1. In **Redirect URI**: - If you're installing the app from the official marketplace listing, enter `https://gitlab.com/-/jira_connect/oauth_callbacks`. @@ -109,7 +109,7 @@ With this method: To set up your self-managed instance for the GitLab for Jira Cloud app in GitLab 15.7 and later: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **GitLab for Jira App**. 1. In **Jira Connect Proxy URL**, enter `https://gitlab.com`. 1. Select **Save changes**. @@ -230,7 +230,7 @@ You might want to use a proxy if you're managing multiple GitLab instances but o To configure your GitLab instance to serve as a proxy: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **GitLab for Jira App**. 1. Select **Enable public key storage**. 1. Select **Save changes**. diff --git a/doc/administration/settings/slack_app.md b/doc/administration/settings/slack_app.md index a55d636dbd4..b4a4df8faa3 100644 --- a/doc/administration/settings/slack_app.md +++ b/doc/administration/settings/slack_app.md @@ -46,7 +46,7 @@ You're then redirected to Slack for the next steps. After you've [created a GitLab for Slack app](#create-a-gitlab-for-slack-app), you can configure the settings in GitLab: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **GitLab for Slack app**. 1. Select the **Enable GitLab for Slack app** checkbox. 1. Enter the details of your GitLab for Slack app: diff --git a/doc/administration/sidekiq/extra_sidekiq_processes.md b/doc/administration/sidekiq/extra_sidekiq_processes.md index 1981ce6bec1..bde60d17f0c 100644 --- a/doc/administration/sidekiq/extra_sidekiq_processes.md +++ b/doc/administration/sidekiq/extra_sidekiq_processes.md @@ -49,7 +49,7 @@ to all available queues: To view the Sidekiq processes in GitLab: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Monitoring > Background Jobs**. +1. Select **Monitoring > Background Jobs**. ## Concurrency diff --git a/doc/administration/static_objects_external_storage.md b/doc/administration/static_objects_external_storage.md index 5696a79dc79..258af6b045b 100644 --- a/doc/administration/static_objects_external_storage.md +++ b/doc/administration/static_objects_external_storage.md @@ -16,8 +16,8 @@ storage such as a content delivery network (CDN). To configure external storage for static objects: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Repository**. -1. Expand the **External storage for repository static objects** section. +1. Select **Settings > Repository**. +1. Expand **External storage for repository static objects**. 1. Enter the base URL and an arbitrary token. When you [set up external storage](#set-up-external-storage), use a script that sets these values as `ORIGIN_HOSTNAME` and `STORAGE_TOKEN`. 1. Select **Save changes**. diff --git a/doc/administration/system_hooks.md b/doc/administration/system_hooks.md index a69e3cc3df8..57a23a25a08 100644 --- a/doc/administration/system_hooks.md +++ b/doc/administration/system_hooks.md @@ -53,7 +53,7 @@ For push and tag events, the same structure and deprecations are followed as [pr To create a system hook: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **System Hooks**. +1. Select **System Hooks**. 1. Select **Add new webhook**. 1. Provide the **URL** and **Secret Token**. 1. Select the checkbox next to each optional **Trigger** you want to enable. diff --git a/doc/administration/whats-new.md b/doc/administration/whats-new.md index 1fca5d600e5..8af9387f821 100644 --- a/doc/administration/whats-new.md +++ b/doc/administration/whats-new.md @@ -32,7 +32,7 @@ You can configure **What's new** to display features based on the tier, or you can hide it. To configure it: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Preferences**. +1. Select **Settings > Preferences**. 1. Expand **What's new**, and choose one of the following options: | Option | Description | diff --git a/doc/ci/pipelines/cicd_minutes.md b/doc/ci/pipelines/cicd_minutes.md index c28e5ac730e..699136ccf97 100644 --- a/doc/ci/pipelines/cicd_minutes.md +++ b/doc/ci/pipelines/cicd_minutes.md @@ -59,7 +59,7 @@ Prerequisites: To change the default quota that applies to all namespaces: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > CI/CD**. +1. Select **Settings > CI/CD**. 1. Expand **Continuous Integration and Deployment**. 1. In the **Compute quota** box, enter a limit. 1. Select **Save changes**. @@ -80,7 +80,7 @@ Prerequisites: To set a compute quota for a namespace: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Groups**. +1. Select **Overview > Groups**. 1. For the group you want to update, select **Edit**. 1. In the **Compute quota** box, enter the maximum number of compute minutes. 1. Select **Save changes**. diff --git a/doc/ci/runners/configure_runners.md b/doc/ci/runners/configure_runners.md index eef78b70155..ad39c3f1546 100644 --- a/doc/ci/runners/configure_runners.md +++ b/doc/ci/runners/configure_runners.md @@ -203,8 +203,8 @@ Prerequisites: To automatically rotate runner authentication tokens: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > CI/CD**. -1. Expand **Continuous Integration and Deployment** +1. Select **Settings > CI/CD**. +1. Expand **Continuous Integration and Deployment**. 1. Set a **Runners expiration** time for runners, leave empty for no expiration. 1. Select **Save changes**. diff --git a/doc/ci/runners/runners_scope.md b/doc/ci/runners/runners_scope.md index 580930d7d92..48f6a22e9b3 100644 --- a/doc/ci/runners/runners_scope.md +++ b/doc/ci/runners/runners_scope.md @@ -48,7 +48,7 @@ When you create a runner, it is assigned a runner authentication token that you To create a shared runner: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **CI/CD > Runners**. +1. Select **CI/CD > Runners**. 1. Select **New instance runner**. 1. Select the operating system where GitLab Runner is installed. 1. In the **Tags** section, in the **Tags** field, enter the job tags to specify jobs the runner can run. @@ -584,7 +584,7 @@ queued for longer than the median value, and half of the jobs queued for less th median value. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **CI/CD > Runners**. +1. Select **CI/CD > Runners**. 1. Select **View metrics**. ## Determine which runners need to be upgraded **(ULTIMATE ALL)** @@ -631,7 +631,7 @@ Prerequisites: To determine the IP address of a shared runner: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **CI/CD > Runners**. +1. Select **CI/CD > Runners**. 1. Find the runner in the table and view the **IP Address** column.  diff --git a/doc/ci/testing/img/code_quality_mr_diff_report_v15_7.png b/doc/ci/testing/img/code_quality_mr_diff_report_v15_7.png Binary files differdeleted file mode 100644 index b45124e0e5d..00000000000 --- a/doc/ci/testing/img/code_quality_mr_diff_report_v15_7.png +++ /dev/null diff --git a/doc/development/img/snowplow_flow.png b/doc/development/img/snowplow_flow.png Binary files differdeleted file mode 100644 index aae597edc13..00000000000 --- a/doc/development/img/snowplow_flow.png +++ /dev/null diff --git a/doc/development/integrations/jenkins.md b/doc/development/integrations/jenkins.md index 5400acd5655..2a9903a0665 100644 --- a/doc/development/integrations/jenkins.md +++ b/doc/development/integrations/jenkins.md @@ -25,7 +25,7 @@ GitLab does not allow requests to localhost or the local network by default. Whe 1. Log into your GitLab instance as an administrator. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Network**. +1. Select **Settings > Network**. 1. Expand **Outbound requests**, and select the following checkboxes: - **Allow requests to the local network from webhooks and integrations** diff --git a/doc/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md b/doc/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md index cfb6e4e1f55..56e83184060 100644 --- a/doc/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md +++ b/doc/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md @@ -55,7 +55,7 @@ On GitLab.com events are sent to a collector configured by GitLab. By default, s You can configure your self-managed GitLab instance to use a custom Snowplow collector. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **Snowplow**. 1. Select **Enable Snowplow tracking** and enter your Snowplow configuration information. For example: diff --git a/doc/install/azure/index.md b/doc/install/azure/index.md index eed512f6e73..3acdaa9a178 100644 --- a/doc/install/azure/index.md +++ b/doc/install/azure/index.md @@ -248,7 +248,7 @@ in this section whenever you need to update GitLab. To determine the version of GitLab you're currently running: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Dashboard**. +1. Select **Overview > Dashboard**. 1. Find the version under the **Components** table. If there's a newer available version of GitLab that contains one or more diff --git a/doc/integration/advanced_search/elasticsearch.md b/doc/integration/advanced_search/elasticsearch.md index 9c926add8c2..0a456e6c73e 100644 --- a/doc/integration/advanced_search/elasticsearch.md +++ b/doc/integration/advanced_search/elasticsearch.md @@ -168,7 +168,7 @@ Prerequisites: To enable advanced search: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Advanced Search**. +1. Select **Settings > Advanced Search**. NOTE: To see the **Advanced Search** section, you need an active GitLab Premium @@ -211,7 +211,7 @@ initial indexing, not to re-create an index from scratch. To enable advanced search with **Index all projects**: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Advanced Search**. +1. Select **Settings > Advanced Search**. 1. Select the **Elasticsearch indexing** checkbox, then select **Save changes**. 1. Select **Index all projects**. 1. Optional. Select **Check progress** to see the status of background jobs. @@ -402,7 +402,7 @@ To enable languages support: 1. Install the desired plugins, refer to [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/7.9/installation.html) for plugins installation instructions. The plugins must be installed on every node in the cluster, and each node must be restarted after installation. For a list of plugins, see the table later in this section. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Advanced Search**. +1. Select **Settings > Advanced Search**. 1. Locate **Custom analyzers: language support**. 1. Enable plugins support for **Indexing**. 1. Select **Save changes** for the changes to take effect. @@ -423,7 +423,7 @@ For guidance on what to install, see the following Elasticsearch language plugin To disable the Elasticsearch integration: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Advanced Search**. +1. Select **Settings > Advanced Search**. 1. Clear the **Elasticsearch indexing** and **Search with Elasticsearch enabled** checkboxes. 1. Select **Save changes**. 1. Optional. For Elasticsearch instances that are still online, delete existing indices: @@ -439,7 +439,7 @@ To disable the Elasticsearch integration: ## Unpause Indexing 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Advanced Search**. +1. Select **Settings > Advanced Search**. 1. Expand **Advanced Search**. 1. Clear the **Pause Elasticsearch indexing** checkbox. @@ -462,7 +462,7 @@ To trigger the reindexing process: 1. Sign in to your GitLab instance as an administrator. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Advanced Search**. +1. Select **Settings > Advanced Search**. 1. Expand **Elasticsearch zero-downtime reindexing**. 1. Select **Trigger cluster reindexing**. @@ -477,7 +477,7 @@ While the reindexing is running, you can follow its progress under that same sec #### Elasticsearch zero-downtime reindexing 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Advanced Search**. +1. Select **Settings > Advanced Search**. 1. Expand **Elasticsearch zero-downtime reindexing**, and you'll find the following options: @@ -525,7 +525,7 @@ Sometimes, you might want to abandon the unfinished reindex job and resume the i ``` 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Advanced Search**. +1. Select **Settings > Advanced Search**. 1. Expand **Advanced Search**. 1. Clear the **Pause Elasticsearch indexing** checkbox. diff --git a/doc/integration/akismet.md b/doc/integration/akismet.md index c4af7deccb9..b8b871d83f2 100644 --- a/doc/integration/akismet.md +++ b/doc/integration/akismet.md @@ -31,7 +31,7 @@ To use Akismet: 1. Select **Show** to reveal the API key, and copy the API key's value. 1. Sign in to GitLab as an administrator. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Reporting**. +1. Select **Settings > Reporting**. 1. Expand **Spam and Anti-bot Protection**. 1. Select the **Enable Akismet** checkbox. 1. Fill in the API key from step 3. diff --git a/doc/integration/datadog.md b/doc/integration/datadog.md index b5ea06cde57..c5fe2bc5f0f 100644 --- a/doc/integration/datadog.md +++ b/doc/integration/datadog.md @@ -28,7 +28,7 @@ project, group, or instance level: 1. *For instance-level integrations:* 1. Sign in to GitLab as a user with administrator access. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Integrations**. +1. Select **Settings > Integrations**. 1. Scroll to **Add an integration**, and select **Datadog**. 1. Select **Active** to enable the integration. 1. Specify the [**Datadog site**](https://docs.datadoghq.com/getting_started/site/) to send data to. diff --git a/doc/integration/kerberos.md b/doc/integration/kerberos.md index 63589ffec33..b5515a730d3 100644 --- a/doc/integration/kerberos.md +++ b/doc/integration/kerberos.md @@ -107,7 +107,7 @@ If you're an administrator, you can link a Kerberos account to an existing GitLab account. To do so: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Users**. +1. Select **Overview > Users**. 1. Select a user, then select the **Identities** tab. 1. From the **Provider** dropdown list, select **Kerberos**. 1. Make sure the **Identifier** corresponds to the Kerberos username. diff --git a/doc/integration/oauth_provider.md b/doc/integration/oauth_provider.md index 63a2a4fabf7..30e14e95d3b 100644 --- a/doc/integration/oauth_provider.md +++ b/doc/integration/oauth_provider.md @@ -76,7 +76,7 @@ To create a new application for a group: To create an application for your GitLab instance: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Applications**. +1. Select **Applications**. 1. Select **New application**. When creating application in the **Admin Area** , mark it as **trusted**. diff --git a/doc/integration/omniauth.md b/doc/integration/omniauth.md index de335b68fdd..ab43a14d169 100644 --- a/doc/integration/omniauth.md +++ b/doc/integration/omniauth.md @@ -258,7 +258,7 @@ By default, sign-in is enabled for all the OAuth providers configured in `config To enable or disable an OmniAuth provider: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **Sign-in restrictions**. 1. In the **Enabled OAuth authentication sources** section, select or clear the checkbox for each provider you want to enable or disable. diff --git a/doc/integration/recaptcha.md b/doc/integration/recaptcha.md index 52d72e56e5b..bee6381a078 100644 --- a/doc/integration/recaptcha.md +++ b/doc/integration/recaptcha.md @@ -18,7 +18,7 @@ To use reCAPTCHA, first create a site and private key. 1. To get reCAPTCHA v2 keys, fill in the form and select **Submit**. 1. Sign in to your GitLab server as an administrator. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Reporting**. +1. Select **Settings > Reporting**. 1. Expand **Spam and Anti-bot Protection**. 1. In the reCAPTCHA fields, enter the keys you obtained in the previous steps. 1. Select the **Enable reCAPTCHA** checkbox. diff --git a/doc/integration/sourcegraph.md b/doc/integration/sourcegraph.md index b8cf4895542..f6fb387f016 100644 --- a/doc/integration/sourcegraph.md +++ b/doc/integration/sourcegraph.md @@ -49,7 +49,7 @@ You can skip this step if you already have your GitLab repositories searchable i ### Configure your GitLab instance with Sourcegraph 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand the **Sourcegraph** configuration section. 1. Check **Enable Sourcegraph**. 1. Set the Sourcegraph URL to your Sourcegraph instance, such as `https://sourcegraph.example.com`. diff --git a/doc/security/hardening_application_recommendations.md b/doc/security/hardening_application_recommendations.md index 9b30d8716bb..857e322191e 100644 --- a/doc/security/hardening_application_recommendations.md +++ b/doc/security/hardening_application_recommendations.md @@ -14,7 +14,7 @@ web interface. ## System hooks 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **System Hooks**. +1. Select **System Hooks**. In a typical hardened environment, internal information is not transmitted or stored outside of the system. For an offline environment system, this is @@ -32,7 +32,7 @@ encouraged for communications through system hooks. ## Push rules 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Push Rules**. +1. Select **Push Rules**. Ensure that the following items are selected: @@ -46,7 +46,7 @@ The adjustments help limit pushes to established and authorized users. ## Deploy keys 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Deploy Keys**. +1. Select **Deploy Keys**. Public deploy keys at are used to give read or read/write access to **all** projects on the instance, and are intended for remote automation to access @@ -58,7 +58,7 @@ the documentation on [deploy keys](../user/project/deploy_keys/index.md) and ## General 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. Hardening adjustments can be made in 4 sections. @@ -176,7 +176,7 @@ For more detailed information, see ## Integrations 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Integrations**. +1. Select **Settings > Integrations**. In general, as long as administrators control and monitor usage, integrations are fine in a hardened environment. Be cautious about integrations that allow @@ -187,7 +187,7 @@ process or authenticated user. ## Metrics and profiling 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Metrics and profiling**. +1. Select **Settings > Metrics and profiling**. The main focus for hardening is **Usage statistics**: @@ -204,7 +204,7 @@ help you make an informed decision, see ## Network 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Network**. +1. Select **Settings > Network**. For any setting that enables rate limiting, make sure it is selected. Default values should be fine. Additionally there are numerous settings that enable access, and all diff --git a/doc/security/password_length_limits.md b/doc/security/password_length_limits.md index 598dc70732d..177d5564e7d 100644 --- a/doc/security/password_length_limits.md +++ b/doc/security/password_length_limits.md @@ -24,7 +24,7 @@ The user password length is set to a minimum of 8 characters by default. To change the minimum password length using GitLab UI: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **Sign-up restrictions**. 1. Enter a **Minimum password length** value greater than or equal to `8`. 1. Select **Save changes**. diff --git a/doc/security/reset_user_password.md b/doc/security/reset_user_password.md index 74adeeea5a0..ffee1208f2a 100644 --- a/doc/security/reset_user_password.md +++ b/doc/security/reset_user_password.md @@ -20,7 +20,7 @@ The user's new password must meet all [password requirements](../user/profile/us To reset a user's password in the UI: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Users**. +1. Select **Overview > Users**. 1. For the user whose password you want to update, select **Edit**. 1. In the **Password** area, type a password and password confirmation. 1. Select **Save changes**. diff --git a/doc/security/ssh_keys_restrictions.md b/doc/security/ssh_keys_restrictions.md index 91e65278e0f..465389eb1ca 100644 --- a/doc/security/ssh_keys_restrictions.md +++ b/doc/security/ssh_keys_restrictions.md @@ -20,8 +20,8 @@ GitLab allows you to restrict the allowed SSH key technology as well as specify the minimum key length for each technology: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General** . -1. Expand the **Visibility and access controls** section: +1. Select **Settings > General** . +1. Expand **Visibility and access controls**:  diff --git a/doc/security/two_factor_authentication.md b/doc/security/two_factor_authentication.md index f2c07241446..c7d6796a212 100644 --- a/doc/security/two_factor_authentication.md +++ b/doc/security/two_factor_authentication.md @@ -34,8 +34,8 @@ You can use the UI or the API to enforce 2FA for all users. ### Use the UI 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. -1. Expand the **Sign-in restrictions** section: +1. Select **Settings > General**. +1. Expand **Sign-in restrictions**: - Select **Enforce two-factor authentication** to enable this feature. - In **Two-factor grace period**, enter a number of hours. If you want to enforce 2FA on next sign-in attempt, enter `0`. diff --git a/doc/security/unlock_user.md b/doc/security/unlock_user.md index c7ed049620d..179fd5eae3e 100644 --- a/doc/security/unlock_user.md +++ b/doc/security/unlock_user.md @@ -38,7 +38,7 @@ If 2FA is enabled, users are locked after three failed sign-in attempts. Account ## Unlock a user from the Admin Area 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Users**. +1. Select **Overview > Users**. 1. Use the search bar to find the locked user. 1. From the **User administration** dropdown list, select **Unlock**. diff --git a/doc/security/user_email_confirmation.md b/doc/security/user_email_confirmation.md index 42edb77db0d..1863c6e21ba 100644 --- a/doc/security/user_email_confirmation.md +++ b/doc/security/user_email_confirmation.md @@ -11,7 +11,7 @@ the user signs up. When this setting is enabled, the user is unable to sign in u they confirm their email address. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **Sign-up restrictions** and look for the **Email confirmation settings** options. ## Confirmation token expiry diff --git a/doc/security/webhooks.md b/doc/security/webhooks.md index 745ef77864b..3f16f0f6a65 100644 --- a/doc/security/webhooks.md +++ b/doc/security/webhooks.md @@ -50,7 +50,7 @@ To prevent exploitation of insecure internal web services, all webhook and integ To allow access to these addresses: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Network**. +1. Select **Settings > Network**. 1. Expand **Outbound requests**. 1. Select the **Allow requests to the local network from webhooks and integrations** checkbox. @@ -63,7 +63,7 @@ Prerequisites: [System hooks](../administration/system_hooks.md) can make requests to the local network by default. To prevent system hook requests to the local network: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Network**. +1. Select **Settings > Network**. 1. Expand **Outbound requests**. 1. Clear the **Allow requests to the local network from system hooks** checkbox. @@ -78,7 +78,7 @@ Prerequisites: To filter requests by blocking many requests: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Network**. +1. Select **Settings > Network**. 1. Expand **Outbound requests**. 1. Select the **Block all requests, except for IP addresses, IP ranges, and domain names defined in the allowlist** checkbox. @@ -103,7 +103,7 @@ Prerequisites: To allow outbound requests to certain IP addresses and domains: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > Network**. +1. Select **Settings > Network**. 1. Expand **Outbound requests**. 1. In **Local IP addresses and domain names that hooks and integrations can access**, enter your IP addresses and domains. diff --git a/doc/tutorials/automate_runner_creation/index.md b/doc/tutorials/automate_runner_creation/index.md index ef50dee7765..38261933d52 100644 --- a/doc/tutorials/automate_runner_creation/index.md +++ b/doc/tutorials/automate_runner_creation/index.md @@ -213,7 +213,7 @@ Now that you've automated your runner creation and automation, you can view the runners that use the same configuration in the GitLab UI. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **CI/CD > Runners**. +1. Select **CI/CD > Runners**. 1. In the search box, enter the runner description or search the list of runners. 1. To view the runners that use the same configuration, in the **Details** tab, next to **Runners**, select **Show details**. diff --git a/doc/tutorials/manage_user/index.md b/doc/tutorials/manage_user/index.md index 0f56e2b3bf7..836d1b71c1d 100644 --- a/doc/tutorials/manage_user/index.md +++ b/doc/tutorials/manage_user/index.md @@ -107,7 +107,7 @@ You will now manually create the users for your organization. These are test users. To create the first test user, Alex Smith: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Overview > Users**. +1. Select **Overview > Users**. 1. Select **New user**. 1. Complete the required fields: - **Name**: `Alex Smith` diff --git a/doc/user/group/index.md b/doc/user/group/index.md index 943d4137185..22fe60a8000 100644 --- a/doc/user/group/index.md +++ b/doc/user/group/index.md @@ -365,7 +365,7 @@ To change the role that can create projects under a group: 1. On the left sidebar, select **Search or go to** and find your group. 1. Select **Settings > General**. 1. Expand the **Permissions and group features** section. -1. From the **Roles allowed to create projects** dropdown list, select an option. +1. From **Roles allowed to create projects**, select an option. 1. Select **Save changes**. To change this setting globally, see [Default project creation protection](../../administration/settings/visibility_and_access_controls.md#define-which-roles-can-create-projects). diff --git a/doc/user/group/saml_sso/group_sync.md b/doc/user/group/saml_sso/group_sync.md index 1b5e8414ee7..144d927f7e5 100644 --- a/doc/user/group/saml_sso/group_sync.md +++ b/doc/user/group/saml_sso/group_sync.md @@ -214,7 +214,7 @@ To enable global group memberships lock: 1. [Configure SAML](../../../integration/saml.md) for your self-managed GitLab instance. 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand the **Visibility and access controls** section. 1. Ensure that **Lock memberships to SAML Group Links synchronization** is selected. diff --git a/doc/user/group/subgroups/index.md b/doc/user/group/subgroups/index.md index 672eefc079e..a63d4a98fa2 100644 --- a/doc/user/group/subgroups/index.md +++ b/doc/user/group/subgroups/index.md @@ -58,23 +58,25 @@ To view the subgroups of a group: 1. On the left sidebar, select **Search or go to** and find your group. 1. Select the **Subgroups and projects** tab. -1. To view a nested subgroup, expand a subgroup in the hierarchy list. +1. Select the subgroup you want to view. + To view nested subgroups, expand (**{chevron-down}**) a subgroup. ### Private subgroups in public parent groups -In the hierarchy list, public groups with a private subgroup have an expand option (**{chevron-down}**) -for all users that indicate there is a subgroup. When users who are not direct or inherited members of -the private subgroup select expand (**{chevron-down}**), the nested subgroup does not display. +In the hierarchy list, public groups with private subgroups have an expand option (**{chevron-down}**), +which indicates the group has nested subgroups. The expand option (**{chevron-down}**) is visible +to all users, but the private group is displayed only to users who are direct or inherited members +of the private subgroup. -If you prefer to keep information about the presence of nested subgroups private, we advise that you -add private subgroups only to private parent groups. +If you prefer to keep information about the presence of nested subgroups private, +you should add private subgroups only to private parent groups. ## Create a subgroup Prerequisites: - You must have either: - - At least the Maintainer role for a group to create subgroups for it. + - At least the Maintainer role for a group. - The [role determined by a setting](#change-who-can-create-subgroups). These users can create subgroups even if group creation is [disabled by an Administrator](../../../administration/admin_area.md#prevent-a-user-from-creating-top-level-groups) in the user's settings. @@ -84,11 +86,10 @@ You cannot host a GitLab Pages subgroup website with a top-level domain name. Fo To create a subgroup: -1. On the left sidebar, select **Search or go to** and find a parent group for the subgroup. +1. On the left sidebar, select **Search or go to** and find the group you want to create the subgroup in. 1. On the parent group's overview page, in the upper-right corner, select **New subgroup**. -1. Select **Create group**. 1. Fill in the fields. View a list of [reserved names](../../reserved_names.md) that cannot be used as group names. -1. Select **Create group**. +1. Select **Create subgroup**. ### Change who can create subgroups @@ -102,24 +103,21 @@ To change who can create subgroups on a group: 1. On the left sidebar, select **Search or go to** and find your group. 1. Select **Settings > General**. 1. Expand **Permissions and group features**. - 1. Select a role from **Roles allowed to create subgroups**. + 1. From **Roles allowed to create subgroups**, select an option. 1. Select **Save changes**. - As an administrator: 1. On the left sidebar, at the bottom, select **Admin Area**. - 1. On the left sidebar, select **Overview > Groups**. - 1. In the group's row select **Edit**. - 1. Select a role from **Allowed to create subgroups**. + 1. On the left sidebar, select **Overview > Groups** and find your group. + 1. In the group's row, select **Edit**. + 1. From the **Allowed to create subgroups** dropdown list, select an option. 1. Select **Save changes**. For more information, view the [permissions table](../../permissions.md#group-members-permissions). ## Subgroup membership -NOTE: -There is a bug that causes some pages in the parent group to be accessible by subgroup members. For more details, see [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/340421). - -When you add a member to a group, that member is also added to all subgroups. The user's permissions are inherited from -the group's parent. +When you add a member to a group, that member is also added to all subgroups of that group. +The member's permissions are inherited from the group's parent. Subgroup members can be: @@ -162,6 +160,7 @@ To see if a member has inherited the permissions from a parent group: 1. On the left sidebar, select **Search or go to** and find your group. 1. Select **Manage > Members**. + The member's inheritance is displayed in the **Source** column. Members list for an example subgroup _Four_: @@ -188,22 +187,23 @@ Members can be [filtered by inherited or direct membership](../index.md#filter-a ### Override ancestor group membership -Users with the Owner role on a subgroup can add members to it. +Users with the Owner role in a subgroup can add members to it. -You can't give a user a role on a subgroup that's lower than the roles they have on ancestor groups. To override a user's -role on an ancestor group, add the user to the subgroup again with a higher role. For example: +You can't give a user a role in a subgroup that is lower than the roles the user has in ancestor groups. +To override a user's role in an ancestor group, add the user to the subgroup again with a higher role. +For example: -- If User 1 is added to group _Two_ with the Developer role, they inherit that role in every subgroup of group _Two_. -- To give User 1 the Maintainer role on group _Four_ (under _One / Two / Three_), add them again to group _Four_ with +- If User 1 is added to group _Two_ with the Developer role, User 1 inherits that role in every subgroup of group _Two_. +- To give User 1 the Maintainer role in group _Four_ (under _One / Two / Three_), add User 1 again to group _Four_ with the Maintainer role. -- If User 1 is removed from group _Four_, their role falls back to their role on group _Two_. They have the Developer - role on group _Four_ again. +- If User 1 is removed from group _Four_, the user's role falls back to their role in group _Two_. User 1 has the Developer + role in group _Four_ again. ## Mention subgroups Mentioning subgroups ([`@<subgroup_name>`](../../discussions/index.md#mentions)) in issues, commits, and merge requests -notifies all direct members of that group. Inherited members of a subgroup are not notified by mentions. Mentioning works the same as for projects and groups, and you can choose the group -of people to be notified. +notifies all direct members of that group. Inherited members of a subgroup are not notified by mentions. +Mentioning works the same as for projects and groups, and you can choose the group of members to be notified. <!-- ## Troubleshooting diff --git a/doc/user/img/enable_AI_ML_features.png b/doc/user/img/enable_AI_ML_features.png Binary files differdeleted file mode 100644 index 97d06c877e4..00000000000 --- a/doc/user/img/enable_AI_ML_features.png +++ /dev/null diff --git a/doc/user/infrastructure/clusters/connect/index.md b/doc/user/infrastructure/clusters/connect/index.md index e56ec2b2af2..4a8ec3d85f7 100644 --- a/doc/user/infrastructure/clusters/connect/index.md +++ b/doc/user/infrastructure/clusters/connect/index.md @@ -45,7 +45,7 @@ your cluster's level. **Instance-level clusters:** 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Kubernetes**. +1. Select **Kubernetes**. ## Security implications for clusters connected with certificates 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 b7b382afc21..614639c705f 100644 --- a/doc/user/packages/container_registry/reduce_container_registry_storage.md +++ b/doc/user/packages/container_registry/reduce_container_registry_storage.md @@ -282,7 +282,7 @@ For self-managed instances, those settings can be updated in the [Rails console] They are also available in the [administrator area](../../../administration/admin_area.md): 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > CI/CD** +1. Select **Settings > CI/CD** 1. Expand **Container Registry**. ### Use the cleanup policy API diff --git a/doc/user/project/integrations/slack.md b/doc/user/project/integrations/slack.md index 91e21da6807..9b92fa35e24 100644 --- a/doc/user/project/integrations/slack.md +++ b/doc/user/project/integrations/slack.md @@ -11,8 +11,6 @@ WARNING: This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/372411) in GitLab 15.9 and is planned for removal in 17.0. Use the [GitLab for Slack app](gitlab_slack_application.md) instead. This change is a breaking change. -For the planned support of the GitLab for Slack app for self-managed instances, -see [epic 1211](https://gitlab.com/groups/gitlab-org/-/epics/1211). The Slack notifications integration enables your GitLab project to send events (such as issue creation) to your existing Slack team as notifications. Setting up diff --git a/doc/user/project/repository/code_suggestions/self_managed.md b/doc/user/project/repository/code_suggestions/self_managed.md index a1022c52e81..2bd798ea842 100644 --- a/doc/user/project/repository/code_suggestions/self_managed.md +++ b/doc/user/project/repository/code_suggestions/self_managed.md @@ -47,7 +47,7 @@ Prerequisites: To enable Code Suggestions for your self-managed GitLab instance: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **Code Suggestions** and select **Turn on Code Suggestions for this instance**. In GitLab 16.3, you do not need to enter anything into the **Personal access token** field. In GitLab 16.4 and later, there is no **Personal access token** field. @@ -95,7 +95,7 @@ To enable Code Suggestions for your GitLab SaaS account: To enable Code Suggestions for your self-managed GitLab instance: 1. On the left sidebar, at the bottom, select **Admin Area**. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **Code Suggestions** and: - Select **Turn on Code Suggestions for this instance**. - In **Personal access token**, enter your GitLab SaaS personal access token. diff --git a/doc/user/workspace/gitlab_agent_configuration.md b/doc/user/workspace/gitlab_agent_configuration.md index 856b39814fa..0e35c72c5ef 100644 --- a/doc/user/workspace/gitlab_agent_configuration.md +++ b/doc/user/workspace/gitlab_agent_configuration.md @@ -11,12 +11,12 @@ info: To determine the technical writer assigned to the Stage/Group associated w > - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136744) in GitLab 16.7. Feature flag `remote_development_feature_flag` removed. When you [set up a workspace](configuration.md#set-up-a-workspace), -you must configure remote development for the GitLab agent. +you must configure the GitLab agent for remote development. The remote development settings are available in the agent configuration file under `remote_development`. You can use any agent defined under the root group of your project, -provided that remote development is properly configured for that agent. +provided that the agent is properly configured for remote development. ## Remote development settings @@ -116,7 +116,7 @@ Use this setting to define a list of IP CIDR ranges to allow as egress destinati Define egress rules when: - The GitLab instance is on a private IP range. -- Workspace users must access a cloud resource on a private IP range. +- The workspace must access a cloud resource on a private IP range. Each element of the list defines an `allow` attribute with an optional `except` attribute. `allow` defines an IP range to allow traffic from. |
