coder
diff --git a/‎docs/admin/users/organizations.md
Lines changed: 37 additions & 32 deletions b/‎docs/admin/users/organizations.md
Lines changed: 37 additions & 32 deletions
diff --git a/‎docs/tutorials/using-organizations.md
Lines changed: 0 additions & 135 deletions b/‎docs/tutorials/using-organizations.md
Lines changed: 0 additions & 135 deletions
@@ -14,9 +14,14 @@ with multiple platform teams, all with unique resources:
 
 ![Organizations Example](../../images/admin/users/organizations/diagram.png)
 
+For more information about how to use organizations, visit the
+[organizations best practices](../../tutorials/best-practices/organizations.md)
+guide.
+
 ## The default organization
 
-All Coder deployments start with one organization called `Coder`.
+All Coder deployments start with one organization called `Coder`. All new users
+are added to this organization by default.
 
 To edit the organization details, navigate to `Deployment -> Organizations` in
 the top bar:
@@ -30,29 +35,29 @@ From there, you can manage the name, icon, description, users, and groups:
 ## Additional organizations
 
 Any additional organizations have unique admins, users, templates, provisioners,
-groups, and workspaces. Each organization must have at least one
-[provisioner](../provisioners.md) as the built-in provisioner only applies to
+groups, and workspaces. Each organization must have at least one dedicated
+[provisioner](../provisioners.md) since the built-in provisioner only applies to
 the default organization.
 
 You can configure [organization/role/group sync](./idp-sync.md) from your
 identity provider to avoid manually assigning users to organizations.
 
-## Creating an organization
+## How to create an organization
 
 ### Prerequisites
 
-- Coder v2.16+ deployment with Premium license with Organizations enabled
+- Coder v2.16+ deployment with Premium license and Organizations enabled
   ([contact your account team](https://coder.com/contact)) for more details.
 - User with `Owner` role
 
 ### 1. Create the organization
 
-Within the sidebar, click `New organization` to create an organization. In this
+In the sidebar, select **New organization** to create an organization. In this
 example, we'll create the `data-platform` org.
 
 ![New Organization](../../images/admin/users/organizations/new-organization.png)
 
-From there, let's deploy a provisioner and template for this organization.
+Next deploy a provisioner and template for this organization.
 
 ### 2. Deploy a provisioner
 
@@ -61,50 +66,50 @@ for executing Terraform/OpenTofu to provision the infrastructure for workspaces
 and testing templates. Before creating templates, we must deploy at least one
 provisioner as the built-in provisioners are scoped to the default organization.
 
-Using Coder CLI, run the following command to create a key that will be used to
-authenticate the provisioner:
+1. Using Coder CLI, run the following command to create a key that will be used
+   to authenticate the provisioner:
+
+   ```shell
+   coder provisioner keys create data-cluster-key --org data-platform
+   Successfully created provisioner key data-cluster! Save this authentication token, it will not be shown again.
 
-```sh
-coder provisioner keys create data-cluster-key --org data-platform
-Successfully created provisioner key data-cluster! Save this authentication token, it will not be shown again.
+   < key omitted >
+   ```
 
-< key omitted >
-```
+1. Start the provisioner with the key on your desired platform.
 
-Next, start the provisioner with the key on your desired platform. In this
-example, we'll start it using the Coder CLI on a host with Docker. For
-instructions on using other platforms like Kubernetes, see our
-[provisioner documentation](../provisioners.md).
+   In this example, start the provisioner using the Coder CLI on a host with
+   Docker. For instructions on using other platforms like Kubernetes, see our
+   [provisioner documentation](../provisioners.md).
 
-```sh
-export CODER_URL=https://<your-coder-url>
-export CODER_PROVISIONER_DAEMON_KEY=<key>
-coder provisionerd start --org <org-name>
-```
+   ```sh
+   export CODER_URL=https://<your-coder-url>
+   export CODER_PROVISIONER_DAEMON_KEY=<key>
+   coder provisionerd start --org <org-name>
+   ```
 
 ### 3. Create a template
 
 Once you've started a provisioner, you can create a template. You'll notice the
-"Create Template" screen now has an organization dropdown:
+**Create Template** screen now has an organization dropdown:
 
 ![Template Org Picker](../../images/admin/users/organizations/template-org-picker.png)
 
-### 5. Add members
+### 4. Add members
 
-Navigate to `Deployment->Organizations` to add members to your organization.
-Once added, they will be able to see the organization-specific templates.
+From **Administration > Settings**, select **Organizations** to add members to
+your organization. Once added, they will be able to see the
+organization-specific templates.
 
 ![Add members](../../images/admin/users/organizations/organization-members.png)
 
-### 6. Create a workspace
+### 5. Create a workspace
 
 Now, users in the data platform organization will see the templates related to
 their organization. Users can be in multiple organizations.
 
 ![Workspace List](../../images/admin/users/organizations/workspace-list.png)
 
-## Beta
+## Next steps
 
-As of v2.16.0, Organizations is in beta. If you encounter any issues, please
-[file an issue](https://github.com/coder/coder/issues/new) or contact your
-account team.
+- [Organizations - best practices](../../tutorials/best-practices/organizations.md)