diff options
| author | Mike Lewis <mlewis@gitlab.com> | 2019-06-12 05:55:12 +0000 |
|---|---|---|
| committer | Mike Lewis <mlewis@gitlab.com> | 2019-06-12 05:55:12 +0000 |
| commit | 9baff6f6b58981ac1565d371b01948a286f7bffd (patch) | |
| tree | 259ad453d25c80ccdfe4136bccad6d1616d9b9a6 /doc/subscriptions | |
| parent | ee87aa5a0f8964c0bde89cef5a71daf9a74bf70f (diff) | |
| parent | 014ab2eb06786f31521332ab1779c39318377240 (diff) | |
| download | gitlab-ce-9baff6f6b58981ac1565d371b01948a286f7bffd.tar.gz | |
Merge branch 'docs-SSOT-misc-1' into 'master'
Docs: SSOT edits to docs that are alone in root directories
See merge request gitlab-org/gitlab-ce!28694
Diffstat (limited to 'doc/subscriptions')
| -rw-r--r-- | doc/subscriptions/index.md | 19 |
1 files changed, 18 insertions, 1 deletions
diff --git a/doc/subscriptions/index.md b/doc/subscriptions/index.md index 9b0aa5aa272..37051f6b10f 100644 --- a/doc/subscriptions/index.md +++ b/doc/subscriptions/index.md @@ -1,3 +1,7 @@ +--- +type: index, reference +--- + # Subscription setup and management This page will help get you started with your new subscription or manage an existing one, whether you have subscribed to GitLab.com or self-managed GitLab. @@ -42,7 +46,8 @@ After purchase, the license file is sent to the email address tied to the Custom ### Link your GitLab.com account with your Customers Portal account -NOTE: **Note:** This is *required* for GitLab.com subscriptions. +NOTE: **Note:** +This is *required* for GitLab.com subscriptions. Once signed into the customers portal, if your account is not already linked, you should be prompted to link your account with a "Link my GitLab Account" button. @@ -109,3 +114,15 @@ These issues are the best avenue for getting updates on specific product plans a ### Contacting Support Learn more about the tiers of [GitLab Support](https://about.gitlab.com/support/) or [submit a request via the Support Portal](https://support.gitlab.com/hc/en-us/requests/new). + +<!-- ## Troubleshooting + +Include any troubleshooting steps that you can foresee. If you know beforehand what issues +one might have when setting this up, or when something is changed, or on upgrading, it's +important to describe those, too. Think of things that may go wrong and include them here. +This is important to minimize requests for support, and to avoid doc comments with +questions that you know someone might ask. + +Each scenario can be a third-level heading, e.g. `### Getting error message X`. +If you have none to add when creating a doc, leave this section in place +but commented out to help encourage others to add to it in the future. --> |