> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/billing-account/dashboard-users-and-connections/widget-provider-list-vs-sources.md).

# Why don't widget providers match my connections?

The widget's provider list and your dashboard Sources panel come from the same place by default, but **your app can override the list per session**.

The widget renders providers from the `providers` field in your [`generateWidgetSession`](https://docs.tryterra.co/health-and-fitness-api/user-authentication/implementation-terra-widget) request if it's present, and otherwise falls back to the providers enabled on [your dashboard](https://github.com/tryterra/api-faqs/blob/main/dashboard/connections/README.md).

Two providers have extra conditions:

* **Apple Health** only appears when the call passes `use_terra_avengers_app: true`.
* **Samsung Health** only appears when the call passes a `samsung_app_url`.

To target different areas of your app, pass subsets of your dashboard-enabled providers. To get the standard behaviour, **drop the `providers` field entirely**, which is the cleanest default.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/billing-account/dashboard-users-and-connections/widget-provider-list-vs-sources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.