Connect access to a visible task
Identify why the product needs the permission and what changes when it is granted. A generic “improve your experience” explanation may not help someone understand a request for location, contacts or notifications.
Use the platform's current permission implementation and requirements. Do not replace system controls with an imitation that suggests consent was granted. Avoid promising that every denial can be reversed within the app.
Review the request flow
| Question | What to specify |
|---|---|
| Purpose | Which supported task needs the access? |
| Timing | When does the user encounter that task? |
| Scope | What access is actually required? |
| Decline | What useful path remains? |
| Follow-up | When, if ever, is another explanation appropriate? |
If access is essential to a specific feature, explain that limitation accurately without implying the whole app requires it when it does not.
Worked example: notifications before value
Illustrative example: a planning app requests notification access before the user creates a plan. The customer does not yet know what reminders would help with. An explanation connected to a supported reminder task provides more context than a broad first-launch prompt.
Evaluate useful reminder outcomes, opt-outs and complaints where observable. A higher grant rate alone does not establish a better customer experience.
Test refusal as seriously as acceptance
Check that the interface handles declined or unavailable access without breaking unrelated tasks. Review the explanation in every actual language version. Keep collection and use consistent with the purpose described.
Start with one permission and map its task, explanation and decline path. Use the onboarding guide to distinguish a legitimate prerequisite from unnecessary first-session friction.
Ayoub Mouhachtt
Growth & performance marketing. Explore my working background.
An AI-assisted educational guide commissioned for Ayoub’s Growth Notebook. Worked examples are illustrative; they are separate from the portfolio’s client evidence. How these guides are prepared.