◆ Google Looker

Manage Looker user attributes

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
See the prompt↓All Google Looker tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSet the 'Sales_Region' user attribute for David Miller to 'North America' and for Maria…+
Set the 'Sales_Region' user attribute for David Miller to 'North America' and for Maria Rodriguez to 'Europe'. Apply these changes by end of day today so their dashboards reflect the correct data.
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 update the 'Department' user attribute for the entire finance team, check for any…+
Before I update the 'Department' user attribute for the entire finance team, check for any reports or dashboards that might break if their department value changes. Flag any potential issues and suggest alternative ways to segment their data if needed.
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 new 'Project_Lead' user attribute isn't filtering reports correctly for half the project…+
The new 'Project_Lead' user attribute isn't filtering reports correctly for half the project managers.
The new 'Project_Lead' user attribute isn't filtering reports correctly for half the project managers, and Mark from engineering is complaining he's seeing everyone's projects. I've checked the attribute values, but I'm worried I misunderstood how the attribute interacts with the underlying data filters, or if there's a caching issue. What's the most likely diagnosis, and what's the quickest way to verify and fix it without causing more data confusion?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently get questions about why users can't see specific data, and it often traces back to…+
I frequently get questions about why users can't see specific data, and it often traces back to user attribute misconfigurations.
I frequently get questions about why users can't see specific data, and it often traces back to user attribute misconfigurations or overlooked dependencies. It's a constant drain on my time. What habit should I change when I set up or modify user attributes to ensure data visibility is always correct and transparent, especially when new data sources are added?
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.