Merge branch 'docs-add-badges-ee' into 'master'

Docs: add product badges to docs

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

doc/README.md

@@ -42,17 +42,18 @@ coordinate, and track your progress your way with GitLab’s flexible project
 management tools.
 
 - Chat operations
+  - [GitLab ChatOps](ci/chatops/README.md) **[ULTIMATE]**
   - [Mattermost slash commands](user/project/integrations/mattermost_slash_commands.md)
   - [Slack slash commands](user/project/integrations/slack_slash_commands.md)
 - [Discussions](user/discussions/index.md): Threads, comments, and resolvable discussions in issues, commits, and  merge requests.
 - [Issues](user/project/issues/index.md)
 - [Project Issue Boards](user/project/issue_board.md)
 - [Group Issue Boards](user/project/issue_board.md#group-issue-boards)
-- **(Starter/Premium/Ultimate)** [Related Issues](user/project/issues/related_issues.md): create a relationship between issues
+- [Related Issues](user/project/issues/related_issues.md): create a relationship between issues.**[STARTER]**
 - [Issues and merge requests templates](user/project/description_templates.md): Create templates for submitting new issues and merge requests.
 - [Labels](user/project/labels.md): Categorize your issues or merge requests based on descriptive titles.
 - [Milestones](user/project/milestones/index.md): Organize issues and merge requests into a cohesive group, optionally setting a due date.
-  - **(Starter/Premium/Ultimate)** [Burndown Charts](user/project/milestones/burndown_charts.md): Watch your project's progress throughout a specific milestone.
+  - [Burndown Charts](user/project/milestones/burndown_charts.md): Watch your project's progress throughout a specific milestone. **[STARTER]**
 - [Todos](workflow/todos.md): A chronological list of to-dos that are waiting for your input, all in a simple dashboard.
 - [GitLab Quick Actions](user/project/quick_actions.md): Textual shortcuts for common actions on issues or merge requests that are usually done by clicking buttons or dropdowns in GitLab's UI.
 
@@ -80,15 +81,15 @@ on projects and code.
   - [GitLab Pages](user/project/pages/index.md): Build, test, and deploy your static website with GitLab Pages.
 - [Groups](user/group/index.md): Organize your projects in groups.
   - [Subgroups](user/group/subgroups/index.md)
-  - **(Ultimate)** [Epics](user/group/epics/index.md)
-  - **(Ultimate)** [Roadmap](user/group/roadmap/index.md)
-  - **(Starter/Premium/Ultimate)** [Contribution Analytics](user/group/contribution_analytics/index.md): See detailed statistics of group contributors.
+  - [Epics](user/group/epics/index.md) **[ULTIMATE]**
+  - [Roadmap](user/group/roadmap/index.md) **[ULTIMATE]**
+  - [Contribution Analytics](user/group/contribution_analytics/index.md): See detailed statistics of group contributors. **[STARTER]**
 - [Search through GitLab](user/search/index.md): Search for issues, merge requests, projects, groups, todos, and issues in Issue Boards.
-  - **(Starter/Premium/Ultimate)** [Advanced Global Search](user/search/advanced_global_search.md): Leverage Elasticsearch for faster, more advanced code search across your entire GitLab instance.
-  - **(Starter/Premium/Ultimate)** [Advanced Syntax Search](user/search/advanced_search_syntax.md): Use advanced queries for more targeted search results.
+  - [Advanced Global Search](user/search/advanced_global_search.md): Leverage Elasticsearch for faster, more advanced code search across your entire GitLab instance. **[STARTER]**
+  - [Advanced Syntax Search](user/search/advanced_search_syntax.md): Use advanced queries for more targeted search results. **[STARTER]**
 - [Snippets](user/snippets.md): Snippets allow you to create little bits of code.
 - [Wikis](user/project/wiki/index.md): Enhance your repository documentation with built-in wikis.
-- **(Premium/Ultimate)** [GitLab Service Desk](user/project/service_desk.md): A simple way to allow people to create issues in your GitLab instance without needing their own user account.
+- [GitLab Service Desk](user/project/service_desk.md): A simple way to allow people to create issues in your GitLab instance without needing their own user account. **[PREMIUM]**
 - [Web IDE](user/project/web_ide/index.md)
 
 #### Repositories
@@ -101,7 +102,7 @@ Manage your [repositories](user/project/repository/index.md) from the UI (user i
   - [File templates](user/project/repository/web_editor.md#template-dropdowns)
   - [Create a directory](user/project/repository/web_editor.md#create-a-directory)
   - [Start a merge request](user/project/repository/web_editor.md#tips) (when committing via UI)
-  - **(Premium/Ultimate)** [File locking](user/project/file_lock.md): Lock a file to avoid merge conflicts.
+  - [File locking](user/project/file_lock.md): Lock a file to avoid merge conflicts. **[PREMIUM]**
 - [Branches](user/project/repository/branches/index.md)
   - [Default branch](user/project/repository/branches/index.md#default-branch)
   - [Create a branch](user/project/repository/web_editor.md#create-a-new-branch)
@@ -109,15 +110,15 @@ Manage your [repositories](user/project/repository/index.md) from the UI (user i
   - [Delete merged branches](user/project/repository/branches/index.md#delete-merged-branches)
 - [Commits](user/project/repository/index.md#commits)
   - [Signing commits](user/project/repository/gpg_signed_commits/index.md): use GPG to sign your commits.
-- **(Starter/Premium/Ultimate)** [Repository Mirroring](workflow/repository_mirroring.md)
-- **(Starter/Premium/Ultimate)** [Push rules](push_rules/push_rules.md): Additional control over pushes to your project.
+- [Repository Mirroring](workflow/repository_mirroring.md) **[STARTER]**
+- [Push rules](push_rules/push_rules.md): Additional control over pushes to your project. **[STARTER]**
 
 #### Integrations
 
 - [Project Services](user/project/integrations/project_services.md): Integrate a project with external services, such as CI and chat.
 - [GitLab Integration](integration/README.md): Integrate with multiple third-party services with GitLab to allow external issue trackers and external authentication.
-- [Trello Power-Up](integration/trello_power_up.md): Integrate with GitLab's Trello Power-Up
-- **(Premium/Ultimate)** [JIRA Development Panel](integration/jira_development_panel.md): See GitLab information in the JIRA Development Panel
+- [Trello Power-Up](integration/trello_power_up.md): Integrate with GitLab's Trello Power-Up.
+- [JIRA Development Panel](integration/jira_development_panel.md): See GitLab information in the JIRA Development Panel. **[PREMIUM]**
 
 #### Automation
 
@@ -135,8 +136,8 @@ auto scales to run your tests faster.
 - [Merge Requests](user/project/merge_requests/index.md)
   - [Work In Progress Merge Requests](user/project/merge_requests/work_in_progress_merge_requests.md)
   - [Merge Request discussion resolution](user/discussions/index.md#moving-a-single-discussion-to-a-new-issue): Resolve discussions, move discussions in a merge request to an issue, only allow merge requests to be merged if all discussions are resolved.
-  - **(Starter/Premium/Ultimate)** [Merge Request approval](user/project/merge_requests/merge_request_approvals.md): Make sure every merge request is approved by one or more people before getting merged.
-  - **(Ultimate)** [Static Application Security Testing](user/project/merge_requests/sast.md): Scan your code for vulnerabilities and display the results in merge requests.
+  - [Merge Request approval](user/project/merge_requests/merge_request_approvals.md): Make sure every merge request is approved by one or more people before getting merged. **[STARTER]**
+  - [Static Application Security Testing](user/project/merge_requests/sast.md): Scan your code for vulnerabilities and display the results in merge requests. **[ULTIMATE]**
   - [Checkout merge requests locally](user/project/merge_requests/index.md#checkout-merge-requests-locally)
   - [Cherry-pick](user/project/merge_requests/cherry_pick_changes.md)
 - [Review Apps](ci/review_apps/index.md): Preview changes to your app right from a merge request.
@@ -158,8 +159,8 @@ confidently and securely with GitLab’s built-in Continuous Delivery and Deploy
 
 - [GitLab Pages](user/project/pages/index.md): Build, test, and deploy a static site directly from GitLab.
 - [Auto Deploy](topics/autodevops/index.md#auto-deploy): Configure GitLab CI/CD for the deployment of your application.
-- **(Premium/Ultimate)** [Deploy Boards](user/project/deploy_boards.md): View of the current health and status of each CI environment running on Kubernetes, displaying the status of the pods in the deployment.
-- **(Premium/Ultimate)** [Canary Deployments](user/project/canary_deployments.md): A popular CI strategy, where a small portion of the fleet is updated to the new version first.
+- [Deploy Boards](user/project/deploy_boards.md): View of the current health and status of each CI environment running on Kubernetes, displaying the status of the pods in the deployment. **[PREMIUM]**
+- [Canary Deployments](user/project/canary_deployments.md): A popular CI strategy, where a small portion of the fleet is updated to the new version first. **[PREMIUM]**
 - [Environments and deployments](ci/environments.md): With environments, you can control the continuous deployment of your software within GitLab.
 
 ### Configure

doc/administration/audit_events.md

@@ -2,9 +2,7 @@
 last_updated: 2017-12-13
 ---
 
-# Audit Events
-
-> Available in [GitLab Enterprise Editions][ee].
+# Audit Events **[STARTER ONLY]**
 
 GitLab Enterprise Edition offers a way to view the changes made within the
 GitLab server as a help to system administrators.
@@ -37,8 +35,6 @@ There are two kinds of events logged:
 
 ### Group events
 
-> Available in [GitLab Starter][ee].
-
 NOTE: **Note:**
 You need Owner [permissions] to view the group Audit Events page.
 
@@ -58,8 +54,6 @@ From there, you can see the following actions:
 
 ### Project events
 
-> Available in [GitLab Starter][ee].
-
 NOTE: **Note:**
 You need Master [permissions] or higher to view the project Audit Events page.
 
@@ -73,10 +67,9 @@ From there, you can see the following actions:
 - Permission changes of a user assigned to a project
 - User was removed from project
 
-### Instance events
+### Instance events **[PREMIUM ONLY]**
 
 > [Introduced][ee-2336] in [GitLab Premium][ee] 9.3.
-Available only for GitLab administrators.
 
 Server-wide audit logging introduces the ability to observe user actions across
 the entire instance of your GitLab server, making it easy to understand who

doc/administration/auditor_users.md

-# Auditor users
+# Auditor users **[PREMIUM ONLY]**
 
 >[Introduced][ee-998] in [GitLab Premium][eep] 8.17.
 

doc/administration/auth/README.md

@@ -9,7 +9,7 @@ providers.
 
 - [LDAP](ldap.md) Includes Active Directory, Apple Open Directory, Open LDAP,
   and 389 Server
-  - **(Starter/Premium)** [LDAP for GitLab EE](ldap-ee.md): LDAP additions to GitLab Enterprise Editions
+  - [LDAP for GitLab EE](ldap-ee.md): LDAP additions to GitLab Enterprise Editions **[STARTER ONLY]**
 - [OmniAuth](../../integration/omniauth.md) Sign in via Twitter, GitHub, GitLab.com, Google,
   Bitbucket, Facebook, Shibboleth, Crowd, Azure and Authentiq ID
 - [CAS](../../integration/cas.md) Configure GitLab to sign in using CAS

doc/administration/auth/ldap-ee.md

-# LDAP Additions in GitLab EE
+# LDAP Additions in GitLab EE **[STARTER ONLY]**
 
 This is a continuation of the main [LDAP documentation](ldap.md), detailing LDAP
 features specific to GitLab Enterprise Edition.
@@ -47,7 +47,7 @@ The process will also update the following user information:
 > **Note:** The LDAP sync process updates existing users while new users will
   be created on first sign in.
 
-## Group Sync
+## Group Sync **[PREMIUM ONLY]**
 
 If your LDAP supports the `memberof` property, GitLab will add the user to any
 new groups they might be added to when the user logs in. That way they don't need

doc/administration/database_load_balancing.md

-# Database Load Balancing
+# Database Load Balancing **[PREMIUM ONLY]**
 
 > [Introduced][ee-1283] in [GitLab Premium][eep] 9.0.
 

doc/administration/geo/disaster_recovery/index.md

-# Disaster Recovery
+# Disaster Recovery **[PREMIUM ONLY]**
 
 Geo replicates your database, your Git repositories, and few other assets.
 We will support and replicate more data in the future, that will enable you to

doc/administration/geo/replication/index.md

-# Geo (Geo Replication)
+# Geo (Geo Replication) **[PREMIUM ONLY]**
 
 > **Notes:**
 - Geo is part of [GitLab Premium][ee].

doc/administration/high_availability/consul.md

-# Working with the bundled Consul service
+# Working with the bundled Consul service **[PREMIUM ONLY]**
 
 ## Overview
 

doc/administration/high_availability/database.md

-# Configuring a Database for GitLab HA
+# Configuring a Database for GitLab HA **[PREMIUM ONLY]**
 
 You can choose to install and manage a database server (PostgreSQL/MySQL)
 yourself, or you can use GitLab Omnibus packages to help. GitLab recommends

doc/administration/index.md

-# Administrator documentation
+# Administrator documentation **[CORE ONLY]**
 
 Learn how to administer your GitLab instance (Community Edition and
 Enterprise Edition).
@@ -25,14 +25,14 @@ Learn how to install, configure, update, and maintain your GitLab instance.
 ### Installing GitLab
 
 - [Install](../install/README.md): Requirements, directory structures, and installation methods.
-  - **(Starter/Premium)** [Database load balancing](database_load_balancing.md): Distribute database queries among multiple database servers.
-  - **(Starter/Premium)** [Omnibus support for external MySQL DB](https://docs.gitlab.com/omnibus/settings/database.html#using-a-mysql-database-management-server-enterprise-edition-only): Omnibus package supports configuring an external MySQL database.
-  - **(Starter/Premium)** [Omnibus support for log forwarding](https://docs.gitlab.com/omnibus/settings/logs.html#udp-log-shipping-gitlab-enterprise-edition-only)
+  - [Database load balancing](database_load_balancing.md): Distribute database queries among multiple database servers. **[STARTER ONLY]**
+  - [Omnibus support for external MySQL DB](https://docs.gitlab.com/omnibus/settings/database.html#using-a-mysql-database-management-server-enterprise-edition-only): Omnibus package supports configuring an external MySQL database. **[STARTER ONLY]**
+  - [Omnibus support for log forwarding](https://docs.gitlab.com/omnibus/settings/logs.html#udp-log-shipping-gitlab-enterprise-edition-only) **[STARTER ONLY]**
 - [High Availability](high_availability/README.md): Configure multiple servers for scaling or high availability.
   - [High Availability on AWS](../university/high-availability/aws/README.md): Set up GitLab HA on Amazon AWS.
-- **(Premium)** [Geo](geo/replication/index.md): Replicate your GitLab instance to other geographical locations as a read-only fully operational version.
-- **(Premium)** [Disaster Recovery](geo/disaster_recovery/index.md): Quickly fail-over to a different site with minimal effort in a disaster situation.
-- **(Premium)** [Pivotal Tile](../install/pivotal/index.md): Deploy GitLab as a pre-configured appliance using Ops Manager (BOSH) for Pivotal Cloud Foundry.
+- [Geo](geo/replication/index.md): Replicate your GitLab instance to other geographical locations as a read-only fully operational version. **[PREMIUM ONLY]**
+- [Disaster Recovery](geo/disaster_recovery/index.md): Quickly fail-over to a different site with minimal effort in a disaster situation. **[PREMIUM ONLY]**
+- [Pivotal Tile](../install/pivotal/index.md): Deploy GitLab as a pre-configured appliance using Ops Manager (BOSH) for Pivotal Cloud Foundry. **[PREMIUM ONLY]**
 
 ### Configuring GitLab
 
@@ -47,8 +47,8 @@ Learn how to install, configure, update, and maintain your GitLab instance.
 [source installations](../install/installation.md#installation-from-source).
 - [Environment variables](environment_variables.md): Supported environment variables that can be used to override their defaults values in order to configure GitLab.
 - [Plugins](plugins.md): With custom plugins, GitLab administrators can introduce custom integrations without modifying GitLab's source code.
-- **(Starter/Premium)** [Elasticsearch](../integration/elasticsearch.md): Enable Elasticsearch to empower GitLab's Advanced Global Search. Useful when you deal with a huge amount of data.
-- **(Premium)** [External Classification Policy Authorization](../user/admin_area/settings/external_authorization.md)
+- [Elasticsearch](../integration/elasticsearch.md): Enable Elasticsearch to empower GitLab's Advanced Global Search. Useful when you deal with a huge amount of data. **[STARTER ONLY]**
+- [External Classification Policy Authorization](../user/admin_area/settings/external_authorization.md) **[PREMIUM ONLY]**
 
 #### Customizing GitLab's appearance
 
@@ -90,12 +90,12 @@ created in snippets, wikis, and repos.
 - [Sign-up restrictions](../user/admin_area/settings/sign_up_restrictions.md): block email addresses of specific domains, or whitelist only specific domains.
 - [Access restrictions](../user/admin_area/settings/visibility_and_access_controls.md#enabled-git-access-protocols): Define which Git access protocols can be used to talk to GitLab (SSH, HTTP, HTTPS).
 - [Authentication/Authorization](../topics/authentication/index.md#gitlab-administrators): Enforce 2FA, configure external authentication with LDAP, SAML, CAS and additional Omniauth providers.
-  - **(Starter/Premium)** [Sync LDAP](auth/ldap-ee.md)
-  - **(Starter/Premium)** [Kerberos authentication](../integration/kerberos.md)
-- **(Starter/Premium)** [Email users](../tools/email.md): Email GitLab users from within GitLab.
+  - [Sync LDAP](auth/ldap-ee.md) **[STARTER ONLY]**
+  - [Kerberos authentication](../integration/kerberos.md) **[STARTER ONLY]**
+- [Email users](../tools/email.md): Email GitLab users from within GitLab. **[STARTER ONLY]**
 - [User Cohorts](../user/admin_area/user_cohorts.md): Display the monthly cohorts of new users and their activities over time.
-- **(Starter/Premium)** [Audit logs and events](audit_events.md): View the changes made within the GitLab server.
-- **(Premium)** [Auditor users](auditor_users.md): Users with read-only access to all projects, groups, and other resources on the GitLab instance.
+- [Audit logs and events](audit_events.md): View the changes made within the GitLab server. **[STARTER ONLY]**
+- [Auditor users](auditor_users.md): Users with read-only access to all projects, groups, and other resources on the GitLab instance. **[PREMIUM ONLY]**
 - [Incoming email](incoming_email.md): Configure incoming emails to allow
   users to [reply by email], create [issues by email] and
   [merge requests by email], and to enable [Service Desk].
@@ -123,7 +123,7 @@ created in snippets, wikis, and repos.
 - [Repository checks](repository_checks.md): Periodic Git repository checks.
 - [Repository storage paths](repository_storage_paths.md): Manage the paths used to store repositories.
 - [Repository storage rake tasks](raketasks/storage.md): A collection of rake tasks to list and migrate existing projects and attachments associated with it from Legacy storage to Hashed storage.
-- **(Starter/Premium)** [Limit repository size](../user/admin_area/settings/account_and_limit_settings.md): Set a hard limit for your repositories' size.
+- [Limit repository size](../user/admin_area/settings/account_and_limit_settings.md): Set a hard limit for your repositories' size. **[STARTER ONLY]**
 
 ## Continuous Integration settings
 

doc/administration/job_artifacts.md

@@ -91,8 +91,6 @@ _The artifacts are stored by default in
 - [Introduced][ee-1762] in [GitLab Premium][eep] 9.4.
 - Since version 9.5, artifacts are [browsable], when object storage is enabled. 
   9.4 lacks this feature.
-> Available in [GitLab Premium](https://about.gitlab.com/products/) and
-[GitLab.com Silver](https://about.gitlab.com/gitlab-com/).
 > Since version 10.6, available in [GitLab CE](https://about.gitlab.com/products/)
 
 If you don't want to use the local disk where GitLab is installed to store the

doc/administration/operations/index.md

@@ -13,6 +13,6 @@ by GitLab to another file system or another server.
 that to prioritize important jobs.
 - [Sidekiq MemoryKiller](sidekiq_memory_killer.md): Configure Sidekiq MemoryKiller
 to restart Sidekiq.
-- **(Starter/Premium)** [Extra Sidekiq operations](extra_sidekiq_processes.md): Configure an extra set of Sidekiq processes to ensure certain queues always have dedicated workers, no matter the amount of jobs that need to be processed.
+- [Extra Sidekiq operations](extra_sidekiq_processes.md): Configure an extra set of Sidekiq processes to ensure certain queues always have dedicated workers, no matter the amount of jobs that need to be processed. **[STARTER ONLY]**
 - [Unicorn](unicorn.md): Understand Unicorn and unicorn-worker-killer.
 - [Speed up SSH operations](fast_ssh_key_lookup.md): Authorize SSH users via a fast, indexed lookup to the GitLab database.

doc/administration/uploads.md

@@ -48,10 +48,10 @@ _The uploads are stored by default in
 
 1. Save the file and [restart GitLab][] for the changes to take effect.
 
-### Using object storage
+### Using object storage **[PREMIUM]**
 
 >**Notes:**
-- [Introduced][ee-3867] in [GitLab Enterprise Edition Premium][eep] 10.5.
+- [Introduced][ee-3867] in [GitLab Premium][eep] 10.5.
 
 If you don't want to use the local disk where GitLab is installed to store the
 uploads, you can use an object storage provider like AWS S3 instead.
@@ -206,5 +206,5 @@ _The uploads are stored by default in
 
 [reconfigure gitlab]: restart_gitlab.md#omnibus-gitlab-reconfigure "How to reconfigure Omnibus GitLab"
 [restart gitlab]: restart_gitlab.md#installations-from-source "How to restart GitLab"
-[eep]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition Premium"
+[eep]: https://about.gitlab.com/gitlab-ee/ "GitLab Premium"
 [ee-3867]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3867

doc/api/README.md

@@ -18,11 +18,11 @@ following locations:
 - [Deployments](deployments.md)
 - [Deploy Keys](deploy_keys.md)
 - [Environments](environments.md)
-- [Epics](epics.md)
-- [Epic Issues](epic_issues.md)
+- [Epics](epics.md) **[ULTIMATE]**
+- [Epic Issues](epic_issues.md) **[ULTIMATE]**
 - [Events](events.md)
 - [Feature flags](features.md)
-- [Geo Nodes](geo_nodes.md)
+- [Geo Nodes](geo_nodes.md) **[PREMIUM]**
 - [Gitignores templates](templates/gitignores.md)
 - [GitLab CI Config templates](templates/gitlab_ci_ymls.md)
 - [Groups](groups.md)
@@ -37,7 +37,7 @@ following locations:
 - [Labels](labels.md)
 - [License](license.md)
 - [Merge Requests](merge_requests.md)
-- [Merge Request Approvals](merge_request_approvals.md)
+- [Merge Request Approvals](merge_request_approvals.md) **[STARTER]**
 - [Project milestones](milestones.md)
 - [Group milestones](group_milestones.md)
 - [Namespaces](namespaces.md)

doc/api/boards.md

@@ -141,7 +141,7 @@ Example response:
   }
 ```
 
-## Create a board (Starter-Only)
+## Create a board **[STARTER]**
 
 Creates a board.
 
@@ -209,7 +209,7 @@ Example response:
   }
 ```
 
-## Delete a board (Starter-Only)
+## Delete a board **[STARTER]**
 
 Deletes a board.
 

doc/api/epic_issues.md

-# Epic Issues API
+# Epic Issues API **[ULTIMATE]**
 
 Every API call to epic_issues must be authenticated.
 

doc/api/epics.md

-# Epics API
+# Epics API **[ULTIMATE]**
 
 Every API call to epic must be authenticated.
 
 If a user is not a member of a group and the group is private, a `GET` request on that group will result to a `404` status code.
 
-Epics are available only in Ultimate. If epics feature is not available a `403` status code will be returned.
+If epics feature is not available a `403` status code will be returned.
 
 ## Epic issues API
 

doc/api/merge_request_approvals.md

-# Project-level approvals
+# Merge request approvals **[STARTER]**
 
-Configuration for approvals on all Merge Requests in the project. Must be authenticated for all endpoints.
+Configuration for approvals on all Merge Requests (MR) in the project. Must be authenticated for all endpoints.
 
-## Get Configuration
+## Project-level MR approvals
+
+### Get Configuration
 
 >**Note:** This API endpoint is only available on 10.6 Starter and above.
 
@@ -57,7 +59,7 @@ GET /projects/:id/approvals
 }
 ```
 
-## Change configuration
+### Change configuration
 
 >**Note:** This API endpoint is only available on 10.6 Starter and above.
 
@@ -115,7 +117,7 @@ POST /projects/:id/approvals
 }
 ```
 
-## Change allowed approvers
+### Change allowed approvers
 
 >**Note:** This API endpoint is only available on 10.6 Starter and above.
 
@@ -175,10 +177,11 @@ PUT /projects/:id/approvers
 ```
 
 
-# Merge Request-level Approvals
+## Merge Request-level MR approvals
+
 Configuration for approvals on a specific Merge Request. Must be authenticated for all endpoints.
 
-## Get Configuration
+### Get Configuration
 
 >**Note:** This API endpoint is only available on 8.9 Starter and above.
 
@@ -226,7 +229,7 @@ GET /projects/:id/merge_requests/:merge_request_iid/approvals
 }
 ```
 
-## Change approval configuration
+### Change approval configuration
 
 >**Note:** This API endpoint is only available on 10.6 Starter and above.
 
@@ -265,7 +268,7 @@ POST /projects/:id/merge_requests/:merge_request_iid/approvals
 }
 ```
 
-## Change allowed approvers for Merge Request
+### Change allowed approvers for Merge Request
 
 >**Note:** This API endpoint is only available on 10.6 Starter and above.
 

doc/api/projects.md

@@ -1407,10 +1407,7 @@ POST /projects/:id/housekeeping
 | --------- | ---- | -------- | ----------- |
 | `id` | integer/string | yes | The ID of the project or NAMESPACE/PROJECT_NAME |
 
-## Push Rules
-
->**Note:**
-Available in [GitLab Starter](https://about.gitlab.com/products).
+## Push Rules **[STARTER]**
 
 ### Get project push rules
 
@@ -1507,9 +1504,9 @@ Read more in the [Project import/export](project_import_export.md) documentation
 
 Read more in the [Project members](members.md) documentation.
 
-## Start the pull mirroring process for a Project
+## Start the pull mirroring process for a Project **[STARTER]**
 
-> Introduced in GitLab 10.3. **Note:** Available in [GitLab Starter](https://about.gitlab.com/products).
+> Introduced in [GitLab Starter](https://about.gitlab.com/products) 10.3.
 
 ```
 POST /projects/:id/mirror/pull

doc/ci/chatops/README.md

-# GitLab ChatOps
+# GitLab ChatOps **[ULTIMATE]**
 > **Notes:**
 
 > * [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4466) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 10.6.

doc/ci/ci_cd_for_external_repos/bitbucket_integration.md

-# Using GitLab CI/CD with a Bitbucket Cloud repository
+# Using GitLab CI/CD with a Bitbucket Cloud repository **[PREMIUM]**
 
 GitLab CI/CD can be used with Bitbucket Cloud by creating a
 [CI/CD project](../../user/project/ci_cd_for_external_repo.md) and connecting

doc/ci/ci_cd_for_external_repos/github_integration.md

-# Using GitLab CI/CD with a GitHub repository
+# Using GitLab CI/CD with a GitHub repository **[PREMIUM]**
 
 GitLab CI/CD can be used with **GitHub.com** and **GitHub Enterprise** by
 creating a [CI/CD project][cicd-projects] to connect your GitHub repository to

doc/ci/ci_cd_for_external_repos/index.md

-# GitLab CI/CD for external repositories
+# GitLab CI/CD for external repositories **[PREMIUM]**
 
 >[Introduced][ee-4642] in [GitLab Premium][eep] 10.6.
 
@@ -21,7 +21,6 @@ snippets disabled. These features
 
 ![CI/CD for external repository project creation](img/ci_cd_for_external_repo.png)
 
-
 [ee-4642]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4642
 [eep]: https://about.gitlab.com/products/
 [mirroring]: ../../workflow/repository_mirroring.md

doc/ci/examples/README.md

@@ -45,17 +45,17 @@ There's also a collection of repositories with [example projects](https://gitlab
 
 [Analyze code quality with the Code Climate CLI](code_climate.md).
 
-## Static Application Security Testing (SAST)
+## Static Application Security Testing (SAST) **[ULTIMATE]**
 
-**(Ultimate)** [Scan your code for vulnerabilities](sast.md)
+[Scan your code for vulnerabilities](sast.md)
 
-## Dependency Scanning
+## Dependency Scanning **[ULTIMATE]**
 
-**(Ultimate)** [Scan your dependencies for vulnerabilities](dependency_scanning.md)
+[Scan your dependencies for vulnerabilities](dependency_scanning.md)
 
-## Dependency Scanning
+## Dependency Scanning **[ULTIMATE]**
 
-**(Ultimate)** [Scan your dependencies for vulnerabilities](https://docs.gitlab.com/ee/ci/examples/dependency_scanning.html)
+[Scan your dependencies for vulnerabilities](https://docs.gitlab.com/ee/ci/examples/dependency_scanning.html)
 
 ## Container Scanning
 

doc/ci/examples/dependency_scanning.md

-# Dependency Scanning with GitLab CI/CD
-
-NOTE: **Note:**
-In order to use this tool, a [GitLab Ultimate][ee] license
-is needed.
+# Dependency Scanning with GitLab CI/CD **[ULTIMATE]**
 
 This example shows how to run Dependency Scanning on your
 project's dependencies by using GitLab CI/CD.

doc/ci/examples/sast.md

-# Static Application Security Testing with GitLab CI/CD
-
-NOTE: **Note:**
-In order to use this tool, a [GitLab Ultimate][ee] license
-is needed.
+# Static Application Security Testing with GitLab CI/CD **[ULTIMATE]**
 
 This example shows how to run
 [Static Application Security Testing (SAST)](https://en.wikipedia.org/wiki/Static_program_analysis)

doc/ci/multi_project_pipeline_graphs.md

-# Multi-project pipeline graphs
+# Multi-project pipeline graphs **[PREMIUM]**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/2121) in
 [GitLab Premium 9.3](https://about.gitlab.com/2017/06/22/gitlab-9-3-released/#multi-project-pipeline-graphs).

doc/ci/pipelines.md

@@ -206,13 +206,11 @@ by name. The order of severity is:
 
 ![Pipeline mini graph sorting](img/pipelines_mini_graph_sorting.png)
 
-### Multi-project pipelines graphs
+### Multi-project pipelines graphs **[PREMIUM]**
 
 With [multi-project pipeline graphs](multi_project_pipeline_graphs.md),
 you can visualize cross-project pipelines.
 
-It is available only in [GitLab Premium][eep].
-
 ## How the pipeline duration is calculated
 
 Total running time for a given pipeline would exclude retries and pending

doc/ci/triggers/README.md

@@ -21,7 +21,7 @@ A unique trigger token can be obtained when [adding a new trigger](#adding-a-new
 You can use the `CI_JOB_TOKEN` [variable][predef] (used to authenticate
 with the [GitLab Container Registry][registry]) in the following cases.
 
-#### When used with multi-project pipelines
+#### When used with multi-project pipelines **[PREMIUM]**
 
 > **Note**:
 The use of `CI_JOB_TOKEN` for multi-project pipelines was [introduced][ee-2017]
@@ -45,7 +45,7 @@ Pipelines triggered that way also expose a special variable:
 
 Read more about the [pipelines trigger API][trigapi].
 
-#### When a pipeline depends on the artifacts of another pipeline
+#### When a pipeline depends on the artifacts of another pipeline **[PREMIUM]**
 
 > **Note**:
 The use of `CI_JOB_TOKEN` in the artifacts download API was [introduced][ee-2346]

doc/ci/variables/README.md

@@ -202,7 +202,7 @@ Protected variables can be added by going to your project's
 
 Once you set them, they will be available for all subsequent pipelines.
 
-### Limiting environment scopes of secret variables
+### Limiting environment scopes of secret variables **[PREMIUM]**
 
 >**Notes:**
 [Introduced][ee-2112] in [GitLab Premium][premium] 9.4.

doc/ci/yaml/README.md

@@ -1197,7 +1197,7 @@ test:
   retry: 2
 ```
 
-## `include`
+## `include` **[STARTER]**
 
 > Introduced in [GitLab Edition Premium][ee] 10.5.
 > Available for Starter, Premium and Ultimate [versions][gitlab-versions] since 10.6.

doc/development/doc_styleguide.md

@@ -157,6 +157,39 @@ below.
 
     Otherwise, leave this mention out.
 
+### Product badges
+
+When a feature is available in EE-only tiers, add the corresponding tier according to the
+feature availability:
+
+- For GitLab Starter and GitLab.com Bronze: `**[STARTER]**`
+- For GitLab Premium and GitLab.com Silver: `**[PREMIUM]**`
+- For GitLab Ultimate and GitLab.com Gold: `**[ULTIMATE]**`
+- For GitLab Core and GitLab.com Free: `**[CORE]**`
+
+To exclude GitLab.com tiers (when the feature is not available in GitLab.com), add the
+keyword "only":
+
+- For GitLab Starter: `**[STARTER ONLY]**`
+- For GitLab Premium: `**[PREMIUM ONLY]**`
+- For GitLab Ultimate: `**[ULTIMATE ONLY]**`
+- For GitLab Core: `**[CORE ONLY]**`
+
+The tier should be ideally added to headers, so that the full badge will be displayed.
+But it can be also mentioned from paragraphs, list items, and table cells. For these cases,
+the tier mention will be represented by an orange question mark.
+E.g., `**[STARTER]**` renders **[STARTER]**, `**[STARTER ONLY]**` renders **[STARTER ONLY]**.
+
+The absence of tiers' mentions mean that the feature is available in GitLab Core,
+GitLab.com Free, and higher tiers.
+
+#### How it works
+
+Introduced by [!244](https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/244),
+the special markup `**[STARTER]**` will generate a `span` element to trigger the
+badges and tooltips (`<span class="badge-trigger starter">`). When the keyword
+"only" is added, the corresponding GitLab.com badge will not be displayed.
+
 ### GitLab Restart
 
 There are many cases that a restart/reconfigure of GitLab is required. To

doc/install/README.md

@@ -2,7 +2,7 @@
 comments: false
 ---
 
-# Installation
+# Installation **[CORE ONLY]**
 
 GitLab can be installed via various ways. Check the [installation methods][methods]
 for an overview.
@@ -37,7 +37,7 @@ the full process of installing GitLab on Google Container Engine (GKE), pushing
 - _Testing only!_ [DigitalOcean and Docker Machine](digitaloceandocker.md) -
   Quickly test any version of GitLab on DigitalOcean using Docker Machine.
 - [GitLab Pivotal Tile](pivotal/index.md) - Install and configure GitLab
-  Premium on Pivotal Cloud Foundry.
+  Premium on Pivotal Cloud Foundry. **[PREMIUM ONLY]**
 - [Getting started with GitLab and DigitalOcean](https://about.gitlab.com/2016/04/27/getting-started-with-gitlab-and-digitalocean/): requirements, installation process, updates.
 - [Demo: Cloud Native Development with GitLab](https://about.gitlab.com/2017/04/18/cloud-native-demo/): video demonstration on how to install GitLab on Kubernetes, build a project, create Review Apps, store Docker images in Container Registry, deploy to production on Kubernetes, and monitor with Prometheus.
 

doc/install/pivotal/index.md

-# GitLab Pivotal Tile
+# GitLab Pivotal Tile **[PREMIUM ONLY]**
 
 > Introduced in [GitLab Premium][eep] 8.2.
 

doc/integration/elasticsearch.md

-# Elasticsearch integration
+# Elasticsearch integration **[STARTER ONLY]**
 
 >
 [Introduced][ee-109] in GitLab [Starter][ee] 8.4. Support

doc/integration/jira_development_panel.md

-# GitLab JIRA Development Panel integration
+# GitLab JIRA Development Panel integration **[PREMIUM]**
 
 > [Introduced][ee-2381] in [GitLab Premium][eep] 10.0.
 

doc/integration/kerberos.md

-# Kerberos integration
-
->**Note:**
-Available in [GitLab Starter][ee].
+# Kerberos integration **[STARTER ONLY]**
 
 GitLab can integrate with [Kerberos][kerb] as an authentication mechanism.
 
@@ -24,7 +21,6 @@ following prerequisites. You still need to configure your system for
 Kerberos usage, such as specifying realms. GitLab will make use of the
 system's Kerberos settings.
 
-
 ### GitLab keytab
 
 1. Create a Kerberos Service Principal for the HTTP service on your GitLab server.

doc/integration/slash_commands.md

@@ -19,7 +19,7 @@ Taking the trigger term as `project-name`, the commands are:
 | `/project-name issue search <query>` | Shows up to 5 issues matching `<query>` |
 | `/project-name issue move <id> to <project>` | Moves issue ID `<id>` to `<project>` |
 | `/project-name deploy <from> to <to>` | Deploy from the `<from>` environment to the `<to>` environment |
-| `/project-name run <job name> <arguments>` | Execute [ChatOps](../ci/chatops/README.md) job `<job name>` on `master` (available in GitLab Ultimate only) |
+| `/project-name run <job name> <arguments>` | Execute [ChatOps](../ci/chatops/README.md) job `<job name>` on `master` **[ULTIMATE]** |
 
 Note that if you are using the [GitLab Slack application](https://docs.gitlab.com/ee/user/project/integrations/gitlab_slack_application.html) for
 your GitLab.com projects, you need to [add the `gitlab` keyword at the beginning of the command](https://docs.gitlab.com/ee/user/project/integrations/gitlab_slack_application.html#usage).

doc/push_rules/push_rules.md

-# Push Rules
-
-> Available in [GitLab Enterprise Editions][ee].
+# Push Rules **[STARTER]**
 
 Gain additional control over pushes to your repository.
 

doc/tools/email.md

-# Email from GitLab
-
->**Note:**
-Available in [GitLab Starter][ee].
+# Email from GitLab **[STARTER ONLY]**
 
 As a GitLab administrator you can email GitLab users from within GitLab.
 

doc/topics/autodevops/index.md

@@ -227,7 +227,7 @@ In GitLab Starter, differences between the source and
 target branches are also
 [shown in the merge request widget](../../user/project/merge_requests/code_quality_diff.md).
 
-### Auto SAST
+### Auto SAST **[ULTIMATE]**
 
 > Introduced in [GitLab Ultimate][ee] 10.3.
 
@@ -240,7 +240,7 @@ check out.
 In GitLab Ultimate, any security warnings are also
 [shown in the merge request widget](../../user/project/merge_requests/sast.md).
 
-### Auto Dependency Scanning
+### Auto Dependency Scanning **[ULTIMATE]**
 
 > Introduced in [GitLab Ultimate][ee] 10.7.
 
@@ -292,7 +292,7 @@ up in the merge request widget for easy discovery. When the branch is deleted,
 for example after the merge request is merged, the Review App will automatically
 be deleted.
 
-### Auto DAST
+### Auto DAST **[ULTIMATE]**
 
 > Introduced in [GitLab Ultimate][ee] 10.4.
 
@@ -305,7 +305,7 @@ later download and check out.
 In GitLab Ultimate, any security warnings are also
 [shown in the merge request widget](../../user/project/merge_requests/dast.md).
 
-### Auto Browser Performance Testing
+### Auto Browser Performance Testing **[PREMIUM]**
 
 > Introduced in [GitLab Premium][ee] 10.4.
 

doc/user/admin_area/settings/external_authorization.md

-# External authorization control
+# External authorization control **[PREMIUM]**
 
 >
 [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/4216) in

doc/user/group/contribution_analytics/index.md

-# Contribution Analytics
+# Contribution Analytics **[STARTER]**
 
 >**Note:**
-This feature was introduced in [GitLab Starter][ee] 8.3.
+Introduced in [GitLab Starter][ee] 8.3.
 
 Track your team members' activity across your organization.
 

doc/user/group/epics/index.md

-# Epics
+# Epics **[ULTIMATE]**
 
 > Introduced in [GitLab Ultimate][ee] 10.2.
 

doc/user/group/index.md

@@ -152,7 +152,7 @@ There are two different ways to add a new project to a group:
 
     ![Select group](img/select_group_dropdown.png)
 
-### Default project creation level
+### Default project creation level **[STARTER]**
 
 > [Introduced][ee-2534] in [GitLab Premium][ee] 10.5.
 > Brought to [GitLab Starter][ee] in 10.7.
@@ -270,10 +270,7 @@ To enable this feature, navigate to the group settings page. Select
 
 ![Checkbox for share with group lock](img/share_with_group_lock.png)
 
-#### Member Lock
-
-> Available in [GitLab Starter](https://about.gitlab.com/products/) and
-[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
+#### Member Lock **[STARTER]**
 
 With **Member Lock** it is possible to lock membership in project to the
 level of members in group.
@@ -299,18 +296,13 @@ request to add new user to project through API will not be possible.
 
 - **Projects**: view all projects within that group, add members to each project,
 access each project's settings, and remove any project from the same screen.
-- **Webhooks**: configure [webhooks](../project/integrations/webhooks.md)
-and [push rules](../../push_rules/push_rules.md) to your group
-(Push Rules is available in [GitLab Starter][ee].)
-- **Audit Events**: view [Audit Events](../../administration/audit_events.md)
-for the group (GitLab admins only, available in [GitLab Starter][ee])
-- **Pipelines quota**: keep track of the
-[pipeline quota](../admin_area/settings/continuous_integration.md) for the group
-
-## User contribution analysis
-
-> Available in [GitLab Starter](https://about.gitlab.com/products/) and
-[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
+- **Webhooks**: configure [webhooks](../project/integrations/webhooks.md) to your group.
+- **Push rules**: configure [push rules](https://docs.gitlab.com/ee/push_rules/push_rules.html#push-rules) to your group. **[STARTER]**
+- **Audit Events**: view [Audit Events](https://docs.gitlab.com/ee/administration/audit_events.html#audit-events)
+for the group. **[STARTER ONLY]**
+- **Pipelines quota**: keep track of the [pipeline quota](../admin_area/settings/continuous_integration.md) for the group
+
+## User contribution analysis **[STARTER]**
 
 With [GitLab Contribution Analytics](contribution_analytics/index.md)
 you have an overview of the contributions (pushes, merge requests,

doc/user/group/roadmap/index.md

-# Roadmap
+# Roadmap **[ULTIMATE]**
 
 > Introduced in [GitLab Ultimate][ee] 10.5.
 

doc/user/group/saml_sso/index.md

-# SAML SSO for Groups (Beta)
+# SAML SSO for Groups (Beta) **[PREMIUM]**
 
 > Introduced in [GitLab Premium][https://about.gitlab.com/products/] 10.7.
 

doc/user/permissions.md

@@ -126,17 +126,12 @@ and drag issues around. Read though the
 [documentation on Issue Boards permissions](project/issue_board.md#permissions)
 to learn more.
 
-### File Locking permissions
-
-> Available in [GitLab Premium](https://about.gitlab.com/products/) and [GitLab.com Silver](https://about.gitlab.com/gitlab-com/).
+### File Locking permissions **[PREMIUM]**
 
 The user that locks a file or directory is the only one that can edit and push their changes back to the repository where the locked objects are located.
 
 Read through the documentation on [permissions for File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html#permissions-on-file-locking) to learn more.
 
-File Locking is available in
-[GitLab Premium](https://about.gitlab.com/products/) only.
-
 ### Confidential Issues permissions
 
 Confidential issues can be accessed by reporters and higher permission levels,
@@ -199,7 +194,7 @@ will find the option to flag the user as external.
 By default new users are not set as external users. This behavior can be changed
 by an administrator under **Admin > Application Settings**.
 
-## Auditor users
+## Auditor users **[PREMIUM ONLY]**
 
 >[Introduced][ee-998] in [GitLab Premium][eep] 8.17.
 
@@ -286,16 +281,13 @@ for details about the pipelines security model.
 Since GitLab 8.15, LDAP user permissions can now be manually overridden by an admin user.
 Read through the documentation on [LDAP users permissions](../administration/auth/how_to_configure_ldap_gitlab_ee/index.md) to learn more.
 
-## Auditor users permissions
+## Auditor users permissions **[PREMIUM ONLY]**
 
 > Available in [GitLab Premium](https://about.gitlab.com/products/).
 
 An Auditor user should be able to access all projects and groups of a GitLab instance
 with the permissions described on the documentation on [auditor users permissions](https://docs.gitlab.com/ee/administration/auditor_users.html#permissions-and-restrictions-of-an-auditor-user).
 
-Auditor users are available in [GitLab Premium](https://about.gitlab.com/products/)
-only.
-
 [^1]: On public and internal projects, all users are able to perform this action
 [^2]: Guest users can only view the confidential issues they created themselves
 [^3]: If **Public pipelines** is enabled in **Project Settings > CI/CD**

doc/user/project/canary_deployments.md

-# Canary Deployments
+# Canary Deployments **[PREMIUM]**
 
 > [Introduced][ee-1659] in [GitLab Premium][eep] 9.1.
 

doc/user/project/clusters/index.md

@@ -222,7 +222,7 @@ to reach your apps. This heavily depends on your domain provider, but in case
 you aren't sure, just create an A record with a wildcard host like
 `*.example.com.`.
 
-## Setting the environment scope
+## Setting the environment scope **[PREMIUM]**
 
 NOTE: **Note:**
 This is only available for [GitLab Premium][ee] where you can add more than
@@ -281,7 +281,7 @@ The result will then be:
 - The staging cluster will be used for the "deploy to staging" job.
 - The production cluster will be used for the "deploy to production" job.
 
-## Multiple Kubernetes clusters
+## Multiple Kubernetes clusters **[PREMIUM]**
 
 > Introduced in [GitLab Premium][ee] 10.3.
 
@@ -308,7 +308,7 @@ GitLab CI/CD build environment.
 | `KUBE_CA_PEM` | (**deprecated**) Only if a custom CA bundle was specified. Raw PEM data. |
 | `KUBECONFIG` | Path to a file containing `kubeconfig` for this deployment. CA bundle would be embedded if specified. |
 
-## Monitoring your Kubernetes cluster
+## Monitoring your Kubernetes cluster **[ULTIMATE]**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4701) in [GitLab Ultimate][ee] 10.6.
 
@@ -346,9 +346,7 @@ and add a Kubernetes cluster again.
 
 Here's what you can do with GitLab if you enable the Kubernetes integration.
 
-### Deploy Boards
-
-> Available in [GitLab Premium][ee].
+### Deploy Boards **[PREMIUM]**
 
 GitLab's Deploy Boards offer a consolidated view of the current health and
 status of each CI [environment](../../../ci/environments.md) running on Kubernetes,
@@ -358,9 +356,7 @@ workflow they already use without any need to access Kubernetes.
 
 [> Read more about Deploy Boards](../deploy_boards.md)
 
-### Canary Deployments
-
-> Available in [GitLab Premium][ee].
+### Canary Deployments **[PREMIUM]**
 
 Leverage [Kubernetes' Canary deployments](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments)
 and visualize your canary deployments right inside the Deploy Board, without

doc/user/project/deploy_boards.md

-# Deploy Boards
+# Deploy Boards **[PREMIUM]**
 
 > [Introduced][ee-1589] in [GitLab Premium][ee] 9.0.
 

doc/user/project/description_templates.md

@@ -55,12 +55,12 @@ changes you made after picking the template and return it to its initial status.
 
 ![Description templates](img/description_templates.png)
 
-## Setting a default template for issues and merge requests
+## Setting a default template for issues and merge requests  **[STARTER**
 
 >
 **Notes:**
 - This feature was introduced before [description templates](#overview) and is
-  available only for [GitLab Enterprise Starter][products]. It can be enabled
+  available in [GitLab Starter][products]. It can be enabled
   in the project's settings.
 - Templates for issues were [introduced][ee-28] in GitLab EE 8.1.
 - Templates for merge requests were [introduced][ee-7478ece] in GitLab EE 6.9.

doc/user/project/file_lock.md

-# File Locking
+# File Locking **[PREMIUM]**
 
 >**Notes:**
 - [Introduced][ee-440] in [GitLab Premium][ee] 8.9.

doc/user/project/index.md

@@ -17,7 +17,7 @@ When you create a project in GitLab, you'll have access to a large number of
 
 - [Issue tracker](issues/index.md): Discuss implementations with your team within issues
   - [Issue Boards](issue_board.md): Organize and prioritize your workflow
-  - [Multiple Issue Boards](issue_board.md#multiple-issue-boards) (**Starter/Premium**): Allow your teams to create their own workflows (Issue Boards) for the same project
+  - [Multiple Issue Boards](https://docs.gitlab.com/ee/user/project/issue_board.html#multiple-issue-boards): Allow your teams to create their own workflows (Issue Boards) for the same project **[STARTER]**
 - [Repositories](repository/index.md): Host your code in a fully
 integrated platform
   - [Branches](repository/branches/index.md): use Git branching strategies to
@@ -34,11 +34,11 @@ integrated platform
 
 - [Issue tracker](issues/index.md): Discuss implementations with your team within issues
   - [Issue Boards](issue_board.md): Organize and prioritize your workflow
-  - [Multiple Issue Boards](issue_board.md#multiple-issue-boards) (**Starter/Premium**): Allow your teams to create their own workflows (Issue Boards) for the same project
+  - [Multiple Issue Boards](issue_board.md#multiple-issue-boards): Allow your teams to create their own workflows (Issue Boards) for the same project **[STARTER]**
 - [Merge Requests](merge_requests/index.md): Apply your branching
 strategy and get reviewed by your team
-  - [Merge Request Approvals](merge_requests/merge_request_approvals.md) (**Starter/Premium**): Ask for approval before
-  implementing a change
+  - [Merge Request Approvals](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html): Ask for approval before
+  implementing a change **[STARTER]**
   - [Fix merge conflicts from the UI](merge_requests/resolve_conflicts.md):
   Your Git diff tool right from GitLab's UI
   - [Review Apps](../../ci/review_apps/index.md): Live preview the results

doc/user/project/integrations/kubernetes.md

@@ -81,9 +81,7 @@ GitLab CI/CD build environment:
 
 Here's what you can do with GitLab if you enable the Kubernetes integration.
 
-### Deploy Boards
-
-> Available in [GitLab Premium][ee].
+### Deploy Boards **[PREMIUM]**
 
 GitLab's Deploy Boards offer a consolidated view of the current health and
 status of each CI [environment](../../../ci/environments.md) running on Kubernetes,
@@ -93,9 +91,7 @@ workflow they already use without any need to access Kubernetes.
 
 [> Read more about Deploy Boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html)
 
-### Canary Deployments
-
-> Available in [GitLab Premium][ee].
+### Canary Deployments **[PREMIUM]**
 
 Leverage [Kubernetes' Canary deployments](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments)
 and visualize your canary deployments right inside the Deploy Board, without

doc/user/project/integrations/prometheus.md

@@ -91,7 +91,7 @@ GitLab will automatically scan the Prometheus server for metrics from known serv
 
 You can view the performance dashboard for an environment by [clicking on the monitoring button](../../../ci/environments.md#monitoring-environments).
 
-### Adding additional metrics
+### Adding additional metrics **[PREMIUM]**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3799) in [GitLab Premium](https://about.gitlab.com/products/) 10.6.
 

doc/user/project/issue_board.md

-# Issue Board
+# Issue Boards
 
 >**Note:**
 [Introduced][ce-5554] in [GitLab 8.11](https://about.gitlab.com/2016/08/22/gitlab-8-11-released/#issue-board).
@@ -267,7 +267,7 @@ to another list the label changes and a system not is recorded.
 
 ![Issue Board system notes](img/issue_board_system_notes.png)
 
-## Multiple issue boards
+## Multiple Issue Boards
 
 > Introduced in [GitLab Enterprise Edition 8.13](https://about.gitlab.com/2016/10/22/gitlab-8-13-released/#multiple-issue-boards-ee).
 
@@ -283,7 +283,7 @@ Multiple issue boards feature is available for **projects in GitLab Starter Edit
 
 ![Multiple Issue Boards](img/issue_boards_multiple.png)
 
-## Board with configuration
+## Configurable Issue Board **[STARTER]**
 
 > Introduced in [GitLab Starter Edition 10.2](https://about.gitlab.com/2017/11/22/gitlab-10-2-released/#issue-boards-configuration).
 
@@ -303,7 +303,7 @@ If you don't have editing permission in a board, you're still able to see the co
 
 ![Viewing board configuration](img/issue_board_view_scope.png)
 
-## Group Issue Boards
+## Group Issue Boards **[PREMIUM]**
 
 > Introduced in [GitLab Enterprise Edition 10.0 Premium](https://about.gitlab.com/2017/09/22/gitlab-10-0-released/#group-issue-boards).
 
@@ -316,7 +316,7 @@ group-level objects are available.
 
 ![Group issue board](img/group_issue_board.png)
 
-## Focus mode
+## Focus mode **[STARTER]**
 
 > Introduced in [GitLab Enterprise Edition 9.1](https://about.gitlab.com/2017/04/22/gitlab-9-1-released/#issue-boards-focus-mode-ees-eep).
 
@@ -329,12 +329,13 @@ Click the button at the top right to toggle focus mode on and off. In focus mode
 [Developers and up](../permissions.md) can use all the functionality of the
 Issue Board, that is create/delete lists and drag issues around.
 
-##  Group Issue Board
+## Group Issue Boards
 
->Introduced in GitLab 10.6
+> Introduced in GitLab 10.6
 
-Group issue board is analogous to project-level issue board and it is accessible at the group
-navigation level. A group-level issue board allows you to view all issues from all projects in that group or descendant subgroups. Similarly, you can only filter by group labels for these
+Group Issue Board is analogous to project-level issue board and it is accessible at the group
+navigation level. A group-level issue board allows you to view all issues from all projects in that group
+(currently, it does not see issues from projects in subgroups). Similarly, you can only filter by group labels for these
 boards. When updating milestones and labels for an issue through the sidebar update mechanism, again only
 group-level objects are available.
 
@@ -342,7 +343,7 @@ group-level objects are available.
 
 Different issue board features are available in different [GitLab tiers](https://about.gitlab.com/pricing/), as shown in the following table:
 
-| Tier | Number of project issue boards | Board with configuration in project issue boards | Number of group issue boards | Board with configuration in group issue boards |
+| Tier | Number of Project Issue Boards | Board with configuration in Project Issue Boards | Number of Group Issue Boards | Board with configuration in Group Issue Boards |
 | --- | --- | --- | --- | --- |
 | Core    | 1        | No  | 1        | No  |
 | Starter  | Multiple | Yes | 1        | No  |

doc/user/project/issues/create_new_issue.md

@@ -59,15 +59,12 @@ supported.
 
 ![Bottom of a project issues page](img/new_issue_from_email.png)
 
-## New issue via Service Desk
+## New issue via Service Desk **[PREMIUM]**
 
 Enable [Service Desk](../service_desk.md) to your project and offer email support.
 By doing so, when your customer sends a new email, a new issue can be created in
 the appropriate project and followed up from there.
 
-_Service Desk is available only for [GitLab Premium](https://about.gitlab.com/products/)
-and [GitLab.com Silver](https://about.gitlab.com/gitlab-com/) subscribers._
-
 ## New issue from the group-level Issue Tracker
 
 Head to the Group dashboard and click "Issues" in the sidebar to visit the Issue Tracker

doc/user/project/issues/csv_export.md

-# Export Issues to CSV
+# Export Issues to CSV **[STARTER]**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1126) in [GitLab Starter 9.0](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#export-issues-ees-eep).
 

doc/user/project/issues/index.md

@@ -139,19 +139,13 @@ Find GitLab Issue Boards by navigating to your **Project's Dashboard** > **Issue
 Read through the documentation for [Issue Boards](../issue_board.md)
 to find out more about this feature.
 
-### Export Issues to CSV
-
-> Available in [GitLab Starter](https://about.gitlab.com/products/) and
-[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
+### Export Issues to CSV **[STARTER]**
 
 Issues can be [exported as CSV](csv_export.md) from GitLab and are sent to your email as an attachment.
 
 _Exporting issues to CSV is available only in [GitLab Enterprise Edition](https://about.gitlab.com/products/)._
 
-## Related Issues
-
-> Available in [GitLab Starter](https://about.gitlab.com/products/) and
-[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
+## Related Issues **[STARTER]**
 
 Related Issues are a bi-directional relationship between any two issues
 and appear in a block below the issue description. Issues can be across groups

doc/user/project/issues/issues_functionalities.md

@@ -41,10 +41,7 @@ it's reassigned to someone else to take it from there.
 if a user is not member of that project, it can only be
 assigned to them if they created the issue themselves.
 
-##### 3.1. Multiple Assignees
-
-> Available in [GitLab Starter](https://about.gitlab.com/products/) and
-[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
+##### 3.1. Multiple Assignees **[STARTER]**
 
 Often multiple people likely work on the same issue together,
 which can especially be difficult to track in large teams
@@ -89,10 +86,7 @@ but they are immediately available to all projects in the group.
 > **Tip:**
 if the label doesn't exist yet, when you click **Edit**, it opens a dropdown menu from which you can select **Create new label**.
 
-#### 8. Weight
-
-> Available in [GitLab Starter](https://about.gitlab.com/products/) and
-[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
+#### 8. Weight **[STARTER]**
 
 - Attribute a weight (in a 0 to 9 range) to that issue. Easy to complete
 should weight 1 and very hard to complete should weight 9.

doc/user/project/issues/multiple_assignees_for_issues.md

-# Multiple Assignees for Issues
+# Multiple Assignees for Issues **[STARTER]**
 
 > **Note:**
 [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/1904)

doc/user/project/issues/related_issues.md

-# Related issues
+# Related issues **[STARTER]**
 
 > [Introduced][ee-1797] in [GitLab Starter][ee] 9.4.
 

doc/user/project/labels.md

@@ -88,9 +88,9 @@ From the group epic list page, you can [filter](../search/index.md#issues-and-me
 ### Filtering in issue boards
 
 - From [project boards](issue_board.md), you can filter by both group labels and project labels in the [search and filter bar](../search/index.md#issue-boards).
-- From [group issue boards](issue_board.md#group-issue-boards), you can filter by only group labels in the [search and filter bar](../search/index.md#issue-boards) (available in GitLab Premium).
-- From [project boards](issue_board.md), you can filter by both group labels and project labels in the [issue board configuration](issue_board.md#board-with-configuration) (available in GitLab Premium).
-- From [group issue boards](issue_board.md#group-issue-boards), you can filter by only group labels in the [issue board configuration](issue_board.md#board-with-configuration) (available in GitLab Premium).
+- From [group issue boards](issue_board.md#group-issue-boards), you can filter by only group labels in the [search and filter bar](../search/index.md#issue-boards). **[PREMIUM]**
+- From [project boards](issue_board.md), you can filter by both group labels and project labels in the [issue board configuration](issue_board.md#board-with-configuration). **[PREMIUM]**
+- From [group issue boards](issue_board.md#group-issue-boards), you can filter by only group labels in the [issue board configuration](issue_board.md#board-with-configuration). **[PREMIUM]**
 
 ## Subscribing to labels
 

doc/user/project/merge_requests/browser_performance_testing.md

-# Browser Performance Testing
+# Browser Performance Testing **[PREMIUM]**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3507) in [GitLab Premium](https://about.gitlab.com/products/) 10.3.
 

doc/user/project/merge_requests/code_quality_diff.md

-# Code Quality
+# Code Quality **[STARTER]**
 
 > [Introduced][ee-1984] in [GitLab Starter][ee] 9.3.
 

doc/user/project/merge_requests/container_scanning.md

-# Container Scanning
+# Container Scanning **[ULTIMATE]**
 
 > [Introduced][ee-3672] in [GitLab Ultimate][ee] 10.4.
 

doc/user/project/merge_requests/dast.md

-# Dynamic Application Security Testing (DAST)
+# Dynamic Application Security Testing (DAST) **[ULTIMATE]**
 
 > [Introduced][ee-4348] in [GitLab Ultimate][ee] 10.4.
 

doc/user/project/merge_requests/dependency_scanning.md

-# Dependency Scanning
+# Dependency Scanning **[ULTIMATE]**
 
 > [Introduced][ee-5105] in [GitLab Ultimate][ee] 10.7.
 

doc/user/project/merge_requests/index.md

@@ -32,15 +32,15 @@ With GitLab merge requests, you can:
 
 With **[GitLab Enterprise Edition][ee]**, you can also:
 
-- View the deployment process across projects with [Multi-Project Pipeline Graphs](https://docs.gitlab.com/ee/ci/multi_project_pipeline_graphs.html#multi-project-pipeline-graphs) (available only in GitLab Premium)
-- Request [approvals](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html) from your managers (available in GitLab Starter)
-- [Squash and merge](https://docs.gitlab.com/ee/user/project/merge_requests/squash_and_merge.html) for a cleaner commit history (available in GitLab Starter)
-- Analyze the impact of your changes with [Code Quality](#code-quality) (available in GitLab Starter)
-- Analyze your source code for vulnerabilities with [Static Application Security Testing](#static-application-security-testing) (available in GitLab Ultimate)
-- Analyze your dependencies for vulnerabilities with [Dependency Scanning](#dependency-scanning) (available in GitLab Ultimate)
-- Analyze your Docker images for vulnerabilities with [Container Scanning](#container-scanning) (available in GitLab Ultimate)
-- Analyze your running web applications for vulnerabilities with [Dynamic Application Security Testing](#dynamic-application-security-testing) (available in GitLab Ultimate)
-- Determine the performance impact of changes with [Browser Performance Testing](#browser-performance-testing) (available in GitLab Premium)
+- View the deployment process across projects with [Multi-Project Pipeline Graphs](https://docs.gitlab.com/ee/ci/multi_project_pipeline_graphs.html#multi-project-pipeline-graphs) **[PREMIUM]**
+- Request [approvals](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html) from your managers **[STARTER]**
+- [Squash and merge](https://docs.gitlab.com/ee/user/project/merge_requests/squash_and_merge.html) for a cleaner commit history **[STARTER]**
+- Analyze the impact of your changes with [Code Quality reports](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality_diff.html) **[STARTER]**
+- Analyze your source code for vulnerabilities with [Static Application Security Testing](#static-application-security-testing) **[ULTIMATE]**
+- Analyze your dependencies for vulnerabilities with [Dependency Scanning](#dependency-scanning) **[ULTIMATE]**
+- Analyze your Docker images for vulnerabilities with [Container Scanning](#container-scanning) **[ULTIMATE]**
+- Analyze your running web applications for vulnerabilities with [Dynamic Application Security Testing](#dynamic-application-security-testing) **[ULTIMATE]**
+- Determine the performance impact of changes with [Browser Performance Testing](#browser-performance-testing) **[PREMIUM]**
 
 ## Use cases
 
@@ -48,7 +48,7 @@ A. Consider you are a software developer working in a team:
 
 1. You checkout a new branch, and submit your changes through a merge request
 1. You gather feedback from your team
-1. You work on the implementation optimizing code with [Code Quality](#code-quality)
+1. You work on the implementation optimizing code with [Code Quality reports](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality_diff.html) **[STARTER]**
 1. You build and test your changes with GitLab CI/CD
 1. You request the [approval](#merge-request-approvals) from your manager
 1. Your manager pushes a commit with his final review, [approves the merge request](#merge-request-approvals), and set it to [merge when pipeline succeeds](#merge-when-pipeline-succeeds)
@@ -61,8 +61,8 @@ B. Consider you're a web developer writing a webpage for your company's website:
 1. You gather feedback from your reviewers
 1. Your changes are previewed with [Review Apps](../../../ci/review_apps/index.md)
 1. You request your web designers for their implementation
-1. You request the [approval](#merge-request-approvals) from your manager
-1. Once approved, your merge request is [squashed and merged](#squash-and-merge), and [deployed to staging with GitLab Pages](https://about.gitlab.com/2016/08/26/ci-deployment-and-environments/)
+1. You request the [approval](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html) from your manager **[STARTER]**
+1. Once approved, your merge request is [squashed and merged](https://docs.gitlab.com/ee/user/project/merge_requests/squash_and_merge.html), and [deployed to staging with GitLab Pages](https://about.gitlab.com/2016/08/26/ci-deployment-and-environments/) (Squash and Merge is available in GitLab Starter)
 1. Your production team [cherry picks](#cherry-pick-changes) the merge commit into production
 
 ## Merge requests per project
@@ -237,7 +237,7 @@ can show the Code Climate report right in the merge request widget area.
 
 [Read more about Code Quality reports.](code_quality_diff.md)
 
-## Static Application Security Testing
+## Static Application Security Testing **[ULTIMATE]**
 
 > Introduced in [GitLab Ultimate][products] 10.3.
 
@@ -248,7 +248,7 @@ merge request widget area.
 
 [Read more about Static Application Security Testing reports.](sast.md)
 
-## Dependency Scanning
+## Dependency Scanning **[ULTIMATE]**
 
 > Introduced in [GitLab Ultimate][products] 10.7.
 
@@ -259,7 +259,7 @@ merge request widget area.
 
 [Read more about Dependency Scanning reports.](dependency_scanning.md)
 
-## Container Scanning
+## Container Scanning **[ULTIMATE]**
 
 > Introduced in [GitLab Ultimate][products] 10.4.
 
@@ -270,7 +270,7 @@ merge request widget area.
 
 [Read more about Container Scanning reports.](container_scanning.md)
 
-## Dynamic Application Security Testing
+## Dynamic Application Security Testing **[ULTIMATE]**
 
 > Introduced in [GitLab Ultimate][products] 10.4.
 
@@ -282,7 +282,7 @@ merge request widget area.
 
 [Read more about Dynamic Application Security Testing reports.](dast.md)
 
-## Browser Performance Testing
+## Browser Performance Testing **[PREMIUM]**
 
 > Introduced in [GitLab Premium][products] 10.3.
 

doc/user/project/merge_requests/merge_request_approvals.md

-# Merge request approvals
+# Merge request approvals **[STARTER]**
 
-> Introduced in [GitLab Enterprise Edition 7.12](https://about.gitlab.com/2015/06/22/gitlab-7-12-released/#merge-request-approvers-ee-only), available in [GitLab Starter](https://about.gitlab.com/products/).
+> Introduced in [GitLab Enterprise Edition 7.12](https://about.gitlab.com/2015/06/22/gitlab-7-12-released/#merge-request-approvers-ee-only).
 
 ## Overview
 

doc/user/project/merge_requests/sast.md

-# Static Application Security Testing (SAST)
+# Static Application Security Testing (SAST) **[ULTIMATE]**
 
 > [Introduced][ee-3775] in [GitLab Ultimate][ee] 10.3.
 

doc/user/project/merge_requests/squash_and_merge.md

-# Squash and merge
+# Squash and merge **[STARTER]**
 
 > [Introduced][ee-1024] in [GitLab Starter][ee] 8.17.
 

doc/user/project/milestones/burndown_charts.md

-# Burndown Charts
+# Burndown Charts **[STARTER]**
 
 >**Notes:**
 - [Introduced][ee-1540] in [GitLab Starter 9.1][ee-9.1].

doc/user/project/milestones/index.md

@@ -64,9 +64,9 @@ From the project issue/merge request list pages and the group issue/merge reques
 ### Filtering in issue boards
 
 - From [project issue boards](../issue_board.md), you can filter by both group milestones and project milestones in the [search and filter bar](../../search/index.md#issue-boards).
-- From [group issue boards](../issue_board.md#group-issue-boards) (available in [GitLab Premium](https://about.gitlab.com/products), you can filter by only group milestones in the [search and filter bar](../../search/index.md#issue-boards).
-- From [project issue boards](../issue_board.md), you can filter by both group milestones and project milestones in the [issue board configuration](../issue_board.md#board-with-configuration) (available in [GitLab Starter](https://about.gitlab.com/products)) .
-- From [group issue boards](../issue_board.md#group-issue-boards) (available in [GitLab Premium](https://about.gitlab.com/products)), you can filter by only group milestones in the [issue board configuration](../issue_board.md#board-with-configuration).
+- From [group issue boards](../issue_board.md#group-issue-boards), you can filter by only group milestones in the [search and filter bar](../../search/index.md#issue-boards). **[PREMIUM]**
+- From [project issue boards](../issue_board.md), you can filter by both group milestones and project milestones in the [issue board configuration](../issue_board.md#board-with-configuration). **[STARTER]**
+- From [group issue boards](../issue_board.md#group-issue-boards) you can filter by only group milestones in the [issue board configuration](../issue_board.md#board-with-configuration). **[PREMIUM]**
 
 
 
@@ -105,7 +105,7 @@ These features are only available for project milestones and not group milestone
 - Participants and labels that are used in issues and merge requests that have the milestone assigned are displayed.
 - [Burndown chart](#burndown-charts).
 
-### Burndown Charts
+### Burndown Charts **[STARTER]**
 
 For project milestones only, and in [GitLab Starter](https://about.gitlab.com/products), a [burndown chart](burndown_charts.md) is in the milestone view, showing the progress of completing a milestone.
 

doc/user/project/protected_branches.md

@@ -66,7 +66,7 @@ dropdown list in the "Already protected" area.
 If you don't choose any of those options while creating a protected branch,
 they are set to "Masters" by default.
 
-## Restricting push and merge access to certain users
+## Restricting push and merge access to certain users **[STARTER]**
 
 > This feature was [introduced][ce-5081] in [GitLab Starter][ee] 8.11.
 

doc/user/project/repository/index.md

@@ -163,14 +163,10 @@ Select branches to compare and view the changes inline:
 
 Find it under your project's **Repository > Compare**.
 
-## Locked files
+## Locked files **[PREMIUM]**
 
-> Available in [GitLab Premium](https://about.gitlab.com/products/).
-
-Lock your files to prevent any conflicting changes.
-
-[File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html) is available only in
-[GitLab Premium](https://about.gitlab.com/products/).
+[Lock your files](https://docs.gitlab.com/ee/user/project/file_lock.html) to
+prevent any conflicting changes.
 
 ## Repository's API
 

doc/user/project/service_desk.md

-# Service Desk
+# Service Desk **[PREMIUM]**
 
 > [Introduced][ee-149] in [GitLab Premium 9.1][eep-9.1].
 

doc/user/project/settings/index.md

@@ -34,15 +34,15 @@ Set up your project's merge request settings:
 
 - Set up the merge request method (merge commit, [fast-forward merge](../merge_requests/fast_forward_merge.html)).
 - Merge request [description templates](../description_templates.md#description-templates).
-- Enable [merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html#merge-request-approvals), _available in [GitLab Starter](https://about.gitlab.com/products/)_.
+- Enable [merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html#merge-request-approvals). **[STARTER]**
 - Enable [merge only of pipeline succeeds](../merge_requests/merge_when_pipeline_succeeds.md).
 - Enable [merge only when all discussions are resolved](../../discussions/index.md#only-allow-merge-requests-to-be-merged-if-all-discussions-are-resolved).
 
 ![project's merge request settings](img/merge_requests_settings.png)
 
-### Service Desk
+### Service Desk **[PREMIUM]**
 
-Enable [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html) for your project to offer customer support. Service Desk is available in [GitLab Premium](https://about.gitlab.com/products/).
+Enable [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html) for your project to offer customer support.
 
 ### Export project
 

doc/user/search/advanced_global_search.md

-# Advanced Global Search
+# Advanced Global Search **[STARTER]**
 
 >
 - [Introduced][ee-109] in GitLab [Starter][ee] 8.4.

doc/user/search/advanced_search_syntax.md

-# Advanced Syntax Search
+# Advanced Syntax Search **[STARTER]**
 
 >**Notes:**
 - Introduced in [GitLab Enterprise Starter][ee] 9.2

doc/workflow/README.md

@@ -44,9 +44,9 @@ comments: false
   - [Merge requests versions](../user/project/merge_requests/versions.md)
   - ["Work In Progress" merge requests](../user/project/merge_requests/work_in_progress_merge_requests.md)
   - [Fast-forward merge requests](../user/project/merge_requests/fast_forward_merge.md)
-  - (EE) [Merge request approvals](../user/project/merge_requests/merge_request_approvals.md)
-- (EE) [Repository mirroring](repository_mirroring.md)
-- (EE Premium) [Service Desk](../user/project/service_desk.md)
+  - [Merge request approvals](../user/project/merge_requests/merge_request_approvals.md) **[STARTER]**
+- [Repository mirroring](repository_mirroring.md) **[STARTER]**
+- [Service Desk](../user/project/service_desk.md) **[PREMIUM]**
 - [Manage large binaries with Git LFS](lfs/manage_large_binaries_with_git_lfs.md)
 - [Importing from SVN, GitHub, Bitbucket, etc](importing/README.md)
 - [Todos](todos.md)

doc/workflow/issue_weight.md

-# Issue Weight
+# Issue Weight **[STARTER]**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/76)
 in [GitLab Starter](https://about.gitlab.com/products/) 8.3.

doc/workflow/repository_mirroring.md

 # Repository mirroring
 
-
 Repository Mirroring is a way to mirror repositories from external sources.
 It can be used to mirror all branches, tags, and commits that you have
 in your repository.
@@ -47,7 +46,7 @@ A few things/limitations to consider:
   a push mirror so that your active GitLab repository can push its changes to the
   old location.
 
-## Pulling from a remote repository
+## Pulling from a remote repository **[STARTER]**
 
 >[Introduced][ee-51] in GitLab Enterprise Edition 8.2.
 
@@ -84,7 +83,7 @@ this branch to prevent any changes from being lost.
 
 ![Diverged branch](repository_mirroring/repository_mirroring_diverged_branch.png)
 
-### Trigger update using API
+### Trigger update using API **[STARTER]**
 
 >[Introduced][ee-3453] in GitLab Enterprise Edition 10.3.
 
@@ -94,7 +93,7 @@ will be pulled immediately.
 
 Read the [Pull Mirror Trigger API docs][pull-api].
 
-### Pull only protected branches
+### Pull only protected branches **[STARTER]**
 
 >[Introduced][ee-3326] in GitLab Enterprise Edition 10.3.
 
@@ -102,7 +101,7 @@ You can choose to only pull the protected branches from your remote repository t
 
 To use this option go to your project's repository settings page under pull mirror.
 
-### Overwrite diverged branches
+### Overwrite diverged branches **[STARTER]**
 
 >[Introduced][ee-4559] in GitLab Enterprise Edition 10.6.
 
@@ -111,7 +110,7 @@ if your local version has diverged from the remote.
 
 To use this option go to your project's repository settings page under pull mirror.
 
-### Hard failure
+### Hard failure **[STARTER]**
 
 >[Introduced][ee-3117] in GitLab Enterprise Edition 10.2.
 
@@ -127,7 +126,7 @@ When a project is hard failed, it will no longer get picked up for mirroring.
 A user can resume the project mirroring again by either [forcing an update](#forcing-an-update)
 or by changing the import URL in repository settings.
 
-### SSH authentication
+### SSH authentication **[STARTER]**
 
 > [Introduced][ee-2551] in GitLab Starter 9.5
 
@@ -230,7 +229,7 @@ backoff period.
 If the mirror fails (eg: branch diverged from upstream), the project's backoff
 period will be penalized each time it fails up to a maximum amount of time.
 
-## Pushing to a remote repository
+## Pushing to a remote repository **[STARTER]**
 
 >[Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/249) in
 GitLab Enterprise Edition 8.7.