TalentLMS User Management Guide

• Model type: hybrid
• Description: TalentLMS uses a fixed set of built-in roles (Administrator, Instructor, Learner) as the foundation. On paid plans, admins can create custom user types derived from Instructor or Learner base roles, toggling specific feature permissions on or off. Branch-level admin roles are also available for multi-branch setups.
• Custom roles: Yes
• Custom roles plan: All paid plans (Core and above)
• Granularity: Feature-area toggles within the scope of a base role (Instructor or Learner); not fully attribute-level.

1. Log in as Administrator.
2. Navigate to Users in the top navigation bar.
3. Click the 'Add user' button (plus icon).
4. Fill in required fields: First name, Last name, Email, Username, Password.
5. Optionally assign a User type, Branch, and Groups.
6. Click 'Add user' to save.

Required fields: First name, Last name, Email, Username, Password

Watch out for:

• Username must be unique across the platform; email and username can differ.
• Users added manually receive a welcome email by default; this can be suppressed in settings.
• Adding a user immediately consumes a registered user seat regardless of whether the user has logged in.
• SSO-provisioned users may be created automatically on first login if JIT provisioning is enabled.

• Can delete users: Yes
• Delete/deactivate behavior: TalentLMS supports both deactivation and permanent deletion. Deactivating a user suspends their access and removes them from the active seat count while preserving all their data and history. Deleting a user permanently removes their account and associated data from the platform. Official docs confirm both options are available from the user's profile or the Users list.

1. Navigate to Admin dashboard → Users.
2. Locate the user via search or browse.
3. Click the user's name to open their profile.
4. Click the 'Deactivate' button (or use the status toggle).
5. Confirm the action when prompted.

Watch out for:

• Deleted users cannot be restored; all their progress and records are permanently lost.
• Deactivated users can be reactivated at any time, restoring full access and historical data.
• If a deleted user's email is re-used to create a new account, the new account has no history from the previous account.
• Bulk deactivation or deletion is possible via the Users list by selecting multiple users.

• Where to check usage: Admin dashboard → Account & Settings → Subscription (shows current registered user count vs. plan limit)
• How to identify unused seats: Navigate to Admin dashboard → Users; filter by 'Last login' date to identify users who have never logged in or have not logged in recently. Deactivating these users frees seats.
• Billing notes: Plans are priced by maximum registered user count, not by monthly active users. Deactivated users do not count toward the seat limit. Upgrading to a higher user-count tier is required if the limit is reached. Annual billing provides approximately 20% discount versus monthly billing.

Seat limits are based on maximum registered users, not monthly active users, so every app account that hasn't been deactivated counts against the plan ceiling regardless of login frequency. Admins report unexpected seat exhaustion because inactive-but-not-deactivated accounts silently consume capacity.

Deactivating a user removes them from the seat count while preserving all training history - deletion is permanent and erases course completion records, which creates compliance risk.

Bulk deactivation is available from the Users list, but identifying stale accounts requires manual filtering by last login date. There is no automated idle-user report; the process is a recurring manual task.

Community evidence is not specific enough to quote or summarize yet for this app.

TalentLMS manual user management is practical for teams with low-to-moderate provisioning volume and an existing SSO setup. The deactivate-vs-delete distinction is operationally important: deactivation is reversible and preserves records; deletion is not.

Every app account - Admin, Instructor, Learner, or custom type - counts as a registered seat, so governance hygiene directly affects plan costs.

For organizations running multi-branch structures, branch-level admin roles add a layer of delegation without granting full platform access. Custom user types require cloning a base role and are bounded by that role's permission ceiling, which limits flexibility for edge-case access patterns.

Bottom line

TalentLMS gives administrators a workable manual provisioning path with clear role boundaries and a seat model that rewards active deactivation hygiene.

The platform's inclusion of SSO and SCIM on all paid plans means every app in a connected identity stack can benefit from automated provisioning without requiring an enterprise upgrade.

The primary operational risk is conflating deactivation with deletion - a mistake that is irreversible and can create compliance gaps - so teams should establish a documented offboarding policy before scaling user volume.