Writing Permission and Access Messages
Quick start
Collect or infer:
- •Permission type (location, camera, notifications, data access, role-based)
- •Current state (requesting, granted, denied, expired)
- •Why the permission is needed
- •Impact of granting or denying
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Workflow
- •Identify permission type and current state
- •Write the headline (what access is needed)
- •Write the explanation (why and what user gets)
- •Specify available actions
- •Run the rubric check. Revise until it passes.
Degrees of freedom
- •Low: Must explain why permission is needed
- •Medium: Explanation detail varies by permission sensitivity
- •Allowed variation: Pre-request prompts optional but recommended for sensitive permissions
Constraints
- •Headline: max 60 characters
- •Explanation: max 150 characters
- •Action labels: max 20 characters
- •Always explain the benefit of granting permission
- •Never request unnecessary permissions
References
- •Templates: TEMPLATES.md
- •Rubric: RUBRIC.md
- •Examples: EXAMPLES.md