Pages and permissions

The operational WebUI presents pages according to the authenticated user's permissions. The page catalog and reverse-proxy routing solve different problems: a catalog entry makes a page discoverable, while a route directs its requests to an application.

Page types

Page	Purpose
DATA	Browse authorized containers and datasets
LOGS	Inspect logs with filters and pagination
SCHED	Inspect schedule definitions, runtime state and batch jobs
PROC	Inspect locally managed routines and dispatch permitted lifecycle commands
USERS	Manage identities and grants where supported
ROUTES	Manage registered application routes where supported
WORKERS	Inspect enrolled workers and their status
ACCOUNT	Manage the current user's account

Availability depends on package version, authentication mode and permissions. A hidden menu item is not an authorization boundary; the underlying API must enforce the same grants.

Integration rules

Use stable route identifiers, same-origin navigation and the existing permission model. Avoid duplicate shell navigation when embedding a page. Expiry and login handling should return the user to the intended page without placing credentials in a frame URL or message.

Validation

Use generic fixture users and disposable data. Test keyboard navigation, mobile layout, permission denial, expired sessions and callback requests. Verify mutation controls separately from read-only browsing. Screenshots for public documentation must use illustrative data.