Summary and recommendation
Notion user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Notion's admin controls live under Settings & Members, where Workspace Owners manage roles, seats, and access across the full workspace. The permission model is two-layered: a workspace-level role (Owner, Member, or Guest) combined with per-page or per-teamspace access levels (Full access, Can edit, Can comment, Can view).
There are no custom roles at any plan tier.
SCIM provisioning is gated behind the Enterprise plan and requires SAML SSO to be configured first. Teams on the Business plan get SAML SSO but must handle every app's user lifecycle - invites, role changes, and removals - entirely by hand.
Quick facts
| Admin console path | Settings & Members → Members (workspace owner/admin view) |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Workspace Owner | Full administrative control: manage billing, change workspace settings, invite/remove all members, assign roles, configure SSO/SCIM, export all content, manage integrations. | Cannot be removed from the workspace without first transferring ownership. | All plans (Free, Plus, Business, Enterprise) | Counts as a paid member seat on Plus, Business, and Enterprise plans. | Multiple owners are allowed; each counts as a full paid seat. On Free plan, limited to 1 owner. |
| Member | Can create, edit, and share pages within the workspace. Can invite guests to pages they have access to (subject to workspace settings). Can view all teamspaces they are added to. | Cannot access billing, change workspace-level settings, manage other members' roles, or configure SSO/SCIM. | All plans | Counts as a paid member seat on Plus, Business, and Enterprise plans. | Members can be restricted from inviting guests via a workspace-level toggle controlled by owners. |
| Guest | Access only to specific pages they have been explicitly invited to. Can comment or edit depending on the page-level permission granted (Full access, Can edit, Can comment, Can view). | Cannot access the full workspace, teamspaces, or any pages not explicitly shared with them. Cannot see the member list. | All plans; guest limits vary by plan (Free: up to 10 guests; Plus: up to 100 guests; Business/Enterprise: higher limits apply). | Guests do not consume paid member seats. | Guests from the same email domain as the workspace may be prompted to join as full members, consuming a paid seat. External guests count against per-plan guest limits. |
Permission model
- Model type: role-based
- Description: Notion uses a two-layer permission model. At the workspace level, users are assigned one of three roles: Workspace Owner, Member, or Guest. At the page/teamspace level, access is controlled by per-object permission settings (Full access, Can edit, Can comment, Can view). Teamspace-level roles (Full member, Limited member) further restrict which pages within a teamspace a member can see. There are no custom roles.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Workspace role (Owner/Member/Guest) + per-page permission level (Full access, Can edit, Can comment, Can view) + teamspace membership level (Full/Limited). No field-level or property-level permissions.
How to add users
- Navigate to Settings & Members in the left sidebar.
- Select the 'Members' tab.
- Click 'Add members'.
- Enter the email address(es) of the person(s) to invite.
- Select the role to assign: Member or Workspace Owner.
- Click 'Invite'. The invitee receives an email invitation link.
Required fields: Email address of the invitee
Watch out for:
- Inviting a new member immediately adds a paid seat and may trigger a prorated billing charge on Plus and Business plans.
- If the invitee's email domain matches an allowed domain, they may be able to join without a direct invite (domain-based joining must be enabled by an owner).
- On Free plan, workspace is limited to a small number of collaborators before upgrade is required.
- Guests invited to a page who later join the workspace as members will begin consuming a paid seat.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | Yes | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Notion does not permanently delete member accounts from the workspace. Owners can remove (deactivate) a member, which revokes their workspace access. The user's Notion account itself is not deleted. Content created by the removed member remains in the workspace. Via SCIM on Enterprise, deprovisioning suspends the user's access automatically.
- Navigate to Settings & Members in the left sidebar.
- Select the 'Members' tab.
- Locate the member to remove using search or scroll.
- Click the '…' (three-dot) menu next to the member's name.
- Select 'Remove from workspace'.
- Confirm the removal in the dialog. The member loses access immediately.
| Data impact | Behavior |
|---|---|
| Owned records | Pages and databases created by the removed member remain in the workspace and are still accessible to other members who had access. Content is not deleted. |
| Shared content | Shared pages the removed member had access to remain intact for other collaborators. The removed member loses access to all workspace content. |
| Integrations | Any personal API integrations or connections the member set up under their account may stop functioning if they were tied to their personal token. Workspace-level integrations are unaffected. |
| License freed | The paid seat is released upon removal. On annual plans, the seat cost may not be immediately refunded but the seat count decreases for future billing cycles or renewals. |
Watch out for:
- Removing a member does not reassign ownership of their pages; content remains attributed to them but is accessible to workspace members with existing access.
- If the removed member was the sole owner of private pages not shared with anyone, those pages may become inaccessible to the team. Owners should audit private content before removal.
- On Enterprise with SCIM, deprovisioning via IdP suspends access but workspace owners should also verify the member is fully removed in Notion's member list.
- Annual plan billing: removing a member mid-cycle does not automatically generate a prorated refund; consult Notion billing support.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Member (paid seat) | Full workspace access, ability to create and edit pages, teamspace membership, API access. Roles: Workspace Owner or Member. | Plus: $10/user/month (annual) or $12/user/month (monthly); Business: $20/user/month (annual) or $18/user/month (monthly); Enterprise: custom pricing (typically $18–25/user/month based on volume). |
| Guest (free seat) | Access only to explicitly shared pages. Cannot access full workspace. Limited by plan-based guest caps. | Free; does not consume a paid seat. |
- Where to check usage: Settings & Members → Members tab - displays total member count and lists all current members with their roles.
- How to identify unused seats: Notion does not natively display last-login or activity timestamps in the admin Members tab. Workspace owners must use SCIM audit logs (Enterprise) or manually review member activity. There is no built-in 'inactive member' report on Plus or Business plans.
- Billing notes: Seats are billed per member (Owners + Members). Guests are free but capped per plan. Adding members mid-cycle on monthly plans adjusts the next invoice. On annual plans, adding members triggers a prorated charge for the remainder of the billing year. Removing members on annual plans does not automatically issue prorated credits; contact Notion support. Enterprise pricing is negotiated and volume-based.
The cost of manual management
Adding a member in Notion is immediate and billable: on Plus and Business plans, each invite triggers a prorated seat charge for the remainder of the billing cycle. Removing a member on an annual plan does not automatically generate a credit; teams must contact Notion support to reconcile the difference.
Notion provides no native last-login or activity timestamp in the Members tab on Plus or Business plans. Identifying unused seats requires either manual review or SCIM audit logs, which are only available on Enterprise. Without that signal, overpayment on dormant seats is a quiet, ongoing cost.
What IT admins are saying
The most consistent friction point reported by Notion admins is the SCIM cutoff: Business plan includes SAML SSO but not SCIM, leaving mid-market teams without automated provisioning unless they move to Enterprise at custom pricing.
Guest seat caps are a recurring complaint - the 100-guest limit on Plus is frequently cited as too restrictive for teams with external collaborators.
Offboarding is another pain point: removing a member does not surface or reassign their private pages, creating real content-loss risk during employee departures.
Google Workspace users specifically flag the absence of automatic group sync on non-Enterprise plans, requiring manual group maintenance or a full Enterprise upgrade.
Common complaints:
- Business plan includes SAML SSO but not SCIM provisioning, requiring manual user management for mid-market teams that do not qualify or budget for Enterprise.
- Enterprise pricing is not publicly listed, making cost comparison difficult for procurement teams.
- No native last-login or activity report in the admin panel on Plus or Business plans, making it hard to identify and reclaim unused seats.
- Guest seat limits (especially the 10-guest cap on Free and 100-guest cap on Plus) are frequently cited as restrictive for teams collaborating with external stakeholders.
- Removing a member does not reassign or surface their private pages, leading to content loss risk when offboarding employees.
- Google Workspace users note the absence of automatic group sync; groups must be managed manually or via SCIM on Enterprise.
The decision
Stay on manual management if your team is small, turnover is low, and you are on Plus or Business with no near-term path to Enterprise. The process is straightforward for stable teams, and the guest model handles external collaborators at no seat cost within plan limits.
Move to SCIM-backed provisioning - which requires Enterprise - if you are onboarding and offboarding frequently, managing more than a few dozen members, or operating under compliance requirements that demand auditable provisioning events.
The Business plan's SSO-without-SCIM gap is the clearest forcing function: if you need automated lifecycle management for every app in your stack, Notion's Enterprise tier is the only supported path.
Bottom line
Notion's manual admin workflow is functional but limited above small team sizes.
The absence of activity reporting on Plus and Business plans makes seat hygiene difficult, and the SCIM gap on Business means mid-market teams carry a real operational burden managing every app's user lifecycle by hand.
Enterprise resolves the provisioning problem but comes at custom, volume-negotiated pricing with no public rate - making budget planning harder than it should be for procurement teams.
Automate Notion workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
