Merge branch 'docs-repo-merge-10-group-misc-ee' into 'master'

Docs: (EE Port) Merge EE doc/​user/group to CE

See merge request gitlab-org/gitlab-ee!11639

doc/user/group/clusters/index.md

@@ -111,7 +111,7 @@ The domain should have a wildcard DNS configured to the Ingress IP address.
 When adding more than one Kubernetes cluster to your project, you need to differentiate
 them with an environment scope. The environment scope associates clusters with
 [environments](../../../ci/environments.md) similar to how the
-[environment-specific variables](../../../ci/variables/README.md#limiting-environment-scopes-of-environment-variables-premium)
+[environment-specific variables](https://docs.gitlab.com/ee/ci/variables/#limiting-environment-scopes-of-environment-variables-premium)
 work.
 
 While evaluating which environment matches the environment scope of a

doc/user/group/index.md

@@ -304,7 +304,7 @@ level of members in the group.
 Member lock lets a group owner lock down any new project membership to all the
 projects within the group, allowing tighter control over project membership.
 
-For instance, if you want to lock the group for an [Audit Event](../../administration/audit_events.md),
+For instance, if you want to lock the group for an [Audit Event](https://docs.gitlab.com/ee/administration/audit_events.html),
 you enable Member lock to guarantee that membership of a project cannot be modified during that audit.
 
 To enable this feature:
@@ -323,7 +323,7 @@ request to add a new user to a project through API will not be possible.
 
 Group file templates allow you to share a set of templates for common file
 types with every project in a group. It is analogous to the
-[instance template repository](../admin_area/settings/instance_template_repository.md)
+[instance template repository](https://docs.gitlab.com/ee/user/admin_area/settings/instance_template_repository.html)
 feature, and the selected project should follow the same naming conventions as
 are documented on that page.
 
@@ -354,7 +354,7 @@ Define project templates at a group-level by setting a group as a template sourc
   access each project's settings, and remove any project from the same screen.
 - **Webhooks**: configure [webhooks](../project/integrations/webhooks.md) to your group.
 - **Kubernetes cluster integration**: connect your GitLab group with [Kubernetes clusters](clusters/index.md).
-- **Audit Events**: view [Audit Events](https://docs.gitlab.com/ee/administration/audit_events.html#audit-events)
+- **Audit Events**: view [Audit Events](https://docs.gitlab.com/ee/administration/audit_events.html)
   for the group. **[STARTER ONLY]**
 - **Pipelines quota**: keep track of the [pipeline quota](../admin_area/settings/continuous_integration.md) for the group.
 

doc/user/group/insights/index.md

@@ -24,7 +24,7 @@ If no configuration was set, a [default configuration file](
 https://gitlab.com/gitlab-org/gitlab-ee/blob/master/ee/fixtures/insights/ee/fixtures/insights/default.yml)
 will be used.
 
-See the [Project's Insights documentation](../../project/insights/index.md) for
+See the [Project's Insights documentation](https://docs.gitlab.com/ee/user/project/insights/index.html) for
 more details about the `.gitlab/insights.yml` configuration file.
 
 ## Permissions

doc/user/group/issues_analytics/index.md

-# Issues Analytics
+# Issues Analytics **[PREMIUM]**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/7478) in [GitLab Premium](https://about.gitlab.com/pricing/) 11.5.
 

doc/user/group/saml_sso/scim_setup.md

-# SCIM provisioning using SAML SSO for Groups
+# SCIM provisioning using SAML SSO for Groups **[SILVER ONLY]**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/9388) in [GitLab.com Silver](https://about.gitlab.com/pricing/) 11.10.
 
-GitLab's [SCIM API](../../../api/scim.md) implements part of [the RFC7644 protocol](https://tools.ietf.org/html/rfc7644).
+GitLab's [SCIM API](https://docs.gitlab.com/ee/api/scim.html) implements part of [the RFC7644 protocol](https://tools.ietf.org/html/rfc7644).
 
 Currently, the following actions are available:
 

doc/user/group/security_dashboard/index.md

 ---
-redirect_to: '../../application_security/security_dashboard/index.md'
+redirect_to: 'https://docs.gitlab.com/ee/user/application_security/security_dashboard/index.html'
 ---
 
-This document was moved to [another location](../../application_security/security_dashboard/index.md).
+This document was moved to [another location](https://docs.gitlab.com/ee/user/application_security/security_dashboard/index.html).