Bottom Line: Big Bear CasaOS User Management Does Not Provide Granular ZimaOS App Roles
The request was for users who could access only selected apps and settings without becoming full admins. The Big Bear CasaOS User Management app did not provide that role model. More importantly, it targets CasaOS account data, not the current ZimaOS authorization system.
The historical Big Bear package is built around CasaOS-oriented user-management tooling. CasaOS User Management shows the account-database approach, while the BigBearCasaOS repository provides the upstream package context.
Current ZimaOS Separates Owner/Admin Setup From File-Sharing Members
The current ZimaOS owner account says the first account is the main owner/admin account. For file sharing, ZimaOS supports separate members with Read or Read & Write access through Samba. The ZimaOS Samba members documents that model.
File Permissions Are Not the Same as App and Settings RBAC
A member who can read a shared folder is not automatically a dashboard operator, and restricting a Samba folder does not create a “Plex-only user” role in the ZimaOS administration UI. Current public documentation does not describe granular per-app/settings RBAC comparable to enterprise role systems.
The ZimaOS SMB authentication is the correct path when the actual need is “this person can access these files.”
Use Application-Level Accounts for Application Access
If someone should use Plex, Nextcloud, Home Assistant or another app without administering ZimaOS, create the user inside that application. This keeps NAS administration separate from application permissions.
For richer collaboration roles and quotas, the Nextcloud requirements is a better fit than trying to turn a CasaOS admin helper into a general RBAC layer.
Why Reusing the Big Bear App on ZimaOS Is Risky
The Big Bear tool was built around CasaOS user-management internals. Writing directly to an account database from a third-party administrative container creates upgrade and lockout risk if the schema or authentication model changes. Use native ZimaOS account/share controls where available.
If Granular Dashboard Roles Are Mandatory
Treat that as a product requirement, not a hidden Docker setting. Keep ZimaOS administration restricted to trusted admins and push end-user access into apps and shared folders until the platform publicly documents a more granular dashboard permission model.
The ZimaOS app requirements helps keep app access independent from NAS administration.
