(feature) Add read-only access level to control panel
Introduce a central access policy that lets authenticated non-staff users view backup status pages while keeping credentials, logs, configs, and mutating actions staff-only. Hide sensitive navigation and host controls for read-only users, expose only the status API to authenticated viewers, and document the two access levels.
This commit is contained in:
@@ -131,6 +131,11 @@ Create a superuser if needed:
|
||||
sudo -u pobsync pobsync-manage createsuperuser
|
||||
```
|
||||
|
||||
The control panel supports two access levels. Django staff users can manage hosts, SSH keys, configs, retention,
|
||||
notifications, logs, and administrative actions. Normal authenticated users can view backup status pages such as the
|
||||
dashboard, hosts, runs, snapshots, schedules, purged history, changelog, and `/api/status/`, but cannot see SSH
|
||||
credentials or run mutating actions.
|
||||
|
||||
For other Django management commands on native installs, use `pobsync-manage` so the production environment file is
|
||||
loaded before Django starts:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user