Summary and recommendation
Sigma Computing 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.
Sigma Computing's admin panel gives IT and ops teams direct control over user provisioning through Administration > People > Users.
Every app in your stack benefits from a clean offboarding process, and Sigma is no exception - deactivation preserves content while blocking login, and deletion is permanent and irreversible.
Invitations are email-based;
users must accept before they can log in, and sharing permissions are not granted automatically at invite time.
Quick facts
| Admin console path | Administration (gear icon, bottom-left) > People > Users |
| 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 |
|---|---|---|---|---|---|
| Admin | Full access to all Administration settings, user management, billing, connections, and all workspace content. | Admin account type consumes a licensed seat. Admins can access all content regardless of sharing permissions. | |||
| Creator | Can create, edit, and publish workbooks, datasets, and other documents. Can share content and manage their own documents. | Cannot access Administration panel or manage other users. | Creator seats are typically the highest-cost licensed seat type. | ||
| Explorer | Can explore and interact with shared workbooks, apply filters, drill down, and create personal copies of workbooks. | Cannot publish new workbooks to shared spaces or create new data sources. | Explorer capabilities vary by plan; some interactive features may require a higher plan tier. | ||
| Viewer | Read-only access to shared workbooks and dashboards. | Cannot edit, explore beyond preset controls, or create content. | Viewer is the lowest-cost seat type. Embedded or external viewers may be licensed differently. |
Permission model
- Model type: hybrid
- Description: Sigma uses account types (system roles) that define baseline capabilities, combined with workspace-level and document-level sharing permissions. Teams can be used to grant permissions to groups of users. Custom account types allow admins to create modified permission sets based on existing account types.
- Custom roles: Yes
- Custom roles plan: Not documented
- Granularity: Account-type level (Creator, Explorer, Viewer, Admin) plus per-document and per-workspace sharing permissions (Can View, Can Explore, Can Edit, Can Manage). Custom account types allow toggling specific feature permissions within those tiers.
How to add users
- Navigate to Administration > People > Users.
- Click 'Invite Users'.
- Enter the user's email address.
- Select the account type (Admin, Creator, Explorer, Viewer, or a custom type).
- Optionally assign the user to one or more Teams.
- Click 'Send Invite'. The user receives an email invitation to set up their account.
Required fields: Email address, Account type
Watch out for:
- Users must accept the email invitation before they can log in; pending invitations count toward seat usage depending on plan.
- If SSO is enforced, users must authenticate via the configured identity provider; password-based login may be disabled.
- Inviting a user does not automatically grant access to any specific workbooks or spaces; sharing must be configured separately.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Sigma supports both deactivating and deleting users. Deactivating a user prevents login while preserving their content and account record. Deleting a user permanently removes the account. Official docs describe both actions in the Manage Users page.
- Navigate to Administration > People > Users.
- Locate the user in the list.
- Click the three-dot (more options) menu next to the user.
- Select 'Deactivate' to suspend access without deleting the account.
| Data impact | Behavior |
|---|---|
| Owned records | Content owned by a deactivated or deleted user remains in the workspace and is not automatically removed. |
| Shared content | Shared workbooks and documents the user contributed to remain accessible to other users who have permission. |
| Integrations | Not documented |
| License freed | Deactivating a user frees the licensed seat, making it available for reassignment. |
Watch out for:
- Deactivated users cannot log in but their content persists; admins should reassign ownership of critical documents before deactivation.
- If SCIM provisioning is active, deprovisioning a user in the IdP will automatically deactivate them in Sigma.
- Deletion is permanent and cannot be undone; verify content ownership transfer before deleting.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Admin | Full administrative and analytical capabilities. | |
| Creator | Full content creation, editing, and publishing capabilities. | |
| Explorer | Interactive exploration of shared content; limited creation. | |
| Viewer | Read-only consumption of shared content. |
- Where to check usage: Administration > Account > Usage (or Administration > People > Users to review active vs. inactive accounts and their account types)
- How to identify unused seats: Review the 'Last Active' column in Administration > People > Users to identify users who have not logged in recently. Deactivating inactive users frees their seats.
- Billing notes: Sigma pricing is seat-based and varies by account type. Exact per-seat pricing is not publicly listed for all tiers; Professional plan is listed at $300/month and Enterprise is custom-quoted. Seat counts and overages should be confirmed with Sigma account management.
The cost of manual management
Sigma's seat model spans four account types - Admin, Creator, Explorer, and Viewer - each with distinct capability boundaries. Creator seats carry the highest per-seat cost among licensed types; Viewer is the lowest.
Pending invitations may count against seat allocations depending on plan configuration, so unaccepted invites left open can quietly consume quota. There is no native bulk CSV import for users; large onboarding batches require either SCIM or individual manual invitations.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Manual provisioning in Sigma is viable for small teams or orgs where headcount changes are infrequent. For every app that feeds into a structured joiner-mover-leaver workflow, the lack of bulk import and the email-invite dependency make manual management a bottleneck at scale.
Teams managing more than a handful of users per month should evaluate SCIM, which requires the Enterprise plan and an active SAML SSO configuration. Custom account types are available if the four default tiers don't map cleanly to your org's permission structure.
Bottom line
Sigma's manual user management is straightforward for low-volume provisioning but shows friction at scale: no bulk import, email-gated activation, and seat consumption on pending invites all add operational overhead. The Explorer/Viewer distinction requires deliberate communication to end users to avoid post-provisioning access complaints.
Teams with regular onboarding volume should treat SCIM as the target state, with manual management as a fallback for edge cases only.
Automate Sigma Computing 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.
