◆ Google Looker

Maintain Looker security

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGrant the new intern, Maya, view-only access to the 'Sales Performance' dashboard and the…+
Grant the new intern, Maya, view-only access to the 'Sales Performance' dashboard and the 'Marketing Spend' report group. Make sure she can't download any raw data, only see the visualizations. This needs to be done before her onboarding session at 10 AM.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I add the new 'Customer Feedback' dataset to our Looker instance, I need to ensure it…+
Before I add the new 'Customer Feedback' dataset to our Looker instance, I need to ensure it won't expose any PII. Set up a data masking rule that redacts email addresses and phone numbers from the 'Customers' table before it's accessible to any user group, even admins.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe finance team is seeing different Q3 revenue numbers in our dashboard than in their internal…+
The finance team just escalated a data discrepancy on the Q3 revenue dashboard.
The finance team is seeing different Q3 revenue numbers in our dashboard than in their internal system, and they're pressing for an answer by end of day. I've checked the SQL query, and it looks correct, but I'm worried about a potential join error or a subtle filter I missed. I can't tell them I'm not sure which source is correct. What's the most likely cause for this kind of revenue mismatch and what's the fastest way to diagnose it without causing more panic?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly getting pulled into urgent, ad-hoc access requests for dashboards and reports,…+
I keep getting last-minute requests for access changes or report permissions that disrupt my sprint work.
I'm constantly getting pulled into urgent, ad-hoc access requests for dashboards and reports, often right before a big meeting. It's making it impossible to focus on my planned development tasks. I need to get ahead of this. What habit can I change to better anticipate these needs or empower teams to manage their own standard access without my direct intervention every time?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Google Looker's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.