## TL;DR
Reauthorise the data source first. This error means the connector cannot use the stored configuration for the account that owns the data source, usually after a password change, a revoked grant, or an account migration. Open the data source, reauthenticate the owner credentials, and confirm the underlying account can still reach the data the connector reads.

```text
user configuration invalid
```

## Use this when
- All charts on one data source fail with a user configuration invalid message at the same time.
- The data source owner changed their password, left, or had access revoked recently.
- Other data sources owned by other accounts on the same report still work.

## Not for this skill when
- One chart fails while others on the same source work. That is a chart configuration problem, not the connector grant.
- The underlying service itself is down for all clients. Wait for or fix the source service first.

## Steps
1. Open the report in edit mode and identify the data source behind the failing charts, noting its owner. Verify: every failing chart traces to that one data source
2. Open the data source configuration and run its authorisation or reconnect flow as the owning account. Verify: the connector reports a successful authorisation for the correct account
3. Confirm the owning account can open the underlying data directly, such as the sheet, property, or database the connector reads. Verify: the account sees the data outside Looker Studio
4. Refresh the data source fields and check that no field shows a configuration warning after reconnecting. Verify: the field list loads without errors
5. Reload the report as a viewer and confirm the charts render current data. Verify: all charts on the source display without the configuration message
6. If the owner has left, transfer the report and data source to a service or team account and reauthorise under that account. Verify: the new owner is listed and charts still render after the transfer

## Why it happens
Owner credential models concentrate risk in one grant, which is why these failures arrive with staff changes and password rotations. Moving shared reports to a team owned account, and documenting which account owns each production data source, converts a mystery outage into a routine reauthorisation. The error wording points at configuration because the connector cannot distinguish a revoked grant from a mistyped setup.

Looker Studio community and native connectors run under the data source owner credentials model by default. Charts therefore depend on one account grant staying valid. When that grant breaks, every chart on the source fails with a configuration error that names the user setup rather than the underlying service, because from the connector side the configuration it was given is simply no longer usable. Reconnecting the same account in a private window is a common false fix when the browser is signed in as a different user.

Field notes for Looker Studio and its connectors specifically. The report resource state, the data source credentials model, and the underlying service quotas together explain most incidents, and the error wording in the product is deliberately vague, so the underlying service console, such as the Google Cloud console for BigQuery, is usually where the precise cause is written down. Testing in a private window signed in as the report owner is essential, because Studio behaviour changes with which account the browser carries, and many false fixes come from testing as the wrong user.

Studio estates stay healthy when production reports are owned by team accounts with documented access, and when the heaviest reports sit on extracted or materialized data rather than live queries. The tool makes live connections so easy that estates drift into hundreds of live charts against shared quotas, and the failures then arrive as a group at the busiest moment. A short register of production reports, their owners, and their data sources turns quota and credential incidents from archaeology into administration.
## Variants and edge cases
### Looker Studio user configuration invalid connector reauthorise
The reauthorisation phrasing naming the actual repair.
### Data Studio data source owner credentials invalid all charts
The owner account variant after a password or staff change.
### Looker Studio connector configuration error transfer owner
The transfer variant when the original owner has left.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_u_loeo1GNCxH4hMetuzYBA