Managed settings

Settings come from the server

The portal does not keep a second hand-written settings catalogue. It requests the installed server’s versioned WebAdmin schemas, so available sections, fields, choices, and help text match that server and its installed modules.

Stage changes

Open a section, edit supported form or table fields, and add the change to the pending summary. You can collect edits from several sections before creating one Save Changes plan.

• Text, numbers, choices, booleans, and supported table rows use the server’s own validation.
• Password and file fields use end-to-end encryption with Core 8.1.225 or newer. Leave them empty to keep existing values. Files are limited to 64 KiB each.
• For shared folders, choose Permissions for that folder, select a user or group, then review and apply.
• Specialized native WebAdmin pages remain local until they receive a narrow managed operation.

Review and apply

1. Build a server-generated plan from the pending changes.
2. Review impact, verification, and recovery guidance.
3. Confirm the exact plan before it expires.
4. Follow durable apply progress and postcondition evidence.

If a resource generation changes after review, the stale plan is refused. Retrying an accepted operation cannot silently run it twice.