Using NasDash

Authentication and Roles

Administrator, readers, public mode, sessions, and allowlists.

Administrators manage settings, users and mutations. Readers receive a filtered configuration and permitted read access. Configure accounts in Settings → Users and access, then verify the result with an actual reader session.

Fresh installations are private and create only admin. The first-start guide replaces the setup code with a new administrator password. Switching to public mode in the guide or Settings creates viewer if missing, initially allowed to read every page and widget. Its random password is never printed. Restrict its permissions in Settings → Users and access, and set a password there only if someone should sign in as viewer. Existing accounts and permissions are retained.

Principals and allowlists

In public mode, anonymous requests use the stored viewer account’s permissions. In private mode they receive 401. Authenticated readers use their current stored role and permissions; administrators have full reads. A deleted user’s old token receives 401 in either mode. allowedTabs and allowedWidgets restrict tabs and widget types: for compatibility, an empty list means unrestricted access within that list. An API resource is allowed when at least one mapped tab or widget is allowed. Hiding a button is not an authorization check.

Backend resource mapping

ResourceTabsWidgets
Service pingdashboardquickstats, networkgraph
Machine metricsdashboarddevices, quickstats
Calendar—calendar
Network topologynetworksnetworkgraph
Tailscalenetworkstailscale
Docker container listdocker, networksdockercontainers
Docker details, logs, images, volumesdocker—

Current content widgets also require their permission family: DNS, Media (including Music and Downloads), Photos, Custom API, VPN or UPS. Grant the required widgets in Settings → Users and access and check a reader session.

Mutations require an administrator and permission from the selected provider. The setting that shows Start/Stop buttons in widgets controls presentation, not API authorization. A socket proxy additionally limits permitted API methods.

Configuration and revocable sessions

GET /api/config returns a cloned, filtered configuration without changing the cached server copy. Credentials are masked for all principals. Readers also lose secret categories, disallowed resources, daemon URLs/socket paths and integration credentials. Legitimate permitted service links remain usable. Changing password, role or allowlists increments sessionVersion; subsequent requests reject stale tokens and require a new login. Legacy tokens without this claim use version zero. Keep persisted keys and any existing environment secret stable; see environment variables and backups.

Use All, selected entries or None explicitly when editing access. None denies that list; legacy empty lists retain their unrestricted meaning for compatibility. Machine widget types share a machine-data permission: hiding CPU while allowing another machine widget does not restrict individual sensor values. Verify the resulting page and API access using a separate reader session. The private calendar feed URL stays on the server; readers receive events, not its access token.