Summary and recommendation
Slack 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.
Slack's admin console covers the full user lifecycle - inviting members, assigning roles, managing guests, and deactivating accounts - but the depth of control available depends heavily on your plan. Business+ includes SSO but stops short of SCIM and custom roles, both of which require Enterprise Grid.
When you consider every app in your environment that needs the same lifecycle discipline, Slack's manual tooling is workable for small teams but shows its limits quickly at scale. Granular permission delegation is a Grid-only capability with no intermediate option.
Quick facts
| Admin console path | Workspace name (top-left) → Settings & administration → Manage members | OR → Admin console (Enterprise Grid) |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise Grid |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Primary Owner | Full workspace control: transfer ownership, delete workspace, manage billing, all admin actions. Only one per workspace. | Cannot be deactivated by other admins; ownership must be transferred first. | All plans | Counts as a full paid seat (Pro/Business+/Grid) | Transferring primary ownership requires the current Primary Owner to initiate the transfer; no admin can force it. |
| Workspace Owner | Manage admins, adjust workspace settings, manage apps and integrations, export data (on eligible plans), manage billing on some plans. | Cannot transfer primary ownership or delete the workspace. | All plans | Counts as a full paid seat | On Enterprise Grid, Workspace Owners operate within a single workspace; Org Owners govern the entire Grid org. |
| Workspace Admin | Invite/remove members, manage channels, approve app installs (if enabled), manage guest accounts. | Cannot change owner-level settings, manage billing, or export message history without owner permission. | All plans | Counts as a full paid seat | On Enterprise Grid, workspace-level admins cannot manage org-level policies; those require Org Admin or Org Owner role. |
| Member | Send messages, join public channels, use apps, create channels (if permitted by admin), upload files. | Cannot access admin console, manage other users, or change workspace settings. | All plans | Counts as a full paid seat | Default role for all invited users; admins can restrict channel creation and app installation for members. |
| Multi-Channel Guest | Access to multiple specified channels only; can message and share files within those channels. | Cannot browse or join channels outside their assigned set, cannot see the full member directory. | Pro, Business+, Enterprise Grid | Billed at 1 full seat per 5 multi-channel guests (Pro/Business+); Enterprise Grid pricing varies by contract. | Guest billing ratio (5:1) means small numbers of guests can still consume a full seat. Guests cannot be converted to members without re-inviting. |
| Single-Channel Guest | Access to exactly one channel; can message and share files within that channel only. | Cannot access any other channel, cannot see member directory, cannot use most apps. | Pro, Business+, Enterprise Grid | Billed at 1 full seat per 5 single-channel guests (Pro/Business+). | Single-channel guests are the most restricted account type. Upgrading to multi-channel guest or member requires admin action and may affect billing. |
| Org Owner (Enterprise Grid only) | Manages the entire Enterprise Grid org: create/delete workspaces, set org-wide policies, manage Org Admins, access all workspaces. | Cannot act below org level without also being a workspace owner/admin in a specific workspace. | Enterprise Grid | Counts as a full paid seat | Org Owner role is separate from Workspace Owner; an Org Owner is not automatically an admin in every workspace. |
| Org Admin (Enterprise Grid only) | Manage members across workspaces, enforce org-wide settings, manage channels across workspaces. | Cannot manage billing or delete the org; cannot override Org Owner decisions. | Enterprise Grid | Counts as a full paid seat | Custom roles (Enterprise Grid) can further subdivide Org Admin permissions for delegated administration. |
Permission model
- Model type: hybrid
- Description: Slack uses a fixed role hierarchy (Primary Owner → Owner → Admin → Member → Guest) at the workspace level, with an additional org-level hierarchy on Enterprise Grid (Org Owner → Org Admin). Enterprise Grid also supports custom roles that allow granular delegation of specific admin permissions to designated users without granting full admin access.
- Custom roles: Yes
- Custom roles plan: Enterprise Grid
- Granularity: Custom roles on Enterprise Grid allow scoping permissions such as: manage members, manage channels, manage apps, manage emoji, and manage workflows. Standard plans use only the fixed role hierarchy with no granular permission customization.
How to add users
- Navigate to your workspace URL or go to https://slack.com/admin.
- Click the workspace name in the top-left corner, then select 'Settings & administration' → 'Invite people' (non-Grid) or open the Admin console → Members → 'Invite members' (Grid).
- Enter one or more email addresses in the invitation field.
- Select the role to assign: Member, Multi-Channel Guest, or Single-Channel Guest.
- For guests, specify which channel(s) they will have access to.
- Optionally set an expiration date for guest accounts.
- Click 'Send invitations'. The invitee receives an email with a link to join.
- The user completes account setup (name, password or SSO) and joins the workspace.
Required fields: Email address, Role selection (Member or Guest type), Channel assignment (required for guest roles)
Watch out for:
- Invitations expire after 30 days if not accepted; admins must resend.
- If SSO is enforced, users must authenticate via the configured IdP; password-based signup is blocked.
- On Enterprise Grid, members can be invited to the org and then assigned to specific workspaces separately.
- Approved domains (domain allowlisting) allow anyone with a matching email to join without an explicit invitation, which can cause unexpected seat consumption.
- Guests count toward billing at a 5:1 ratio (5 guests = 1 paid seat) on Pro and Business+; admins should track guest counts carefully.
- Re-inviting a previously deactivated user reactivates their account and restores their message history.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Yes | Admin console → Members → 'Invite members' → 'Upload a CSV' (Enterprise Grid). On Pro/Business+, bulk invite via comma-separated emails in the invite dialog; CSV upload is an Enterprise Grid feature. |
| Domain whitelisting | Yes | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise Grid |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Slack does not allow permanent deletion of user accounts by workspace admins. Accounts can only be deactivated. Deactivated accounts retain all message history, files, and channel memberships in a suspended state. The user cannot log in or be seen as active, but their content remains visible in channels. Account deletion (full erasure) requires a formal data deletion request submitted to Slack under applicable privacy regulations (e.g., GDPR right to erasure), handled by Slack's support team, not through the admin console.
- Go to https://slack.com/admin or navigate to workspace name → Settings & administration → Manage members.
- Search for the member by name or email.
- Click the three-dot menu (⋮) next to the member's name.
- Select 'Deactivate account'.
- Confirm the deactivation in the dialog box.
- The account is immediately deactivated; the user is logged out of all sessions.
| Data impact | Behavior |
|---|---|
| Owned records | All messages sent by the deactivated user remain visible in channels and DMs. Files uploaded by the user remain accessible to other members. The user's profile remains searchable in the member directory as 'Deactivated'. |
| Shared content | Shared files and messages are retained and visible to other workspace members. Channel membership is preserved in a suspended state; the user appears as a former member. |
| Integrations | Apps and integrations authorized under the deactivated user's account may stop functioning. Any workflows or bots using that user's OAuth tokens will lose access and need to be re-authorized by an active admin or member. |
| License freed | The seat is freed immediately upon deactivation and is no longer billed in the next billing cycle. On annual plans, credit may be applied as a prorated account credit rather than a cash refund, depending on plan terms. |
Watch out for:
- Deactivating the Primary Owner is not possible until ownership is transferred to another member.
- Reactivating a deactivated account restores full message history and channel memberships; the user resumes as if never deactivated.
- On Enterprise Grid, deactivating a user at the org level removes them from all workspaces simultaneously; workspace-level deactivation only removes them from that workspace.
- Apps and bots authorized by the deactivated user will break silently; admins should audit integrations before deactivating power users.
- Slack does not send an automatic notification to the deactivated user; communication must be handled externally.
- Guest accounts that are deactivated still count toward the 30-day billing cycle if deactivated mid-cycle on some plan configurations.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Full Member seat | Unlimited message history (Pro+), unlimited apps, full channel access, all collaboration features per plan tier. | Free: $0 (90-day history limit). Pro: $7.25/user/mo (annual) or $8.75/user/mo (monthly). Business+: $15/user/mo (annual) or $18/user/mo (monthly). Enterprise Grid: custom pricing. |
| Guest seat (Multi-Channel or Single-Channel) | Access limited to assigned channels only. Billed at 1 full seat per 5 guests on Pro and Business+. | Effectively 1/5 of a full member seat cost; 5 guests consume 1 billable seat. Enterprise Grid guest billing is contract-dependent. |
| Free plan seat | 90-day message history, 10 app integrations, 1:1 audio/video calls, limited file storage. | $0; up to unlimited members but with feature restrictions. |
- Where to check usage: https://slack.com/admin → Billing (workspace name → Settings & administration → Billing) to view current active member count, guest count, and next invoice estimate. Enterprise Grid: Admin console → Org settings → Billing.
- How to identify unused seats: Slack does not provide a native 'last active' filter in the standard admin console for Pro/Business+ plans. On Enterprise Grid, the Analytics dashboard (Admin console → Analytics → Members) shows last active date, message count, and days since last activity, enabling identification of inactive seats. On lower plans, admins must manually review member list or use the Slack API (users.list with presence data) to identify inactive accounts.
- Billing notes: Slack uses a fair billing model: adding a member mid-cycle results in a prorated charge for the remainder of the billing period. Deactivating a member mid-cycle results in a prorated credit applied to the next invoice, not a cash refund. Annual plan customers receive account credits for deactivated seats. The 5:1 guest-to-seat billing ratio applies on Pro and Business+; partial groups of guests still round up to the nearest full seat. Free plan has no billing but caps message history at 90 days and integrations at 10. Enterprise Grid pricing is negotiated; standard per-user rates do not apply.
The cost of manual management
Without automation, every app in your stack demands its own offboarding action. In Slack specifically, deactivating a user is a manual, one-at-a-time operation through the admin console - there is no bulk deactivation UI on Pro or Business+ plans.
Guest accounts add compounding overhead: the 5:1 billing ratio is non-obvious, partial guest groups round up to a full seat, and there is no native last-active filter on lower plans to help identify seats worth reclaiming.
Admins who need that visibility must either upgrade to Enterprise Grid for the Analytics dashboard or query the API directly.
What IT admins are saying
Recurring friction points reported by Slack admins center on plan architecture and billing opacity. The jump from Business+ to Enterprise Grid carries a significant price increase, and once on Grid, downgrading is not supported.
Admins on Pro and Business+ consistently flag the absence of a last-active date in the member list as a gap that makes license hygiene difficult.
Guest billing surprises - particularly the rounding behavior on small guest counts - are a frequent source of unexpected invoice increases. On Enterprise Grid, the split between org-level and workspace-level admin permissions creates confusion, especially for teams managing multiple workspaces under one org.
Common complaints:
- Enterprise Grid lock-in: once upgraded to Enterprise Grid, downgrading to a lower plan is not supported by Slack.
- Large price jump from Business+ ($15/user/mo) to Enterprise Grid (custom, typically significantly higher), with SCIM and custom roles gated behind Grid.
- Complex multi-workspace architecture on Enterprise Grid creates confusion about org-level vs. workspace-level admin permissions.
- No native 'last active' date visible in the admin member list on Pro and Business+ plans, making it difficult to identify and reclaim unused seats without using the API.
- Deactivated users cannot be permanently deleted through the admin console; full erasure requires a separate GDPR/privacy request to Slack support.
- Guest billing ratio (5:1) is non-obvious and can result in unexpected charges when adding small numbers of guests.
- App integrations authorized by a deactivated user break silently with no automated alert to admins.
- Invitation links expire after 30 days with no automatic reminder, causing friction for slow-onboarding users.
- SSO enforcement cannot be applied selectively to specific user groups on non-Grid plans; it is all-or-nothing at the workspace level.
- CSV bulk invite is only available on Enterprise Grid; Pro and Business+ admins must paste comma-separated emails manually.
The decision
When offboarding a single employee, every app they accessed needs a discrete deprovisioning action - and in Slack, that means a manual console step with no bulk option on lower plans. Manual administration is workable for small, stable teams on Pro or Business+, but becomes operationally expensive as headcount grows or turnover increases.
Teams that need SCIM-based automation, custom role delegation, or org-wide analytics face a hard gate at Enterprise Grid with no intermediate option. If your organization is already evaluating Enterprise Grid for other reasons, the operational lift of manual management is a reasonable factor to weigh alongside the plan cost.
Bottom line
Slack's manual admin tooling is straightforward for day-to-day tasks like inviting members and deactivating accounts, but it surfaces real limitations at scale.
The absence of bulk actions, native inactivity reporting on lower plans, and the Enterprise Grid requirement for SCIM and custom roles mean that teams beyond a few dozen seats will encounter recurring manual overhead.
Guest billing mechanics and the irreversibility of the Grid upgrade are the two areas most likely to produce unplanned costs or operational lock-in.
Automate Slack 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.
