Add and maintain users
Add or import workspace accounts, maintain profiles, manage sign-in and account status, and verify access.
Table of Contents
Use Users to add workspace accounts, review sign-in and access information, update names, and suspend or reactivate accounts. Add one person at a time or use Bulk import to create accounts from a CSV file.
Before you begin
- You need permission to view, create, or update people for the task you are performing. Account activation, authentication, and access-management actions require their own permissions.
- Confirm the person's business email, intended username, and whether their account should be maintained manually, by directory sync, or through HR import.
- Check whether the person will sign in with a password or your organization's single sign-on (SSO). Do not create a duplicate account to resolve a sign-in issue.
1. Find a person or check for an existing account
- Switch to admin view and open Access → Users.
- Use Search to find the person. Check their email and identity before opening a matching row.
- Use sortable column headings, Columns, and Comfortable or Compact row density to review the directory.
- Check Status, Managed by, Source, and Last Login before making changes.

| Information | What to check |
|---|---|
| Status | Active or Suspended describes account availability. No roles indicates that the person holds no role assignments. An active account alone does not prove that the person has signed in or has every permission they need. |
| Managed by | Manual, Directory sync, HR import, or System identifies how the account is maintained. Coordinate changes with the owning process. |
| Source | Identifies provenance such as Migration when available. It is separate from the current maintenance method. |
| Last Login | Shows the recorded sign-in time. Never means no sign-in has been recorded. |
2. Add one person
- From Users, select Add user.
- Enter the person's Email and Username. Use a username of 3–32 characters containing letters a–z, numbers 0–9, underscores, periods, or hyphens.
- Optionally enter First name, Last name, Function, and Job title.
- Verify the email address, then select Save. This creates the account immediately.
- Open the new person's record and verify their authentication method and access. Follow the appropriate sign-in path below.

| Sign-in method | What happens after adding the person |
|---|---|
| Password | Quantum sends an invitation with a link for the recipient to set their own password. The administrator does not choose or view that password. |
| SSO | When the email matches a configured SSO domain rule, Quantum creates an account associated with that provider. No password-setup invitation is sent; the person signs in through SSO. |
New people receive the default Member role. Review the resulting access and any required reviewer assignments separately. Creating an account does not automatically place the person in every approval group or workflow.
3. Bulk import new users
Bulk import creates new accounts. It does not update existing people. For ongoing HR synchronization, use the separate HR data-sync process linked at the end of this guide.
Prepare and upload the CSV
- From Users, select Bulk import.
- Select Download CSV template.
- Complete one row per person, using the column names below. Each file supports up to 1,000 data rows; split larger populations into batches.
- Save the file as CSV, then select Click to upload or drag and drop and choose it.
- Select Validate file. Validation checks the file without creating accounts.

| CSV column | Requirement |
|---|---|
| Required. Provide a valid, unique email address. | |
| username | Optional for bulk import. If supplied, use 3–32 characters: a–z, 0–9, underscore, period, or hyphen. It must be unique. |
| firstName, lastName | Optional name fields. |
| function, jobTitle | Optional profile information. |
Keep the template's column names. Do not add a role column; assign additional roles through access management after import.
Example:
email,username,firstName,lastName,function,jobTitle
alex.morgan@example.com,alex.morgan,Alex,Morgan,Operations,Manager
jamie.lee@example.com,jamie.lee,Jamie,Lee,Finance,AnalystReview and import
- Review each row's Status and Issues. Ready means the row passed validation; Needs fixing identifies a problem.
- Correct invalid addresses, duplicate emails or usernames, and other reported issues. Select Back to upload the corrected file and validate again.
- When the ready rows are the accounts you intend to create, select Import [number] users. This is the step that creates accounts; invalid rows are skipped.
- Review the completion summary and any skipped rows. Select Done.
- Find the imported people in the directory and verify their sign-in method and intended access.

Rows are checked again when the import runs. An account created after validation can therefore cause a row to be skipped. Correct skipped rows and import only the remaining people; re-uploading successfully created accounts will not update them.
4. Review and maintain a person
- Open the person's row in Users.
- On Overview, review their name, email, status, authentication method, and two-factor authentication status.
- To update the name, select Edit, change First name and/or Last name, then select Save. Select Cancel to discard changes.
- Use History to review recorded changes and account activity.
- Use Linked party to open the associated person record when reviewing other person data.

Edit profile does not change email, username, function, or job title. Review other person data through the linked party and use the appropriate data-maintenance process. For synchronized data, correct the authoritative source; a later synchronization may overwrite a manual change.
5. Verify access and reviewer readiness
- Review Access grants on the person's overview. Check the role, records covered, validity dates, and start scope. Roles inherited through an org unit are maintained on that unit's page.
- Review Roles & permissions in the context panel.
- Expand Effective start types to see which request types the person's combined role assignments allow them to start. Other request-type settings can still prevent a form from being offered.
- Check any Capability exceptions and separation-of-duties findings when investigating unexpected access.
- For an approver or reviewer, verify approval-group membership and workflow routing separately.

For changes to roles, scopes, or exceptions, follow Manage roles, capabilities, and access policies. For reviewer assignment, follow Configure approver groups and routing tables.
6. Manage account status and sign-in help
Open the person, select More actions, and choose the action appropriate to their status and authentication method. Available actions depend on your permissions and the person's account.

| Action | When to use it | Effect |
|---|---|---|
| Suspend | The person should no longer access the workspace. | Retains the account but removes access until it is reactivated. |
| Reactivate | A suspended person should regain access. | Restores account access immediately, subject to the person’s permissions and applicable access rules. |
| Send invitation | A password user has not yet set their password or needs a replacement invitation. | Sends a password-setup link. Any earlier invitation link stops working. |
| Reset password | An activated password user needs a new password. | The current password stops working and all sessions end. The person receives a one-time link to set a new password. |
Suspend or reactivate an account
- Confirm that you have opened the correct person and review how the account is managed.
- Select More actions → Suspend or Reactivate.
- Read the confirmation and confirm the intended action.
- Verify the updated status. For externally managed accounts, coordinate the change with the owning system.
Send a replacement invitation or reset a password
- Check Authentication. SSO users sign in through their identity provider and do not use Quantum password resets.
- For an active password account, choose Send invitation if the person has not set a password, or Reset password if they have already activated it.
- Review and confirm the action. Ask the person to use the newest email link and complete the password setup themselves.
Suspended accounts must be reactivated before invitation or password-reset actions can proceed. If a separation-of-duties rule blocks reactivation, resolve the conflicting assignments or access grants before trying again.
Help a user recover access to MFA
Check Authentication before troubleshooting. For an SSO account, the identity provider manages MFA; refer the person to your IT team. A Quantum MFA reset does not reset an identity provider's verification method.
For a Quantum password account that has lost its authenticator, verify the requester's identity through your organization's approved process. In administrator view, open Users, select the correct account, and use More actions → Reset MFA where available. Read the confirmation before proceeding. The reset removes the enrolled authenticator and ends the person's active sessions; it is separate from Reset password.
If the workspace requires MFA, the person must enroll again during their next password sign-in. Otherwise they can enroll again in Account settings. For enrollment steps, changing phones, rejected codes, and the difference between MFA and SSO, see Sign in to Quantum: MFA and SSO.
Troubleshoot common issues
| Issue | What to do |
|---|---|
| Email or username already in use | Search for the existing person, then inspect their status and authentication. Maintain the existing account rather than creating a duplicate. |
| Username rejected | Use 3–32 characters containing a–z, 0–9, underscore, period, or hyphen. Check for duplicates. |
| Invitation missing | Check whether the person uses SSO. For password users, verify the email address, junk folder, and email delivery. Send a replacement invitation when available. |
| Invitation link no longer works | Use the most recent invitation. Sending another invitation invalidates earlier links. |
| SSO sign-in fails | Check the configured provider and domain rule, the person’s identity-provider access, and account status. A Quantum password reset does not repair SSO. |
| Profile change is overwritten | Check Managed by and correct synchronized data in the authoritative source. |
| Bulk-import row is rejected or skipped | Review its Issues, correct the file, and validate again. Existing accounts are not updated by this importer. |
| Action is missing | Check your permissions and the person’s account status, activation state, and authentication method. |
| New account or reactivation is blocked by a separation-of-duties rule | Review the named conflict. For creation, ask an owner to review the default role and rule. For reactivation, resolve conflicting assignments or grants. |
| Person cannot start a form or review a request | Review Access grants and Effective start types, then check form availability, approval-group membership, and workflow routing. |
Choose the correct data-maintenance process
| Use | For |
|---|---|
| Users | Workspace accounts, names, account status, authentication support, and access review. |
| Data management → Parties | Referenced people and organizations, including person data linked to accounts. A party record alone does not establish a login. |
| HR data sync | Ongoing HR-driven data maintenance and configured account provisioning. |
| Roles and access management | Capabilities, roles, access grants, and access policies. |
| Approvers and workflow routing | Who is assigned to review or approve a request. |
See Manage party data and data-quality reviews and Configure HR data sync and SFTP intake.