Document how to enable Auto DevOps at the instance level

doc/user/admin_area/settings/continuous_integration.md

-# Continuous integration Admin settings
+# Continuous Integration and Deployment Admin settings **[CORE ONLY]**
 
-## Maximum artifacts size
+In this area, you will find settings for Auto DevOps, Runners and job artifacts.
+You can find it in the admin area, under **Settings > Continuous Integration and Deployment**.
 
-The maximum size of the [job artifacts][art-yml] can be set in the Admin area
-of your GitLab instance. The value is in *MB* and the default is 100MB. Note
-that this setting is set for each job.
+![Admin area settings button](../img/admin_area_settings_button.png)
 
-1. Go to the **Admin area ➔ Settings** (`/admin/application_settings`).
+## Auto DevOps **[CORE ONLY]**
 
-    ![Admin area settings button](img/admin_area_settings_button.png)
+To enable (or disable) [Auto DevOps](../../../topics/autodevops/index.md)
+for all projects:
 
-1. Change the value of maximum artifacts size (in MB):
+1. Go to **Admin area > Settings > Continuous Integration and Deployment**
+1. Check (or uncheck to disable) the box that says "Default to Auto DevOps pipeline for all projects"
+1. Optionally, set up the [Auto DevOps base domain](../../../topics/autodevops/index.md#auto-devops-base-domain)
+   which is going to be used for Auto Deploy and Auto Review Apps.
+1. Hit **Save changes** for the changes to take effect.
 
-    ![Admin area maximum artifacts size](img/admin_area_maximum_artifacts_size.png)
+From now on, every existing project and newly created ones that don't have a
+`.gitlab-ci.yml`, will use the Auto DevOps pipelines.
 
-1. Hit **Save** for the changes to take effect.
+If you want to disable it for a specific project, you can do so in
+[its settings](../../../topics/autodevops/index.md#enabling-auto-devops).
 
-## Default artifacts expiration
+## Maximum artifacts size **[CORE ONLY]**
 
-The default expiration time of the [job artifacts][art-yml] can be set in
-the Admin area of your GitLab instance. The syntax of duration is described
-in [artifacts:expire_in][duration-syntax]. The default is `30 days`. Note that
-this setting is set for each job. Set it to `0` if you don't want default
-expiration. The default unit is in seconds.
+The maximum size of the [job artifacts](../../../administration/job_artifacts.md)
+can be set in the Admin area of your GitLab instance. The value is in *MB* and
+the default is 100MB per job; on GitLab.com it's [set to 1G](../../gitlab_com/index.md#gitlab-ci-cd).
 
+To change it:
 
-1. Go to **Admin area > Settings** (`/admin/application_settings`).
+1. Go to **Admin area > Settings > Continuous Integration and Deployment**.
+1. Change the value of maximum artifacts size (in MB).
+1. Hit **Save changes** for the changes to take effect.
 
-    ![Admin area settings button](img/admin_area_settings_button.png)
+## Default artifacts expiration **[CORE ONLY]**
 
-1. Change the value of default expiration time ([syntax][duration-syntax]):
+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
+described in [`artifacts:expire_in`](../../../ci/yaml/README.md#artifacts-expire_in)
+and the default value is `30 days`. On GitLab.com they
+[never expire](../../gitlab_com/index.md#gitlab-ci-cd).
 
-    ![Admin area default artifacts expiration](img/admin_area_default_artifacts_expiration.png)
+1. Go to **Admin area > Settings > Continuous Integration and Deployment**.
+1. Change the value of default expiration time.
+1. Hit **Save changes** for the changes to take effect.
 
-1. Hit **Save** for the changes to take effect.
+This setting is set per job and can be overridden in
+[`.gitlab-ci.yml`](../../../ci/yaml/README.md#artifacts-expire_in).
+To disable the expiration, set it to `0`. The default unit is in seconds.
 
-[art-yml]: ../../../administration/job_artifacts.md
-[duration-syntax]: ../../../ci/yaml/README.md#artifacts-expire_in
+## Shared Runners pipeline minutes quota **[STARTER ONLY]**
 
-## Shared Runners pipeline minutes quota
-
-> [Introduced][ee-1078] in GitLab Enterprise Edition 8.16.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1078)
+in GitLab Starter 8.16.
 
 If you have enabled shared Runners for your GitLab instance, you can limit their
 usage by setting a maximum number of pipeline minutes that a group can use on
-shared Runners per month. Set 0 to grant unlimited pipeline minutes.
-While build limits are stored as minutes, the counting is done in seconds.
-Usage resets on the first day of each month.
-
-1. Go to the **Admin area ➔ Settings** (`/admin/application_settings`).
-
-    ![Admin area settings button](img/admin_area_settings_button.png)
+shared Runners per month. Setting this to `0` (default value) will grant
+unlimited pipeline minutes. While build limits are stored as minutes, the
+counting is done in seconds. Usage resets on the first day of each month.
+On GitLab.com, the quota is calculated based on your
+[subscription plan](https://about.gitlab.com/pricing/#gitlab-com).
 
-1. Navigate to the **Continuous Integration** block and enable the Shared
-   Runners setting. Then set the pipeline minutes quota limit.
+To change the pipelines minutes quota:
 
-    ![Shared Runners pipeline minutes quota](img/ci_shared_runners_build_minutes_quota.png)
-
-1. Hit **Save** for the changes to take effect.
+1. Go to **Admin area > Settings > Continuous Integration and Deployment**
+1. Set the pipeline minutes quota limit.
+1. Hit **Save changes** for the changes to take effect
 
 ---
 
@@ -66,18 +76,10 @@ also change each group's pipeline minutes quota to override the global value.
 
 1. Navigate to the **Groups** admin area and hit the **Edit** button for the
    group you wish to change the pipeline minutes quota.
-
-    ![Groups in the admin area](img/admin_area_groups.png)
-
-1. Set the pipeline minutes quota to the desired value and hit **Save changes** for
-   the changes to take effect.
-
-    ![Edit group in the admin area](img/admin_area_group_edit.png)
+1. Set the pipeline minutes quota to the desired value
+1. Hit **Save changes** for the changes to take effect.
 
 Once saved, you can see the build quota in the group admin view.
-
-![Group admin info](img/group_quota_view.png)
-
 The quota can also be viewed in the project admin view if shared Runners
 are enabled.
 
@@ -85,13 +87,7 @@ are enabled.
 
 When the pipeline minutes quota for a group is set to a value different than 0,
 the **Pipelines quota** page is available to the group page settings list.
-
-![Group settings](img/group_settings.png)
-
 You can see there an overview of the pipeline minutes quota of all projects of
 the group.
 
 ![Group pipelines quota](img/group_pipelines_quota.png)
-
-[art-yml]: ../../../administration/job_artifacts.md
-[ee-1078]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1078

doc/user/admin_area/settings/index.md

+# Admin area settings **[CORE ONLY]**
+
+In the admin area settings, you can find various options for your GitLab
+instance like sign-up restrictions, account limits and quota, metrics, etc.
+
+Navigate to it by going to **Admin area > Settings**. Some of the settings
+include:
+
+- [Continuous Integration and Deployment](continuous_integration.md)
+- [Email](email.md)
+- [Sign up restrictions](sign_up_restrictions.md)
+- [Terms](terms.md)
+- [Third party offers](third_party_offers.md)
+- [Usage statistics](usage_statistics.md)
+- [Visibility and access controls](visibility_and_access_controls.md)
+
+## GitLab.com admin area settings
+
+Most of the settings under the admin area change the behavior of the whole
+GitLab instance. For GitLab.com, the admin settings are available only for the
+GitLab.com administrators, and the parameters can be found on the
+[GitLab.com settings](../../gitlab_com/index.md) documentation.