The initial ZimaOS owner/admin username is not intended to be renamed through the supported UI or by editing /etc/passwd. ZimaOS explicitly removed username modification in the 1.2.3 release line, so changing Linux account files alone does not update the application database and permission model.
If you only need another name for a family member or shared-folder account, create a separate member account instead. If the initial owner name itself must change, plan a controlled reinitialization rather than partially renaming system files.
Why Editing /etc/passwd Does Not Work
ZimaOS account identity is not stored only in Linux's traditional /etc/passwd and /etc/shadow files. The web UI, shares, local database, and application services also track account state.
Changing only one layer can leave the dashboard and backend disagreeing about the user.
ZimaOS Explicitly Removed Username Modification
The ZimaOS 1.2.3 release notes state that changing the ZimaOS account username is no longer allowed. The same release also fixed several user-creation problems.
The current ZimaOS 1.2.3 release notes documents that boundary.
Use Member Accounts for Additional People
Current ZimaOS supports separate member accounts for family members and teammates, with independent passwords and share permissions. This is the supported way to give another person a different account name without rewriting the initial owner identity.
The ZimaOS multi-user sharing guide shows how to create, edit, and delete shared-folder member accounts.
Do Not Rename the Linux User Behind ZimaOS
Commands such as usermod, direct edits to /etc/passwd, or manual changes to the user database can break service assumptions, paths, permissions, or login state. ZimaOS is an appliance-style OS, not a generic multi-user Linux distribution.
If You Must Change the Initial Owner Name
The safest supported-style path is to back up data and AppData, then reinitialize the user/account layer or reinstall/reinitialize ZimaOS and create the desired owner name during first setup.
This is a bigger operation than a rename. Document shares, member accounts, app data, and remote-access settings first.
Password Recovery Is Not a Rename Tool
ZimaOS documentation includes a recovery procedure that removes the local user database to restart account initialization. That procedure is for lost-password recovery, not for casually renaming a healthy owner account.
Use it only when you understand the consequences and have protected important configuration.
Choose the Owner Name Carefully During Initial Setup
The current ZimaOS Get Started guide identifies the first account as the main account with owner/admin privileges. Since rename is restricted, choose a stable username during onboarding.
The setup checklist helps reduce recovery surprises.
Changing the Display Name Is Not the Same as Renaming the Account
If a current UI lets you change an avatar, profile label, or other presentation field, that does not necessarily alter the underlying account username used by authentication and permissions. Test the actual login name before assuming the identity changed.
Why a Partial Rename Can Break Shares
Samba permissions, member references, and application-side ownership can all depend on account identifiers that are not visible in /etc/passwd. A partial rename can therefore leave file access working in one place and failing in another.
Plan a Clean Rename During Reinitialization
If the username is important enough to justify a reset, inventory shares, members, AppData, and remote-access settings first. After reinitialization, recreate the owner name deliberately and verify each share before deleting any backup of the previous configuration.
FAQ
Can I rename the first ZimaOS admin user?
Not through the supported username-modification path. ZimaOS explicitly removed account username changes in v1.2.3.
Can I edit /etc/passwd and /etc/shadow?
That changes only part of the identity and can desynchronize ZimaOS services. It is not a supported rename method.
Can I create another administrator with a different name?
You can create member/shared accounts, but they are not necessarily equivalent to replacing the initial owner account.
What if I chose the wrong owner name during setup?
Back up the system and plan a controlled reinitialization rather than performing a partial Linux-user rename.
