Owner arranges site setup, named workstations and operational administration. Supervisor reads the permitted readiness and operational records without inheriting Owner's setup controls. Readiness is evidence about configured checks for the stated build; a passing local or fictional test does not qualify a customer's factory, devices or receiving process.
Establish the intended site
Where Accounts offers Set up your order workspace, the Owner confirms the organisation, enters the site name, chooses the offered time zone and selects Create site. The screen creates one production site for that organisation. Creating it does not start a subscription or approve manufacturing work.
Arrange explicit OrderRun grants in Accounts. Your existing order system remains responsible for customer agreements and authorised changes. Configure the named receiving destination through its separate order-workflow controls; do not infer manufacturing approval from successful site creation.
Read the current readiness result
Open Site readiness and confirm site, build, checked time and site state. Inspect each row under Readiness checks and its explanation. If the page says the site still needs attention, retain the particular reason and have the responsible administrator resolve that check.
The destructive-retention display reports configuration, not an instruction to delete records to obtain a pass. Current source, receiver, printing, security and recovery requirements remain independent of a readiness heading.
Owner uses Enrol a named workstation for the actual station and checks the recorded result. A name is not evidence that a printer or receiving interface is physically qualified. Coordinate each station's current operator and any unfinished work before changing its use.
Interpret plan and usage information
Open the permitted Account view for plan/readiness and usage delivery. The first accepted production order counts once; amendments, retries, remakes and individual despatches do not become additional orders. The product's current plan and readiness checks still control admission.
Waiting or failed usage-delivery counts describe reporting status. Do not repeat an order action to repair reporting or treat delayed reporting as a new order. Compare the original event identity with Accounts where required.
After a restore, an Owner checks each held earlier-generation usage event against Accounts and restored records. On Site readiness, mark only the exact event actually checked, supply the Accounts lookup and reconciliation evidence reference and use Record review and permit same-event delivery. This permits delivery of the same original identity/body; it does not authorise another business event or a changed amount.
Export, pause and restore deliberately
The page's complete-export, verified-archive, pause/resume, closure and recovery controls have separate purposes. Follow records and recovery, including verification of the actual private archive and reconciliation of source, receiver, printing and usage effects.
An unresolved earlier-generation usage event prevents the recovery review from being completed. Clearing a browser form, creating another station or using the fictional workspace cannot supply the missing independent evidence. Preserve the site generation and exact event/command references when arranging help.