Admin Users

Admin Users lists the SolaHR sign-in accounts that belong to your organization and lets you switch an account off or on, correct its name or email, set a SolaHR password, or add a new account. The page header reads Administrators — "Manage workspace administrator accounts".

Use it when you need to stop someone from using SolaHR straight away (for example on their last day), or to tidy up an account. It is an Owner and SolaHR Administrator tool.

This page manages the account, not what the person can do:

Where to find it

Who can do what

A few protected system accounts cannot be edited, disabled or have their password reset by anyone.

How sign-in works

People sign in to SolaHR through Solavel. SolaHR has no sign-in form of its own: the first time someone opens SolaHR from Solavel, SolaHR creates their account here automatically, using their name and email from Solavel.

This has three consequences:

• The list fills itself. Everyone who has opened SolaHR for your organization appears here, whatever their role.
• Name and email follow Solavel. Each time the person signs in through Solavel, SolaHR refreshes the name and email from Solavel. An edit made here lasts only until their next sign-in, so make lasting changes in Solavel.
• The SolaHR password is separate. A password set or reset here is not the person's Solavel password and is not used when they sign in through Solavel. It applies only to tools that sign in to SolaHR's API directly with an email and password.

The Status switch is different: it is SolaHR's own, and it sticks. A disabled account stays disabled even if the person signs in through Solavel again.

Screen tour

• Header: Administrators — "Manage workspace administrator accounts", with New Administrator (top-right).

• Table, sorted by name, 20 accounts per page:

  Column	Meaning
  Name	Account name, in bold
  Email	Sign-in email
  Status	Active (can use SolaHR) or Inactive (blocked)
  Date	Date and time the account was created in SolaHR — usually the first time the person opened SolaHR
  (actions)	Edit, Toggle Status, Reset Password

• Pagination under the table: the range shown, the total, and page buttons.

• Empty state: "Nothing here yet — No records match the current view."

There is no search box, filter, export or bulk action on this page.

Add an administrator

1. Click New Administrator (top-right).

2. Fill in the dialog:

   Field	Required	Rules	Notes
   Name	Yes	Up to 255 characters
   Email	Yes	A valid email that no other SolaHR account uses	Otherwise "The email has already been taken."
   Password	Yes	At least 8 characters	SolaHR-only password (see How sign-in works)
   Confirm Password	Yes	Must match Password

3. Click Save in the dialog footer.

Result: the account is created Active, linked to the current organization, and you see Updated successfully.

An account created here has no Solavel identity, so it cannot open SolaHR in the browser and does not appear on Team access. To give a person access to SolaHR, invite them in Solavel instead.

Edit an account

1. Click Edit on the row.
2. Change Name or Email.
3. Leave Password and Confirm Password empty to keep the current SolaHR password, or fill both (at least 8 characters, matching) to set a new one.
4. Click Save. You see Updated successfully.

Remember that the person's next sign-in through Solavel brings back the name and email stored in Solavel.

Disable or enable an account

1. Click Toggle Status on the row.

2. A confirmation dialog opens with the person's name:

   Current status	Dialog title and message	Confirm button
   Active	Disable administrator — "Disable this administrator's access. Their records will remain unchanged."	Disable administrator
   Inactive	Enable administrator — "Restore this administrator's access under their assigned permissions."	Enable administrator

3. Click the confirm button, or Cancel.

Result: Updated successfully, and the Status badge changes.

What disabling does:

• On their next click in SolaHR the person is signed out and sees that their account is disabled. Their API tokens stop working.
• It applies to the person's SolaHR account as a whole, so they are blocked from SolaHR in every organization they use it in.
• It does not touch their Solavel account, their other apps, their role in Solavel or their Team access scope.
• Nothing they created (attendance, leave decisions, payroll runs) is changed or removed.

You cannot disable your own account; the attempt is refused with Action could not be completed.

Enabling restores access with whatever role and scope the person currently has.

Reset a password

1. Click Reset Password on the row.
2. Enter Password and Confirm Password (both required, at least 8 characters, must match).
3. Click Save.

Result: Updated successfully. The SolaHR password changes and every API token the person had is revoked, so any connected tool must sign in again. Their Solavel password is not changed; to change that, the person uses Solavel's own password reset.

Statuses

There is no delete. To remove someone from your organization, remove them in Solavel; the SolaHR account stays in the list for history.

Worked examples

Quick example: last working day

Al Noor Trading LLC's payroll clerk, Yousef Karim, leaves on 30 September.

1. At 17:00 the owner opens System → Admin Users.
2. On Yousef's row they click Toggle Status.
3. The dialog Disable administrator names Yousef Karim. They click Disable administrator.
4. Updated successfully; Yousef's status is Inactive.

Yousef's open SolaHR tab signs him out on his next click. His past attendance entries and the payroll runs he created stay as they were. The owner then removes him from the organization in Solavel.

Full example: a returning employee and a renamed account

1. Sara Khan went on six months' unpaid leave in March; the owner disabled her account then. She returns on 1 October as HR Manager.
2. The owner opens Admin Users, finds Sara (status Inactive), clicks Toggle Status and confirms Enable administrator. Status: Active.
3. In Solavel, the owner checks Sara's SolaHR role is HR Manager. In Team access her previous scope (Sales and Warehouse) is still there, so she sees those employees as soon as she opens SolaHR.
4. Sara has married and now uses sara.haddad@alnoortrading.ae. The owner first clicks Edit here and changes the email, but on Sara's next sign-in the email goes back to the old one: the email comes from Solavel. The owner updates the email in Solavel, and the next sign-in brings the new email into SolaHR.
5. The company's time-clock integration signs in to SolaHR's API with a service account, timeclock@alnoortrading.ae. After a security review the owner clicks Reset Password on that row, enters a new 16-character password twice and clicks Save. The integration's old token stops working at once, and IT updates it with the new password.
6. Every step above is recorded in the Audit Log with the owner's name, the time and the IP address. Passwords are never shown there.

How it connects

Messages you may see

Tips and common problems

Related

• Team access
• Settings
• Audit Log
• Getting started
• Team (Solavel)
• Invitations (Solavel)
• Application roles (Solavel)