From 1b330c7f0c5bd753c1964b92fd728a793ff06fe6 Mon Sep 17 00:00:00 2001
From: Drew Bailey <2614075+drewbailey@users.noreply.github.com>
Date: Wed, 12 Aug 2020 14:13:22 -0400
Subject: [PATCH] add info about multi-vault namespaces (#8654)

* add info about multi-vault namespaces

* typo
---
 website/pages/docs/enterprise/index.mdx | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/website/pages/docs/enterprise/index.mdx b/website/pages/docs/enterprise/index.mdx
index 125640194..21643cd4d 100644
--- a/website/pages/docs/enterprise/index.mdx
+++ b/website/pages/docs/enterprise/index.mdx
@@ -54,6 +54,12 @@ Redundancy Zones enables an operator to deploy a non-voting server as a hot stan
 
 See the [Autopilot - Redundancy Zones](https://learn.hashicorp.com/nomad/operating-nomad/autopilot#redundancy-zones) documentation for a thorough overview.
 
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster to support multiple Vault Namespaces for topology simplicity and fleet consolidation when running Nomad and Vault together. Nomad will automatically retrieve a Vault token based on a job's defined Vault Namespace and make it available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](https://www.nomadproject.io/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
 ## Governance & Policy
 
 Governance & Policy features are part of an add-on module that enables an organization to securely operate Nomad at scale across multiple teams through features such as Audit Logging, Namespaces, Resource Quotas, Sentinel Policies, and Preemption.