diff --git a/categories/account.yaml b/categories/account.yaml
index de3a9d604..3e9c3dfb2 100644
--- a/categories/account.yaml
+++ b/categories/account.yaml
@@ -23,7 +23,7 @@ Managing your account:
Account members:
- "Domain Access Control"
-- "Managing seats"
+- "Managing Seats"
- "Managing Multiple Members on One Account"
- "Creating Accounts for Clients"
- "Differences between Account Collaborator and Multi-User Accounts"
diff --git a/content/articles/managing-seats.md b/content/articles/managing-seats.md
index c1116667d..2d1f316f2 100644
--- a/content/articles/managing-seats.md
+++ b/content/articles/managing-seats.md
@@ -1,6 +1,6 @@
---
-title: Managing seats
-excerpt: Managing Seats and Members in Your Team Account.
+title: Managing Seats
+excerpt: Managing seats and members in your account.
categories:
- Account
---
@@ -14,7 +14,13 @@ categories:
## Overview
-Account seats for additional team members are only available on Teams or Enterprise plans. The Teams plan includes one seat at no additional cost, allowing you to have one member actively involved in domain management. Any seats beyond the initial one will incur extra costs. Enterprise plans have custom pricing and seat numbers. [See our pricing page for more details](https://dnsimple.com/pricing).
+
+Account seats for additional team members are only available on Teams or Enterprise plans.
+
+
+The Teams plan includes one seat at no additional cost, allowing you to have one member actively involved in domain management. Any seats beyond the initial one will incur extra costs. Enterprise plans have custom pricing and seat numbers. [See our pricing page for more details](https://dnsimple.com/pricing).
+
+A DNSimple account can be associated with one or more users. When you add someone to an account as a member, you will have the option to set their level of access to **full access** (access to all resources inside an account) or **limited access** (specific to each domain). The members will retain their unique login credentials and multi-factor authentication configuration.
## Increasing the number of seats
@@ -45,6 +51,11 @@ Below is an example of decreasing seats when the number of account members excee

+### Removing a member from your account:
+
+1. Click **Remove** for the member you want to remove, and confirm that you want to remove them.
+2. Once you've removed them from the account, that user will no longer show up on the **Members** card.
+
## Inviting new members
To invite new members to your account, follow these steps:
@@ -61,6 +72,10 @@ You can increase the seat count and invite members in one seamless process.

+
+You cannot add a user who has the same email address as the account email address. You must first change the account email address (we recommend a generic email address like admin@ or billing@) before you can that user.
+
+
## Automatic Seat Allocation with Single Sign-On (SSO) Providers:
If you've configured your account with single sign-on using [Google](/articles/google-identity-provider/) or [Okta](/articles/okta-identity-provider/), your seat count is managed based on your organization's configuration, and seat allocation becomes automatic.