◆ Elasticsearch

Check user privileges

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 Elasticsearch tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCheck if Sarah from the marketing team has read access to the 'website_analytics' index and…+
Check if Sarah from the marketing team has read access to the 'website_analytics' index and write access to the 'campaign_data' index, and provide a summary of her current privileges.
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 the new intern starts on Monday, verify that their account has only read-only access to…+
Before the new intern starts on Monday, verify that their account has only read-only access to all production indices, no access to sensitive customer data, and can only view monitoring dashboards.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentJames from the operations team is reporting that he can't see the 'server_logs' index, but his…+
James from the operations team is reporting that he can't see the 'server_logs' index, but his role should grant him access.
James from the operations team is reporting that he can't see the 'server_logs' index, but his role should grant him access. He's frustrated because he needs to troubleshoot a critical incident, and I'm not seeing any explicit denials for his user. I've checked his role assignments, but I'm unsure if it's a cached privilege issue, a conflicting role, or an index pattern problem. What's the most likely diagnosis, and what's the best next step to restore his access immediately?
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 urgent requests from users who can't access data or features they believe they…+
I frequently get urgent requests from users who can't access data or features they believe they should have, leading to firefighting and delays.
I frequently get urgent requests from users who can't access data or features they believe they should have, leading to firefighting and delays. It feels like I'm constantly reacting to permission issues rather than proactively managing them. What habit should I change in how I audit or communicate user privileges to reduce these last-minute access problems and improve user self-service?
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 Elasticsearch'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.