System administration: nodes, settings, jobs, and permissions

System management keeps video services running. A single machine may host onboarding and playback, but administrators still need to check the main service, media node, database, storage, and viewer network separately.

Task	Where to go	What to verify
Confirm control and media nodes are online	System management → Runtime	Main service, NodeAgent, MediaServer, and health endpoint agree
Change runtime settings	System management → Configuration	Preview the diff, choose the target, deploy, then read back effective values
Inspect scheduled and background work	System management → Jobs	Registration, execution result, and recent errors are distinct
Create users or change permissions	User permissions	Sign in as the target user and verify actual access
Diagnose alarms and logs	Live logs, System management	Save matching time windows from the app, agent, and media service

flowchart TB
    A["User action or background job"] --> B["AKStream.Next checks permissions and settings"]
    B --> C["MediaServer / protocol device"]
    B --> D["Database and persistent files"]
    E["NodeAgent"] --> B
    C --> F["State, alarms, and logs"]
    D --> F

Before changing a setting, identify whether it belongs to the platform address, media node, or camera itself. Saving a platform setting does not prove a camera applied it; read back the runtime state or image. A background job listed as registered does not prove its latest business run succeeded.

For first go-live, establish baselines with Security settings, Monitoring and alarms, and Backup and upgrade. Developers should use System and operations APIs rather than parsing console text.