Summary and recommendation
Mindtickle 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.
Mindtickle's user management lives at Admin Panel → Users & Groups → User Management (https://app.mindtickle.com/admin/users).
Super Admins hold full platform authority, including billing and org-level integrations;
Admins operate within a scoped subset of those controls.
Managers and Learners sit below that, with Learners consuming a licensed seat only while active.
The permission model is hybrid: four predefined system roles plus configurable scopes that can be narrowed to specific groups, divisions, or content categories.
Like every app in a mature SaaS stack, Mindtickle supports custom roles for granular control over content creation, reporting, and program administration rights.
Quick facts
| Admin console path | Admin Panel → Users & Groups → User Management |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Super Admin | Full platform access: manage all users, roles, content, integrations, billing settings, and org-wide configurations. | Only Super Admins can assign or revoke the Super Admin role; there must be at least one Super Admin at all times. | |||
| Admin | Manage users, groups, content, and programs within assigned scope; cannot access billing or org-level SSO/SCIM settings. | Cannot modify Super Admin accounts or access billing/subscription settings. | Admin scope can be restricted to specific groups or divisions depending on org configuration. | ||
| Manager | View and manage direct reports' progress, assign content, run reports for their team. | Cannot create or delete users; cannot access org-wide analytics or content library management. | Manager visibility is limited to their direct reporting hierarchy; cross-team visibility requires explicit group assignment. | ||
| Learner (User) | Access assigned programs, missions, and content; complete assessments; view own progress. | Cannot access admin panel, manage other users, or view org-wide reports. | Learners consume a licensed seat; deactivated learners do not consume a seat. |
Permission model
- Model type: hybrid
- Description: Mindtickle uses a set of predefined system roles (Super Admin, Admin, Manager, Learner) combined with configurable permission scopes that can be applied per role. Admins can create custom roles with specific permission combinations for more granular access control.
- Custom roles: Yes
- Custom roles plan: Not documented
- Granularity: Role-level permissions can be scoped to specific groups, divisions, or content categories. Granular permissions include content creation, reporting, user management, and program administration.
How to add users
- Log in as Super Admin or Admin.
- Navigate to Admin Panel → Users & Groups → User Management.
- Click 'Add User' or 'Invite User'.
- Enter required fields: First Name, Last Name, Email Address, Role.
- Optionally assign the user to Groups and set a Manager.
- Click 'Save' or 'Send Invite'. The user receives an email invitation to set their password.
Required fields: First Name, Last Name, Email Address, Role
Watch out for:
- Email address must be unique across the org; duplicate emails are rejected.
- Users added manually receive an email invite and must activate their account before they can log in.
- If SSO is enforced, manually added users may still need to authenticate via the configured IdP on first login.
- Group assignment at creation time is optional but recommended; ungrouped users may not receive program assignments.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Yes | Admin Panel → Users & Groups → User Management → Bulk Upload (CSV) |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Mindtickle's admin UI centers on deactivation for interactive users, while its SCIM surface includes delete-style lifecycle operations. Public documentation does not support a single universal delete rule across every workflow, so removal behavior should be treated as tenant- and path-specific.
- Log in as Super Admin or Admin.
- Navigate to Admin Panel → Users & Groups → User Management.
- Search for or locate the target user.
- Click the user's name or the action menu (⋮) next to their record.
- Select 'Deactivate User'.
- Confirm the deactivation in the dialog prompt.
| Data impact | Behavior |
|---|---|
| Owned records | Content and programs created by the deactivated user remain in the platform and are accessible to admins. |
| Shared content | Shared content and program assignments remain intact; other learners' progress on shared content is unaffected. |
| Integrations | SCIM-provisioned deactivation via IdP triggers the same deactivation state as manual deactivation. |
| License freed | Deactivated users no longer consume a licensed seat; the seat becomes available for reassignment. |
Watch out for:
- Deactivated users can be reactivated by an Admin or Super Admin; historical progress data is restored upon reactivation.
- Deactivation via SCIM (IdP) is the recommended method for organizations using automated provisioning to ensure consistency.
- Deactivating a Manager does not automatically reassign their direct reports; admins must manually update reporting lines.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Licensed User (Learner/Active Seat) | Full access to assigned programs, missions, assessments, and content. Counts against contracted seat total. | |
| Admin/Manager Seat | Administrative or managerial access; whether these consume the same seat pool as learners depends on contract terms. |
- Where to check usage: Admin Panel → Users & Groups → User Management (filter by Active status to see current seat consumption); org-level seat usage may also appear under Admin Panel → Settings → Subscription or via account manager reporting.
- How to identify unused seats: Filter the User Management list by 'Last Login Date' or 'Last Active' to identify users who have not logged in within a defined period. Deactivating these users frees their seats.
- Billing notes: Pricing is not publicly listed; contracts are custom. Pricing seed data suggests ~$30–50/user/month at business tier and ~$92k average annual contract at Enterprise. Seat counts and overages are governed by individual contract terms. Contact Mindtickle account management for seat reconciliation.
The cost of manual management
Every app that relies on manual provisioning carries the same hidden overhead: an admin must individually add, assign, and deactivate each user, and Mindtickle is no exception. Ungrouped users silently miss program assignments, and deactivating a Manager does not cascade to their direct reports - both gaps require follow-up admin work.
Seat costs compound the risk. Identifying unused seats requires manually filtering the User Management list by Last Login Date; there is no automated dashboard for this.
At an estimated ~$30–50/user/month at business tier, unreviewed inactive accounts translate directly into wasted spend.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Manual provisioning is viable for small or slow-moving orgs where user volume is low and change frequency is minimal. The four-role hierarchy is clear enough to administer without tooling, and the deactivation flow is straightforward for individual offboarding.
For any org managing every app in a growing stack with regular onboarding cycles, multiple divisions, or a need to audit seat consumption reliably, the manual approach introduces compounding risk: missed deactivations, ungrouped users, and no automated inactive-seat detection. SCIM provisioning via an IdP is the more defensible path at scale.
Bottom line
Mindtickle's manual user management is functional but labor-intensive at scale. Every app in a growing stack demands the same admin attention, and Mindtickle's lack of an automated inactive-seat dashboard means seat waste accumulates silently.
The hybrid role model offers real flexibility, but that flexibility requires deliberate configuration - ungrouped users, unreconciled Manager hierarchies, and parallel SCIM/manual workflows each introduce drift that only an admin can catch and fix.
Automate Mindtickle 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.
