This 2024 feature request is now partly historical. The original poster wanted separate SMB credentials so network shares did not require an administrator account. Current ZimaOS supports that member-based sharing model.
Current ZimaOS Supports Separate Samba Members
The current ZimaOS multi-user Samba documentation lets a manager create member accounts, assign a member to a shared folder, and choose read-only or read-and-write permission. The NAS file sharing basics explains this workflow, and the authenticated SMB access adds troubleshooting for authenticated clients.
Why Separate Share Credentials Are Better Than Admin Credentials
Samba's Samba account passwords documents separate SMB account passwords and account enable/disable behavior. Using a dedicated share account limits the credentials exposed to ordinary file-sharing clients.
Samba Itself Supports Group-Style Access Rules
The upstream Samba valid users shows that valid users can include individual users and group references such as @pcusers. That proves group-based Samba authorization is technically possible at the Samba layer.
ZimaOS Current Docs Document Members, Not Permission Groups
The source user also requested reusable groups so the same permission set could be applied across multiple folders. The current ZimaOS guide documents individual member accounts and permissions, but does not document a group-management UI. Do not assume the original group request shipped just because multi-user SMB did.
Current Recommendation
- Create separate ZimaOS members for people who need recurring SMB access.
- Grant only the folders and read/write level each member needs.
- Avoid sharing the administrator credential with ordinary SMB clients.
- If you need reusable permission groups, verify current ZimaOS support before editing Samba configuration manually.
Bottom Line
The main 2024 request has been delivered: current ZimaOS supports separate member credentials for Samba shares. The second request—group-based permission management—should still be treated separately because the current official guide documents members, not an explicit groups UI.
