2 ready prompts
Written for the moment this actually comes up.
Improve — make it easier to accept
+Before I send the permissions list to our security lead Aisha, frame it for action: mark any user…
Improve — make it easier to accept
+Before I send the permissions list to our security lead Aisha, frame it for action: mark any user who can change tracking or delete data, highlight service accounts without two-person approval, and propose the minimum permission levels each role (marketing, dev, finance) should keep. Include the exact steps to remove Manage Users rights safely and a template approval email.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We repeatedly have stale or excessive permissions: new hires and agencies are granted high access…
Become — change the pattern
+Permissions creep keeps happening after hires and contractors leave.
We repeatedly have stale or excessive permissions: new hires and agencies are granted high access and it never gets revoked. Where is the process failing — onboarding, offboarding, or lack of role templates? Recommend one small policy and one automated check that a two-person ops team can run weekly to keep access minimal and auditable, plus a short wording for the access removal notice that avoids politics.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other web analytics work people do in Google Analytics.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.