Admin accounts have only two states, “works” and “doesn’t work,” and problems appear as soon as the team grows: former employees can still log in, salespeople can see other people’s customers, and only one person can change settings. In X1, permissions use a three-layer design: roles determine what can be done, data scope determines whose data can be seen, and per-user overrides handle exceptions.

1. There Is Only One Super Admin
The first administrator created during installation is the super admin. Across the entire site, there is always exactly one, and this account cannot be disabled or deleted. It exists to ensure that there is always someone who can change settings and manage accounts.
To hand it over, click “Transfer Super Admin” on another enabled regular administrator, then enter your current password to confirm. After a successful transfer, you become a regular administrator and the other person becomes the new super admin—not “one more super admin,” but “a replacement.”
2. New Accounts Are All Regular Administrators
On the administrator management page, enter a username, password, and password confirmation to create a new account. The new account can log in to the admin panel normally, but it cannot open the administrator management page or invoke the corresponding save operations; accessing that address returns 403. To make it actually useful, you need to give it a role and permissions.
3. Roles: Determining What Can Be Done
A role is a collection of permissions. Permissions are registered by module; for example, articles, mall orders, purchasing, and the POS each have their own permission points. The four POS permissions are typical: pos.use to create orders, pos.manage to manage devices, pos.refund to issue refunds, and pos.reprint to reprint receipts.
When assigning permissions to a role, it is recommended to split them by job function: give customer service only conversation and member viewing permissions, sales order and lead permissions, warehouse staff inventory and purchasing permissions, and finance transaction and reconciliation permissions. Keep the number of roles within the number of job functions; this is easier to maintain than one set per person.

4. Data Scope: Determining Whose Data Can Be Seen
A role also has a “Data Scope”:
- All: Can view orders, members, and leads across the entire site; suitable for owners and finance;
- Only Own: Can view only data where the salesperson is the current account; suitable for sales and customer service.
When “Only Own” is selected, queries for orders, members, and leads automatically add the condition “salesperson = current account,” and lists, exports, and details are all subject to the same restriction. This is not a hidden menu; it is data-layer filtering. You can also avoid narrowing the role as a whole and instead grant only a specific “view only own customers” permission point (member.own), depending on your team’s habits.
5. Per-User Overrides: Handling Exceptions
Someone will always need one more permission than others, but it is not worth creating a new role for one person. Such exceptions can be handled with permission overrides on an individual administrator: add one permission or remove one without affecting the other permissions in that person’s role. When the person leaves, delete the override; the role itself does not need to change.
6. Disabling, Resetting, and Transferring
Regular administrators can be disabled: after disabling, they cannot log in, and already logged-in sessions are invalidated immediately, without waiting for a timeout. Reset passwords must be at least 8 characters. After a reset, all sessions for that account are invalidated, and the user must log in again with the new password. The system does not store the old password, and a reset cannot be undone. All such operations are written to the admin change log and are protected by CSRF and rate limiting.
7. Common Pitfalls
- A newly created administrator sees nothing after logging in: no role means no permissions; create the role first, then assign it.
- Sales can see other people’s orders: the role’s data scope is “All”; change it to “Only Own.”
- Old accounts are suddenly restricted after an upgrade: accounts created before the role feature went live have an empty role, and the system maintains the pre-upgrade permissive behavior; when restrictions are needed, explicitly assign a role to them.
- After disabling an account, it can still perform operations: disabling affects only that account; when multiple accounts are shared, handle each one individually.
- Want to delete an administrator directly: there is no deletion, only disabling; this is to preserve audit and historical record ownership.
Summary
Remember the three layers of permission design: roles govern “what can be done,” data scope governs “whose data can be seen,” and per-user overrides govern “exceptions.” Keep the super admin unique and transferable; when someone leaves, disable rather than delete so that audits have a traceable record.