When an organisation joins Secure Report, its dedicated intake site is provisioned automatically: an isolated instance is created, its address is published, the first-boot setup runs, and the generated credentials are sealed with envelope encryption. Nothing needs to be installed on your side. Settings → Provisioning shows this process as a series of jobs.
Provisioning jobs

​
Reading a job

Each job lists its trigger (signup, manual, retry), its steps — container, route publishing, readiness, first-boot setup, credential storage, configuration — and where it currently stands. A failed step names the reason.

​
Retrying

Provisioning is safe to retry: choose Provision again and completed steps are effectively no-ops while the failed step re-runs. If a job fails repeatedly, contact the platform team — the failure detail on the step is exactly what they’ll ask for.
Once the site is active, provisioning has done its job. Ongoing changes — questionnaires, branding — are pushed from their own Settings tabs, not by re-provisioning.