Settings

What this feature is for

Settings is the administrative boundary for the workspace. It is where owners manage API keys, account preferences, billing context, and safe defaults. 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

Workspace-owner access and a clear reason for every administrative change.

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

Make one change at a time, review the confirmation, rotate keys when access changes, and record the operational reason in your team’s change process.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

Administrative actions should show actor, timestamp, changed object, and resulting state. 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

Never share an API key through chat or commit it to source. Revoke keys that no longer have a clear owner.

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 Settings with API & MCP, Usage, Connections, and Activity. 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.