Ask for a specific permission at the point in time when someone needs to complete a task. This is also known as ‘incremental authorisation’. If someone wants to tag a photo with their location, they’re asked for permission to access location data as they add the tag.
IF thinks this pattern makes it easier for people to understand why data is being collected. They can weigh up their options at the point when it is needed. Using this pattern too frequently can mean that people ignore it, though.
- Asking in context makes it easier for people to understand why a service needs access to that information.
- One decision at a time helps people make considered choices.
- Relatively low friction, depending on how frequently it’s applied.
- Reminds people what data the service does and doesn’t usually access.
- Overuse could overwhelm or frustrate people.
- Low-friction interactions may not be appropriate for sensitive information.
- Can be unclear if access is permitted, or not, after the activity has finished.
- Asking permission in the middle of an important task may mean people don’t have time to consider the implications of what they’re agreeing to.
Browsers ask for permission to give a website access to a webcam, microphone or location when the website requests it.
Was this pattern useful?