Permission questions that show why users say no to a request
Ask users how they answered a new permission request, why they refused and what they are comfortable sharing. Each question below comes with when to ask it and what the answer tells you.
What app permission survey questions tell you
App permission survey questions ask users how they answered a new permission request after an update, why they said no and what they are comfortable letting your app reach. A refused permission can quietly switch off a feature, and these answers tell you which requests need a better reason or a better moment.
Ask within a week or two of the update that added a request, while users remember the prompt. Usertick doesn't run inside phone apps, so send the survey's link by email or open it from the app's settings, with the version as a tag on the link. Pick four to six questions.
Each written answer gets a theme, a type and a sentiment, so worries about the same permission group together. Results shows each card beside the period before, and the inbox gives a response an owner when a refusal broke a feature the user relies on.
- Questions
- 14
- Best asked
- Within two weeks of the update that asked
- Industry
- Mobile apps
- Where to find them
- From library in the Usertick survey editor, on every plan
The 14 permissions after an update questions, with when to ask each
Grouped by what they tell you. Use them as they are or change the wording.
The request after the update
Start with whether users saw the request, how they answered and how well the app explained it.
- 01Yes / No
Did the app ask for a new permission after the last update?
A yes or no on a new permission request after the last update. Add logic to skip the follow-ups for users who answer No, so the survey stays short.
- 02Multiple choice
How did you answer that request?
How the user answered the request, including users who aren't sure. Results shows each share, and a large share who aren't sure says the request was easy to miss or hard to read.
- 04Stars
How clearly did we explain why we needed it?
Rates how clearly the app explained why it needed the permission, on five stars. A low rating beside many refusals points to the explanation.
- 11Screenshot
Capture the permission message you were shown
A capture of the permission message. From your phone app, use File upload so users can attach a screenshot they took. The Screenshot question captures a web page. Both are on every plan, and Free allows 1 of them per survey.
Why users say no
These questions name the reasons behind a refusal and what stopped working because of it.
- 03Text
Why did you say no to a permission?
The reason for saying no, in the user's own words. AI reading files each answer under a theme, so worries about tracking or unclear reasons group together.
- 13Text
Which permission do you not understand why we ask for?
The permission users can't see a reason for, in their own words. Each answer names a request to explain better or to drop.
- 06Yes / No
Did anything stop working after you refused?
Whether something stopped working after a refusal. Every Yes is a feature that depends on a permission without saying so, so tell users what they lose before you ask.
What users are comfortable sharing
Ask which permissions users accept and on what terms, before you add another request.
- 05Multiple choice
Which permissions are you happy to give this app?
Lets users tick the permissions they are happy to give. Results shows a bar with the share for each, which tells you which requests users accept easily.
- 14Matrix
How comfortable are you sharing each of these?
Rates comfort with location, contacts, photos and notifications on three steps. The heat map shows which request users accept only when they know why.
- 08Big scale
How comfortable are you with what the app can reach?
How comfortable users are with what the app can reach, from 1 to 10. Results shows the average and a column per step, a number to follow across releases that add requests.
When and how to ask
Timing, changing a setting later and consent belong together, since they set how your next request works.
- 09Dropdown
When should an app ask for a permission?
When an app should ask, from first launch to only when users go looking. Results shows each share, a guide for when your next request appears.
- 07Customer effort
How easy is it to change a permission later?
A customer effort score for changing a permission later, on a 7 point scale. A low score asks for a link from the app to the right setting.
- 10Yes / No
Do you check what an app can reach before you update it?
Whether the user checks what an app can reach before updating. A large share of Yes tells you new requests are read closely, so every one needs a clear reason.
- 12Consent
May we collect crash reports from your phone?
A checkbox for permission to collect crash reports, kept with the response. Your app has to honor the answer itself, so its own settings screen may be the better place to ask.
Tips for asking about permissions after an update
Small choices that get honest, useful answers.
- 01
Ask while the prompt is fresh
Send the survey within two weeks of the update that added a request. After that, users remember little more than whether a feature works.
- 02
Explain before you ask
Use the reasons users give for saying no to rewrite the screen before your request, then ask again after the next update.
- 03
Watch for broken features
Give every answer where a refusal broke a feature an owner in the inbox, and tell the user how to turn it back on.
- 04
Tag the update on the link
Add the version as a tag on the survey link. The tag stays with each answer, so you can tell which release added the request users refused.
Add these questions to a survey
From the library to the first answers.
- 1
Open the library
In the Usertick survey editor, choose From library, filter by industry and topic, and add several questions at once.
- 2
Or paste your own list
Paste questions reads up to 10 questions from any text on Free, 100 on Starter and 200 on Pro and above, keeps your wording and picks an answer type for each.
- 3
Choose where it runs
Show the survey on your website, send it by email, share its link and QR code, or switch it to a conversation.
- 4
Read the answers
Results counts every score and choice, and Usertick reads each written answer and files it by topic, on every plan.
Templates and more questions about permissions after an update
Full surveys that ask about the same things, and neighboring topics in the library.
Templates
Browse all templatesFrequently asked questions
Within a week or two of an update that added a request. Send the survey by email to a contact list now or on a scheduled date, or open its link from the app.
Four to six. Start with whether the app asked and how the user answered, add how clearly it explained the reason, and end with the permission users don't understand.
Yes, on every plan. When the survey opens from your phone app, use the File upload question (1 per survey on Free) so users can attach a screenshot from their photos.
Yes. The question library comes with every plan, the free plan included, and the free plan covers 150 responses a month across your surveys.
Yes. Once a question is in your survey, reword it, change its options or its answer type, and add logic to skip it for some answers.
Yes. The library is translated into Usertick's built-in languages, and in any other language it shows in English for you to translate.
Listen better, act faster, and build what truly matters.
Start free, see what your customers mean, and get each answer to the person who can act on it.
- 150 responses a month on Free
- Every channel and AI analysis
- No card needed