Decide on access requests using the access policy

About this exercise

Four people on your team asked for system access. Decide each one using the access policy, as exactly 4 numbered lines like '1. Name - Approve / Deny / Approve until DATE - reason'. Approve only what the person's job needs, and give temporary access an end date. Plain text, under 90 words.

Common mistakes when you ask AI for this

• Saying yes to everyone. The AI sympathizes with Tom's frustration and approves with a caution. Try: Say: "Decide using the policy only. Managers can't approve admin rights."
• Forgetting end dates. The AI approves Kenji's cover access with no end date, so it stays forever. Try: Add: "Temporary access gets an end date."
• No clear decision shape. The AI writes 'probably fine' or 'consider limiting'. Try: Give the shape: "Name - Approve / Deny / Approve until DATE - reason."
• Trusting the AI to count words. AI is bad at counting. Ask for "under 90 words" and it often lands well over. Try: Ask for less than the limit and cap each line: "each line under 15 words, under 70 words total."
• Letting markdown in. AI adds bold and headings by default, and in the access tool they show up as stray symbols. Try: Add: "Plain text only, no bold, no headings."

What a strong prompt includes

• Uses the policy
• Gives decision labels
• Asks for end dates
• Says exactly how many
• Asks for plain text

Practice this now ↑

Related exercises

• Add dark mode by overriding your existing CSS variables (Coding AI · Software developers)
• Add input checks to your number guessing game (Coding AI · High school students)
• Add labels to a signup form without rewriting the page (Coding AI · High school students)
• Announce a territory change without promising comp outcomes (Sales AI · Revenue operations)
• Announce the employee assistance program in three steps (Writing AI · HR and recruiting)