Manage legacy administrator profiles

Fusion Owned License is end of life; these instructions describe existing legacy installations, and labels can vary by build.

Add an administrator account

Open **Settings > System Administrator > Add New Admin** and complete:

- **Username**: a unique username for the new account.

- **Password**: the new account's password.

- **Assign role**: its access group.

- **Language** and **Template**: the account's interface preferences.

Use an individual account for each person. These controls affect the legacy Fusion installation; they do not assign the protected Administrator role in DHRU V2.

Set administrator roles

Open **Settings > System Administrator > Administrator Roles** to create roles and allow or restrict access to sections. An administrator with full access can create users, reset passwords, activate or deactivate accounts, and manage the system. Assign the access required for the person's work.

Update the profile

The legacy **My Account / Admin Profile** form contains:

- **Username**: displayed but cannot be edited.

- **First Name**, **Last Name**, **Contact No**, and **Email**: profile and notification details.

- **Assign Role**: select an existing role or choose **Add New role**.

- **My Warehouse**, **Status**, **Language**, **Template**, and **Theme**: warehouse, login status and interface defaults; **Theme** offers Light or Dark.

- **Support Department** and **Live Help Department**: departments assigned to that staff member.

- **Allow Reject order after Success**: allows or disallows rejection after a successful order. Enable this consequential permission only for the intended role.

- **Sales Report in EMail**: daily sales-report emails.

- **Support Ticket Signature**: the signature used in support replies.

If a department or notification is missing, check the relevant profile field rather than granting full access.

Password, app login and API controls

Use **Password change** to change your own login password. In **Install App**, the legacy **Your Password** form generates a QR code for quick mobile-app login; create it only on your own protected installation and keep the QR code private.

The **API** area lists **API Key**, **API IP**, and **API Allow**. Keep keys private and retain the intended IP restrictions. The **.Htaccess Protection** form documents a password restriction that rejects special characters; treat that as a legacy form limitation, not a reason to weaken or reuse your main administrator password.

Two-step verification

Open **My Profile > 2 Step Verification** for the documented Google Authenticator setup. The archived article identifies this page but does not provide text instructions for its QR-code and confirmation fields. Follow the on-screen enrollment controls in your build, and keep authenticator secrets and recovery information private.