Trust page builder
Brand the public proof that your customers and prospects will actually read.
Brand the public proof that your customers and prospects will actually read.
What this feature is for
Trust page builder controls the app-specific identity and component selection behind a public Trust Page. It separates customer communication from internal dashboard work. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
A project, a verified domain or slug, brand assets, and evidence sources safe for public display.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Set the identity, select components, preview the result on mobile and desktop, publish, and send the URL through a customer review process.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
The builder should show the public URL, component status, evidence freshness, and last published time. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
If a component is stale, fix the source monitor before hiding the timestamp. If a brand asset fails, use a safe fallback and keep status legible.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Use the builder with Trust Page, Reports, and Reliability Score. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.