Managed configuration

Managed configuration lets the Pluraprint team roll out installation changes such as your organization name, colors, sign-in setup, and station identification methods. Operators keep using the dashboard normally. Your printers, rules, module choices, and other day-to-day settings remain part of your installation.

Agree on the change#

Ask support to review the intended result and identify any restart or maintenance needs. Branding can update during normal operation. Sign-in and identification changes require a coordinated restart; a change that includes those settings waits in full until the restart.

Support validates a draft, records a reason, and applies it to an initial installation before expanding the rollout. A saved or published change is not necessarily running yet. Support can distinguish a change awaiting restart from a rejected change or an installation that is offline. Shared profile choices and installation overrides remain attached when support edits a published change. Support can search profiles by name and choose a specific older revision without changing the installation’s overrides. If another administrator changes the draft, support must review the new values before publishing; a stale status check also blocks changes until it succeeds.

Uploaded organization logos are verified and cached with the configuration, so they remain available without Central connectivity. Logos linked from external websites still require access to those sites.

Work already underway retains the configuration it started with. Restart planning should protect ongoing printing and include checks of sign-in, agents, and a test job afterward.

Hosting and credentials#

Cloud installations can use managed configuration. On-premises installations use it only when explicitly enabled with your IT team. A comparison mode can validate proposed managed settings while your existing local configuration stays active. Intentionally disconnected installations can continue using local configuration or receive a signed configuration bundle through support.

Support checks the installed application build before enrollment. Older installations need an upgrade that includes the managed-configuration client; enabling the setting alone cannot add that support. They can keep their existing local configuration while the upgrade is planned.

Your IT team keeps the database connections, encryption keys, and local sign-in secrets in the installation’s protected bootstrap configuration. Managed drafts contain named, versioned references to approved local secrets. Support sees whether a required reference is available, never its value.

When connectivity is interrupted#

An installation with an accepted configuration can restart using that saved version while Central is unavailable. Its local database and required secret files must still be available. New remote changes wait until connectivity returns, and cloud-dependent services have their own availability requirements. Support checks saved-configuration compatibility when planning application upgrades and rollbacks, including whether the approved application build can restart without Central connectivity.

A new installation needs its first validated configuration before it starts in managed mode. It does not silently start with default settings. Configuration storage does not extend a license or provide indefinite offline licensing; discuss air-gapped requirements during hosting planning.

Correcting or reversing a change#

Support can publish the values from an earlier revision as a new, recorded change. A rollback can still require a restart, and it does not automatically reverse account or session changes that have already taken effect.

For a temporary presentation problem, your IT team can apply a restricted emergency override with a reason and expiry of no more than 24 hours. It is visible to support and returns to the accepted settings when it expires. It cannot grant permissions or alter license and connection trust settings.

Tell support before restoring an older database or moving an installation. Identity and configuration must be reconciled before new managed cloud writes resume. See backups and recovery for planning responsibilities.