> 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/environments-config-and-going-to-production/environment-isolation-config-and-data.md).

# Why are no users or connections showing in the dashboard?

The dashboard separates **testing, staging, and production** environments, and they are fully independent.

Connections, sources, provider credentials, Firebase settings, bundle IDs, and scope configuration are all configured **per environment**, with no shared configuration across them.

If you see no users or connections while teammates do, **check the environment selector**. Data created in testing or staging will not appear under production. To use different settings per environment, repeat the setup in each one.

Scope and permission configuration is stored in the database and only changes via a **manual save by an admin**. Deployments never reset it, and a change in one environment has no effect on another. See [understanding Terra environments](https://docs.tryterra.co/health-and-fitness-api/integration-setup/understanding-terra-environments).


---

# 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/environments-config-and-going-to-production/environment-isolation-config-and-data.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.