# Go-live checklist
URL: https://docs.awellhealth.com/docs/design-care-flows/go-live-checklist

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



Promotion brings the care flow across, but not the environment configuration. Work through this in
**Production** before the first patient, and after any first-time promotion.

## Branding and hosted pages [#branding-and-hosted-pages]

* **Branding.** Set organization-level branding, such as logos and colors, in Production. See
  [Administer & secure](/docs/administer-and-secure).
* **Custom domains.** Apply custom domain settings for Hosted Pages in Production. See
  [Embed & host](/docs/embed-and-host).
* **Hosted Pages link.** Configure the hosted pages settings in Production *after*
  [publishing](/docs/design-care-flows/publish-set-your-care-flow-live) the flow.

## Platform configuration [#platform-configuration]

* **Identifier systems.** Configure these manually in Production. The name and system must match
  Sandbox exactly, or patient lookups by identifier fail with no error.
* **File upload settings.** Where the flow collects files, configure file storage in Production. See
  [Collect files and images](/docs/design-care-flows/file-upload).

## Integrations and API configuration [#integrations-and-api-configuration]

* **API keys.** Production needs its own; Sandbox keys don't work there, by design.
* **Webhook endpoints.** Point them at production endpoints, not the test ones used while building. See
  [Automate with events](/docs/automate-with-events).
* **Extension configuration.** Anything configured per environment, such as the email provider account
  behind [Send email](/docs/design-care-flows/send-email-notifications), needs setting up again.

## Test scenarios for an API integration [#test-scenarios-for-an-api-integration]

Where another system creates patients or starts care flows through the API, run this sequence in
Production before going live — deliberately the smallest path that touches everything.

1. **Create a patient** through the API. Nothing else can be tested without one, because a care flow
   cannot start without a patient.
2. **Add baseline information** to that patient, at least five items, covering more than one field type.
3. **Start a care flow** for them.
4. **Update the baseline information** and confirm the change lands.
5. **Stop the care flow** through the API.

Run it against Sandbox first, then repeat in Production with production keys. See the
[API reference](/api-reference).

## Nothing here fails with an error message [#nothing-here-fails-with-an-error-message]

Every item here works in Sandbox and is missing in Production until someone sets it up. Verify each one
rather than assuming it carried across.

## Next steps [#next-steps]

Once live, running the flow day to day is covered in [Care delivery](/docs/run-care-flows).