◆ Google Looker

Administer Looker roles

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 Maria from Marketing 'Viewer' access to the 'Campaign Performance' dashboard folder and…+
Grant Maria from Marketing 'Viewer' access to the 'Campaign Performance' dashboard folder and 'Editor' access to the 'Marketing_Data_Source' so she can build her own reports.
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 roll out the new finance dashboards, review the existing user roles for the finance…+
Before I roll out the new finance dashboards, review the existing user roles for the finance department. Suggest a refined set of roles that balances security with the ability for managers to drill down and analysts to create custom views.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentDavid from HR just asked for 'Admin' access to the 'Employee Turnover' dashboard, saying he…+
David from HR just asked for 'Admin' access to the 'Employee Turnover' dashboard, saying he needs to 'fix something urgent'.
David from HR just asked for 'Admin' access to the 'Employee Turnover' dashboard, saying he needs to 'fix something urgent'. Our policy is strict on admin roles, but he sounds genuinely stressed. I don't want to block him if it's critical, but I also can't just hand out admin. What's the best way to diagnose his actual need and grant the minimum necessary access without delaying him further?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting requests for elevated access to dashboards that could be solved by…+
I keep getting requests for elevated access to dashboards that could be solved by better-defined standard roles.
I keep getting requests for elevated access to dashboards that could be solved by better-defined standard roles. It feels like I'm constantly reacting to individual access requests instead of having a clear structure. What habit should I change to anticipate user needs and establish a more scalable and secure role administration process?
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.