Looker Studio Data Source Credentials and Sharing Risk Review (Defensive)
Check who can see which data through shared reports.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review sharing and credentials in Looker Studio as a defensive review of my own environment. List of reports with owner, sharing setting (private, link, organisation, public), data sources and credential type (owner's or viewer's): [REPORT_LIST]. Sensitive data in sources: [SENSITIVE_DATA]. Our policy: [POLICY]. Find reports shared by link or public that use sensitive data, reports using the owner's credentials that expose more than viewers should see, reports owned by people who left, data sources connected to personal accounts, and blended sources that bypass restrictions. Count reports by sharing setting and the share using sensitive sources. Order findings by exposure and explain in plain words who could see what they should not. Propose the smallest fix: restrict sharing to named people or groups, switch to viewer credentials where appropriate, move the source to a team-owned account, or remove unused reports. Return a table with Report, Risk, Fix and Owner, a one-week plan with owners, a message explaining the purpose, and a quarterly routine. A report that may have been exposed should be reported under our incident process [VERIFY]. Base findings on the list, note what you could not see, and do not ask for credentials.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.