Summary and recommendation
Slab 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.
Slab is a knowledge base platform with three fixed workspace roles: Owner, Admin, and Member.
There are no custom roles or granular permission tiers - role definitions are not configurable.
Post and topic visibility can be restricted to specific audiences, but this does not create a separate role layer.
SCIM provisioning and SSO are both gated behind the Business plan ($12.50/user/mo, billed annually) or Enterprise.
The Free plan supports up to 10 members;
the Startup plan starts at $35/mo annually for the first 10 users.
Like every app that gates automation behind a higher tier, the cost of manual management compounds as headcount grows.
Quick facts
| Admin console path | Settings → Members (accessible via the workspace sidebar) |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Business |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Owner | Full workspace control: billing, plan changes, all admin settings, member management, content management, and workspace deletion. | Cannot be removed by Admins; only one Owner per workspace by default. | All plans | Counts as a full paid seat | Ownership transfer must be initiated by the current Owner. |
| Admin | Invite and remove members, manage roles up to Admin level, manage topics and content, configure integrations. | Cannot change billing, cannot remove or demote the Owner, cannot delete the workspace. | All plans | Counts as a full paid seat | Admins can remove other Admins but cannot promote anyone to Owner. |
| Member | Create, edit, and comment on posts; view all non-restricted content; manage own profile. | Cannot invite or remove other users, cannot access workspace settings, cannot manage topics. | All plans | Counts as a full paid seat |
Permission model
- Model type: role-based
- Description: Slab uses three fixed workspace-level roles (Owner, Admin, Member). There are no custom roles or granular permission sets. Post-level and topic-level visibility can be restricted, but role definitions themselves are not customizable.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Workspace-level roles only; post and topic visibility can be set to restricted audiences but this does not constitute a separate role tier.
How to add users
- Navigate to Settings → Members in the workspace sidebar.
- Click 'Invite Members'.
- Enter one or more email addresses (comma-separated) or copy the invite link.
- Select the role to assign (Member or Admin).
- Click 'Send Invites'. Recipients receive an email invitation to join the workspace.
Required fields: Email address
Watch out for:
- Invited users must accept the email invitation before they appear as active members.
- Pending invitations count toward seat usage on paid plans once accepted.
- Invite links grant Member-level access by default; role can be changed after joining.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | Yes | Automatic domain-based user add |
| IdP provisioning | Yes | Business |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Slab's official help documentation describes removing a member from the workspace (deactivation/removal), which revokes access. There is no documented permanent account deletion option available to workspace admins. Removed users lose workspace access but their authored content remains attributed to them.
- Navigate to Settings → Members.
- Locate the member to remove using the search or scroll.
- Click the '…' (more options) menu next to the member's name.
- Select 'Remove from workspace'.
- Confirm the removal in the dialog.
| Data impact | Behavior |
|---|---|
| Owned records | Posts and content authored by the removed member remain in the workspace and retain the original author attribution. |
| Shared content | Content the removed member contributed to remains accessible to other workspace members. |
| Integrations | Any personal integration tokens or connections set up by the removed user may stop functioning; workspace-level integrations are unaffected. |
| License freed | Removing a member frees the seat; the seat count decreases and billing adjusts at the next billing cycle per Slab's billing terms. |
Watch out for:
- Content authored by removed members is not reassigned automatically; it remains under the original author's name.
- If SCIM is configured, deprovisioning via the IdP will automatically remove the user from Slab without manual steps in the admin console.
- Removed users can be re-invited; they would rejoin as a new member and consume a seat again.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Full Member Seat | All roles (Owner, Admin, Member) consume one full seat. There is no viewer-only or read-only free tier for internal users on paid plans. | Startup: $6.67/user/mo (billed annually, minimum 10 users at $35/mo); Business: $12.50/user/mo (billed annually); Enterprise: custom pricing. |
- Where to check usage: Settings → Members shows the current member list and count. Billing seat count is visible under Settings → Billing.
- How to identify unused seats: No built-in last-active or login-date column is documented in the Members settings page. Admins must manually review the member list or use IdP activity reports if SSO is configured.
- Billing notes: Free plan supports up to 10 members. Startup plan starts at $35/mo (billed annually) for the first 10 users. Business plan is $12.50/user/mo billed annually. Seat counts adjust at the next billing cycle when members are removed. SCIM provisioning requires the Business plan and an SSO prerequisite.
The cost of manual management
Every app in your stack that lacks automated provisioning creates the same category of risk: access that outlives employment. In Slab, removing a user requires navigating to Settings → Members, locating the member, and confirming removal through the options menu - one user at a time.
Slab provides no built-in last-login or activity-date column in the Members view. Identifying inactive seats requires either manual review of the member list or cross-referencing IdP activity logs if SSO is configured. Seat counts adjust at the next billing cycle after removal, not immediately.
The decision
Every app in your environment that requires a paid seat for read access raises the stakes of keeping stale members around - Slab is no exception.
Manual management is viable for small, stable teams on the Startup plan where seat counts are predictable and turnover is low, but the three-role model offers little flexibility as org structure grows.
For teams on the Business or Enterprise plan with an active Okta, Entra ID, or OneLogin deployment, SCIM provisioning eliminates the manual removal workflow entirely and is the documented path for offboarding at scale.
Google Workspace is not a supported SCIM IdP - teams using Google as their primary IdP must manage Slab membership manually or via invite link.
Bottom line
Slab's manual user management is straightforward but operationally thin: no activity visibility, no viewer tier, and no bulk operations in the admin console.
Every app that requires a paid seat for read access amplifies the cost of keeping stale members around, and Slab is no exception. Teams that can meet the Business plan threshold and run a supported IdP should treat SCIM as the default operating model;
everyone else should build a recurring manual audit into their access review cadence.
Automate Slab 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.
