diff --git a/website/source/docs/vagrant-cloud/organizations/authentication-policy.html.md b/website/source/docs/vagrant-cloud/organizations/authentication-policy.html.md
new file mode 100755
index 000000000..c46ef8e93
--- /dev/null
+++ b/website/source/docs/vagrant-cloud/organizations/authentication-policy.html.md
@@ -0,0 +1,30 @@
+---
+layout: "docs"
+page_title: "Organization Authentication Policy"
+sidebar_current: "vagrant-cloud-organizations-authentication-policy"
+---
+
+
+# Set an Organization Authentication Policy
+
+Because organization membership affords members access to potentially sensitive
+resources, owners can set organization-wide authentication policy in Vagrant
+Enterprise.
+
+## Requiring Two-Factor Authentication
+
+Organization owners can require that all organization team members use
+[two-factor authentication](/docs/enterprise/user-accounts/authentication.html).
+Those that lack two-factor authentication will be locked out of the web
+interface until they enable it or leave the organization.
+
+Visit your organization's configuration page to enable this feature. All
+organization owners must have two-factor authentication enabled to require the
+practice organization-wide. Note: locked-out users are still be able to interact
+with Vagrant Enterprise using their `ATLAS_TOKEN`.
+
+## Disabling Two-Factor Authentication Requirement
+
+Organization owners can disable the two-factor authentication requirement from
+their organization's configuration page. Locked-out team members (those who have
+not enabled two-factor authentication) will have their memberships reinstated.
diff --git a/website/source/docs/vagrant-cloud/organizations/create.html.md b/website/source/docs/vagrant-cloud/organizations/create.html.md
new file mode 100755
index 000000000..82178df6d
--- /dev/null
+++ b/website/source/docs/vagrant-cloud/organizations/create.html.md
@@ -0,0 +1,15 @@
+---
+layout: "docs"
+page_title: "Create an Organization"
+sidebar_current: "vagrant-cloud-organizations-create"
+---
+
+# Create an Organization
+
+To create an organization:
+
+1. Create a personal account. You'll use this to create and administrate the
+organization. You'll be able to add other users as owners of the organization,
+so it won't be tied solely to your account.
+
+1. Visit your new organization page to create the organization.
diff --git a/website/source/docs/vagrant-cloud/organizations/index.html.md b/website/source/docs/vagrant-cloud/organizations/index.html.md
new file mode 100755
index 000000000..61367eb2c
--- /dev/null
+++ b/website/source/docs/vagrant-cloud/organizations/index.html.md
@@ -0,0 +1,14 @@
+---
+layout: "docs"
+page_page_title: "Organizations in Vagrant Enterprise"
+sidebar_current: "vagrant-cloud-organizations"
+---
+
+## Organizations in Vagrant Enterprise
+
+Organizations are a group of users in Vagrant Enterprise that have access and
+ownership over shared resources. When operating within a team, we recommend
+creating an organization to manage access control, auditing, billing and
+authorization.
+
+Each individual member of your organization should have their own account.
diff --git a/website/source/docs/vagrant-cloud/organizations/migrate.html.md b/website/source/docs/vagrant-cloud/organizations/migrate.html.md
new file mode 100755
index 000000000..8c94423ba
--- /dev/null
+++ b/website/source/docs/vagrant-cloud/organizations/migrate.html.md
@@ -0,0 +1,24 @@
+---
+layout: "docs"
+page_title: "Migrate User to Organization"
+sidebar_current: "vagrant-cloud-organizations-migrate"
+---
+
+# Migrate User to Organization
+
+To migrate an existing user account to an organization:
+
+1. Create or retrieve the username of a new personal account. You'll add this
+account as an "owner" for the new organization during the migration process. If
+you already have another account, write down your username.
+
+2. Sign in as the account you wish to migrate and visit the migration page.
+
+3. Put the username of the personal account you wish to make an owner of the
+organization into the username text field and press "Migrate".
+
+4. You should now be logged out and receive a confirmation email with the
+personal account you migrated to.
+
+5. Now, sign in with your personal account. If you visit you settings page, you
+should see your migrated organization available to administrate.
diff --git a/website/source/layouts/docs.erb b/website/source/layouts/docs.erb
index 8a0b1ae87..4c6adc28f 100644
--- a/website/source/layouts/docs.erb
+++ b/website/source/layouts/docs.erb
@@ -233,6 +233,16 @@
               <li<%= sidebar_current("vagrant-cloud-boxes-using") %>><a href="/docs/vagrant-cloud/boxes/using.html">Finding & Using Boxes</a></li>
             </ul>
           </li>
+
+          <li<%= sidebar_current("vagrant-cloud-organizations") %>>
+            <a href="/docs/vagrant-cloud/organizations/index.html">Organizations</a>
+            <ul class="nav">
+              <li<%= sidebar_current("vagrant-cloud-organizations-create") %>><a href="/docs/vagrant-cloud/organizations/create.html">Create an Organization</a></li>
+              <li<%= sidebar_current("vagrant-cloud-organizations-migrate") %>><a href="/docs/vagrant-cloud/organizations/migrate.html">Migrate User to Organization</a></li>
+              <li<%= sidebar_current("vagrant-cloud-organizations-authentication-policy") %>><a href="/docs/vagrant-cloud/organizations/authentication-policy.html">Authentication Policy</a></li>
+            </ul>
+          </li>
+
           <li<%= sidebar_current("vagrant-cloud-request-limits") %>><a href="/docs/vagrant-cloud/request-limits.html">Request Limits</a></li>
         </ul>
       </li>