From 29d27b73ad68406a89ea86d950f1fa57d6e7b93e Mon Sep 17 00:00:00 2001 From: Mark Fulton <128738155+markunl@users.noreply.github.com> Date: Tue, 13 Feb 2024 08:01:45 -0500 Subject: [PATCH] docs: Update license-keys.mdx (#6012) Added statement to contact customer success for help --- website/docs/using-unleash/deploy/license-keys.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/website/docs/using-unleash/deploy/license-keys.mdx b/website/docs/using-unleash/deploy/license-keys.mdx index 928302dbae..3db9dcdb94 100644 --- a/website/docs/using-unleash/deploy/license-keys.mdx +++ b/website/docs/using-unleash/deploy/license-keys.mdx @@ -5,7 +5,8 @@ title: License Keys for Unleash Enterprise (BETA) import VideoContent from '@site/src/components/VideoContent.jsx' This document describes all aspects and workflows of license key management in Unleash 5.8 and above. -Note that this is beta functionality and as such, these steps should only be followed under the direction of Unleash Customer Success. +Note that this is beta functionality and as such, these steps should only be followed under the direction of Unleash Customer Success. +*For questions, please reach out to Unleash Customer Success using the [linked address](mailto:customersuccess@getunleash.io)* :::info Warning @@ -110,4 +111,4 @@ For security, if using [helm charts](https://github.com/Unleash/helm-charts) or :::info The default image references in the Helm chart point to open-source Unleash resources. To use Unleash Enterprise, you must manually update the image references to point to the appropriate *unleash-enterprise* images -::: \ No newline at end of file +:::