Help
Find the product route and the next documented action from inside the dashboard.
Find the product route and the next documented action from inside the dashboard.
What this feature is for
Help is the in-product route directory and guidance surface for teams that need orientation without leaving the workspace. 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
The question you are trying to answer and the app or workspace context it concerns.
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
Search the route directory, open the matching outcome hub, and follow the related documentation link for setup or troubleshooting.
- 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
A useful help result names the destination, capability, plan boundary, and next action. 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 route is missing or the explanation is stale, send feedback with the exact path and expected behavior.
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 Help with Docs, Feedback, and Operator when the right route is unclear. 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.
