How to Set Up Multiple User Accounts on Haiku
A complete walkthrough creating additional user accounts on Haiku, understanding its current multi-user maturity, and what to expect versus a fully mature multi-user Unix system.
Haiku includes POSIX-style user accounts and permissions through its Unix compatibility layer, though multi-user support historically has not been as central to Haiku’s design focus as it is on Linux or the BSDs — this walks through what’s available and how to set it up.
Step 1: understand Haiku’s historical single-user-oriented design
BeOS, and Haiku after it, were designed primarily around a single interactive user per machine — reflecting BeOS’s original positioning as a personal media workstation OS rather than a shared, multi-user server system. Multi-user support exists at the POSIX/permissions level, but the broader desktop experience (Tracker, Deskbar, most bundled applications) doesn’t center around switching between multiple simultaneous desktop sessions the way a system built primarily for shared or server use might.
Step 2: check current user accounts
cat /etc/passwd
Standard POSIX-style user account information is present and readable the same way it would be on Linux or a BSD.
Step 3: create a new user account
useradd -m newusername
passwd newusername
These standard POSIX user-management commands work as expected through Haiku’s compatibility layer.
Step 4: set appropriate group memberships
usermod -aG <groupname> newusername
Step 5: understand file permission behavior
ls -la /boot/home/
chmod 755 somefile
chown newusername:newgroup somefile
Standard Unix permission bits (owner/group/other, read/write/execute) work exactly as expected — this part of Haiku’s POSIX layer is mature and behaves predictably.
Step 6: switch users at the command line
su - newusername
This works at the shell level, the same as it would on any Unix-family system.
Step 7: understand the current state of full graphical multi-user login
Haiku’s graphical login and desktop session switching, for genuinely separate, simultaneous graphical multi-user use, has historically been less mature and less central to the project’s own priorities than its POSIX-level user/permission support — worth checking current release notes and documentation for the specific state of graphical multi-user session support in whichever Haiku version you’re running, since this is an area that continues to develop.
Step 8: use file permissions for practical single-machine, multi-account separation regardless
Even without a fully mature simultaneous-multi-session graphical experience, separate accounts with distinct home directories and file permissions provide genuine data separation between different users of the same physical machine, used sequentially rather than simultaneously — a meaningfully useful capability on its own, short of full concurrent multi-user desktop support.
Why this is worth understanding honestly rather than assuming full parity with Linux
Haiku’s BeOS heritage as a personal workstation OS, rather than a general-purpose multi-user server system, directly shaped where the project’s development effort has historically gone — POSIX-level permissions and accounts are solid and functional, while a fully-featured, actively-used simultaneous-multi-session graphical experience has not historically been where most contributor effort concentrated. Setting accurate expectations here, rather than assuming Haiku matches a server-oriented Unix system’s multi-user maturity in every respect, avoids frustration from expecting capabilities the project’s own design history and priorities haven’t emphasized to the same degree.