Do I have to assign permissions to every user individually?

No — and you shouldn't. Create a Role (see Roles guide), grant permissions to the role once, then assign that role to each user. Per-user permission overrides exist for edge cases (one specific person gets one extra permission beyond their role), not as the default workflow.

What's the difference between Deactivate and Delete?

Deactivate keeps the user record but blocks login — their assignments, files, leads, and history stay intact. Delete removes the user entirely. Always prefer Deactivate unless you're cleaning up a never-used account. Past assignments stay attributed to the (now deactivated) user.

A user is locked out — how do I unlock them?

Edit the user → User Information tab → Account lockout — toggle off. They can log in immediately. ABP locks users after N failed attempts to prevent brute-force.

Can a user have multiple roles?

Yes — open the user → Roles tab → check multiple. Permissions are the union of all role permissions plus any per-user overrides.

Users — SigmaDSA Help

Create and manage SigmaDSA user accounts — username, password, profile, role assignment, and per-user permission overrides. Permissions guide for lockout, deactivation, and role inheritance.

The Users page (/identity/users) lists every login account in your tenant. From here you create logins, assign roles, override permissions per-user, lock/unlock accounts, and deactivate departing team members.

Users list with New user button, table, and per-row Actions highlighted — The Users list: (1) New user button, (2) user table, (3) per-row Actions (Edit / Permissions / Delete).

Create a user

Click New user

Top-right of the page. The New User modal opens with two tabs — User Information and Roles.

New User modal with tab strip, identity fields, account fields, and Save button highlighted — New User modal: (1) Tabs (User Information / Roles), (2) Username + Password, (3) Name + Surname, (4) Email + Phone, (5) Active + Account lockout toggles, (6) Save.

Fill User Information

Field	What to enter
Username	Login handle. Lowercase, no spaces. Cannot be changed later.
Password	Initial password. Share securely; user can change after first login.
Name + Surname	Display name on the file header, activity log, and notifications.
Email address	Used for password resets, notifications, and OIDC if SSO is enabled.
Phone number	Used for SMS notifications and 2FA if enabled.
Active	On = user can log in. Off = blocked but record kept.
Account lockout	Off normally; on if ABP auto-locked after failed attempts.

Switch to the Roles tab and assign

Roles tab of the New User modal with the role checklist highlighted — Roles tab: (1) Tab strip, (2) role checklist, (3) Save.

Pick one or more roles — Sales / Operations / Manager / Admin. The user inherits all permissions of every checked role. Use roles for permissions, not per-user assignments — it's drastically easier to maintain.

Click Save

The new user can log in immediately with the username + password you set. They'll receive an email if email notifications are configured.

Per-user permission overrides

If one user needs one specific permission that their role doesn't grant (rare), use Permissions from the row's Actions menu.

User Permissions modal with permission groups on the left and Loan CRM permission tree on the right — User Permissions: (1) Permission groups (Setting / Identity / Loan CRM), (2) permission tree for the active group, (3) Save.

The modal has three tabs:

Tab	What it grants
Setting management	Tenant-level settings access.
Identity management	Users, Roles, Permissions admin.
Loan CRM	The 98 product permissions — Leads, Files, Bank Logins, Sanctions, Disbursals, etc.

Inside Loan CRM, permissions are grouped: Lead Management, File Management, Bank Login Management, Document Management, etc. Each group expands to per-action permissions (Create, Update, Delete, View, ViewAll, Assign, Export).

Best practice: don't override here unless absolutely necessary. Edit the role instead so other users in the same role get the same change.

Edit / Deactivate / Delete a user

From the row's Actions menu:

Action	When to use
Edit	Update profile, change roles, toggle Active.
Permissions	Per-user overrides (see above).
Delete	Use sparingly — past assignments lose attribution. Prefer Deactivate.

To Deactivate without deleting: Edit → uncheck Active → Save. The user can no longer log in but everything they touched stays attributed to them.

Common flows

Onboard a new sales rep → New user → set username + password + email → Roles tab → check Sales → Save. Done.
Department change (sales → ops) → Edit user → Roles tab → uncheck Sales → check Operations → Save.
Employee leaves → Edit user → uncheck Active → Save. Reassign their files/leads on the Files and Leads boards.
User locked out → Edit user → Account lockout off → Save.
Specific user needs Export permission → use Permissions modal, but consider creating a new role (e.g., "Sales-with-Export") and assigning that instead.

Users