> 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/help-center/help-topics/data-api-sdk/account-config-environments-and-going-live/scopes-permissions-config.md).

# Why does the API return a no-permissions error for a data type?

A data type is not enabled or no-permissions error usually means that data type is disabled in your dashboard configuration.

The error **`data type is not enabled, enable on the dashboard`** (or **`You do not have permissions for this data category`**) usually means that data type is disabled in your dashboard configuration.

**Open the data types / scopes settings above your configured Sources and enable the categories you want.** The setting is per environment. See [customising data types](https://docs.tryterra.co/unified-api/integration-setup/customising-data-types).

**Users who connected before you enabled the type may need to reconnect once.** Terra builds the permissions it asks a provider for from the data types enabled when the user connects. Where a provider has a separate permission for that data type, for example TrainingPeaks planned workouts, a connection made earlier never requested it, so the user's existing grant doesn't include it. Reconnecting shows the new permission prompt, and new users get it automatically.

Separately, each provider integration has a fixed set of required OAuth scopes (mostly identity and offline-access), pre-selected in the provider's consent UI. If an end user deselects them, the connection fails with missing-scope errors. Surface a notice asking users to leave all permission boxes ticked during authorisation.