Panel Network and Access

The access area lets an administrator inspect interfaces, change network addressing with a confirmation checkpoint, review firewall changes before applying them, configure time and services, manage account permissions and credentials, apply branding and licence settings, and inspect distribution qualification. Every change remains owned by the existing Panel route; these pages do not execute arbitrary host commands.

Find the controls

Safely change network or firewall access

1. Open Network interfaces at /rust/network. Inspect the active interface and network owner; there is no private-address-only restriction.
2. Save network profile stores a host tuning profile without applying it. Delete network profile removes only the saved profile, after confirmation. Trial network tuning and Measure network tuning submit reviewed, temporary tuning requests; neither implies that a performance gain has been demonstrated.
3. For DHCP addressing, review whether automatic addressing is appropriate. Use the addressing editor's Preview before Apply network profile. Reconnect before Confirm network profile; otherwise use Revert network profile or let the checkpoint restore the prior configuration.
4. Open Firewall status at /rust/system/firewall. If the policy belongs to another manager, the host firewall editor will refuse to claim it. A separate appliance firewall owner is used on LexiOS.
5. Use Preview firewall rules to inspect the generated policy difference. Review the allowed Panel source networks and TCP port carefully. Preview does not modify the host.
6. Use Apply reviewed firewall rules only after acknowledging possible lockout. The host owner requires the exact preview plan token; a pending transaction carries an automatic revert deadline.
7. Open a fresh Panel connection from the intended network. Confirm firewall rules before the deadline only after checking connectivity. If it fails, use Revert firewall rules or allow automatic restoration.
8. The guided version is Open access safely with a firewall preview at /rust/access/guides/access.firewall-safe-exposure: Inspect firewall owner, Preview policy difference, Apply after confirming lockout risk, Confirm only after reconnecting. The guide accepts a complete, reviewed policy JSON exported from the host firewall editor. The owner still checks its schema and state.

Do not treat a successful preview as permission to bypass an external firewall manager, or a successful apply as proof that remote connectivity works.

Native account and security settings

On /rust/access, Access roles shows the current authentication mode and signed-in role. The Users card provides Create account, Save account changes, and Delete account, with type and instance permissions validated by the existing account owner. Only the local root account may manage protected administrators; a regular administrator cannot override that restriction. The API keys card offers Create key, Create scoped key, and Revoke through native forms. Revoke and delete require explicit confirmation. The key is shown only in the immediate creation result.

Result vault status shows whether the result vault is configured, writing encrypted records, or unlocked. Use Enable result vault, Unlock result vault, Lock result vault, Encrypt existing results, and Disable result vault from the native page. Save recovery material before enabling encryption: existing sealed results cannot be recovered without it.

At /rust/access/settings, Model verification policy reports whether unverified models are hidden. Set model verification changes only library visibility, without deleting files. Panel layout changes whether the multi-server navigation section is shown; it does not join or leave a fleet. Changes require an administrator and a confirmation checkbox.

A viewer can inspect their access mode but cannot see or submit account, credential, vault, model-verification, layout, networking or firewall mutation forms. The native pages use standard form submission and display owner responses; no browser scripting is required for these operations.

Give a client a scoped credential, then rotate it

1. Open /rust/access/automation. Under Create client token, supply Account owner, Client label (up to 64 characters), Role, Route-family scopes (comma-separated) and Expires after days (1–3650). Prefer a read-only role and only the route families the client needs.
2. Select Create scoped token. The response presents the secret once; copy it directly to the client’s protected credential store. The Issued automation tokens inventory displays identifiers, scopes, roles and expiration, not secrets or hashes.
3. At a planned client cutover, open Rotate client token, enter Existing token ID, choose New expiry in days, check the confirmation and select Rotate token. The previous secret becomes invalid immediately. Update the client with the newly displayed secret.
4. For a credential no longer needed, use Revoke client token, Existing token ID, and the confirmation; its requests will then fail.
5. The guided version is Issue and later rotate a client token at /rust/access/guides/access.client-token: Review existing tokens, Create client credential, Rotate on the client cutover. A create-step undo revokes its token; rotating cannot restore the previous secret.

The new scoped-token API uses /api/tokens/create, /api/tokens/list, /api/tokens/rotate and /api/tokens/revoke. Credentials do not grant greater authority than their owner; they cannot administer other credentials.

Add a least-privilege user

1. On /rust/access, inspect Access roles and current users. Open /rust/access/limited-user.
2. In Create read-only account, enter User name and Initial password (at least ten characters), then check the confirmation before Create limited user.
3. The owner sets role to viewer, instance_control to false, and instances to an empty list. Return to Instance permissions to inspect assignments; change them only if explicitly required.
4. The guided version is Add a user with limited permissions at /rust/access/guides/access.limited-user: Review account policy and Create read-only user. Until an account is relied on, the guide offers a delete undo through the same account owner.

Read-only users cannot issue or rotate tokens, change the firewall, or create accounts through the access forms.

Time, services, identity and distribution

Open Clock and time zone at /rust/system/time to see synchronization status before Change time settings. Open Managed services at /rust/system/services to inspect the actual instance service state and use its existing start, stop or restart controls with the correct role. Open Host permissions at /rust/system to preview privileged helper permissions before any authorized fix. White-label branding, Brand licence, and Commercial licence each delegate to the existing validated owners; supplying a receipt is not itself proof of an entitlement.

At /rust/access/qualification, Distribution install plan displays package prerequisites, Distribution security displays security/network prerequisites, and Security qualification reports redacted checks and blockers. These reports do not install packages, change firewall rules, prove a live boot or authorize a release. The existing detailed /rust/distro and /rust/distro/security screens remain available.

Control reference

The control names and single-sentence help descriptions below are the access registry entries. Screens use the paths shown in the table above; native help markers expose the same text beside relevant controls.

Related guides

See Panel Instances for instance control and service effects, Panel Storage Backup Updates for recovery before disruptive host work, and Panel LexiOS and Secure Boot for appliance boot and trust qualification.