Keep each site's own content and permissions in WordPress.
Prepare one client site
Choose an existing client role in Prepare handoff, add everyday tasks, support and a private guide, and review the proposed changes before applying. Brand the admin and login screens as needed. Presentation changes never grant or remove WordPress permission.
Review and reuse the setup
Export a configuration profile, then use Reuse setup on the destination. Select destination pages and images, map unavailable roles, and confirm source-site URLs. Review the changes before applying; a stale review cannot overwrite a changed workspace.
Maintain the standard
Set role defaults for how the workspace appears to different people. On multisite, use network defaults and locks. Technical teams can optionally review signed Git-based Fleet changes before applying them.
Leave a recovery path
An administrator can return to native appearance or enter safe mode. Ordinary expiry preserves the installed paid workspace and local editing. Updates, paid support and new remote Fleet changes require an active term. Activation follows Freemius rules and your site allowance. Cancelled licenses, including cancellation after exhausted renewal retries, pause paid features.