Administration
The day-to-day admin surface: where to manage users, tune settings, watch system health, and keep your instance up to date.
#Administration
Everything you need to run an EmuView instance day to day lives in three areas of the dashboard. This section covers what each one does and how they fit together.
#The three admin areas
| Area | Where | What you manage |
|---|---|---|
| System | Sidebar → System | Health dashboard, live monitor, resource usage, access inspector, version & updates |
| Auth | Sidebar → Auth | Users, roles & permissions, API keys, crews |
| Settings | Sidebar → Settings (bottom) | Instance configuration — branding, security, sign-in, cache, webhooks, AI, and more |
Provisioning and deploying the instance itself is covered separately in Self-hosting — this section assumes your instance is already running.
#Who can administer
Access to every admin area is governed by the same role-based permissions as your data:
- super_admin — full access to everything, including other admins
- admin — manages users (below admin), roles, settings, schema, and system tools
- Custom roles — grant exactly the admin permissions you want (for example, a support role with
system/users:readonly)
The first account, created during setup, is a super_admin. Everything else is up to you.
#A quick tour
- Users & roles — create accounts, assign roles, shape permissions, and verify who can see what
- Settings — how configuration works (env overrides vs the UI) and what's configurable
- Monitoring — the health dashboard, live monitor, usage metrics, and audit log
- Backups — export and import your data
- Updates — the version card, update channels, and the Update button