Permission request screen examples

A permission request screen explains why an app wants access before the operating system shows its own prompt. Our examples focus on notifications: a short explanation of why alerts help, a preview of example notifications and the system allow or block dialog, designed for web and mobile in eight visual styles with light and dark versions. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.

DeviceAll Web Mobile

StyleAll Minimal Editorial Brutalist Luxury Playful Corporate Retro Monochrome

Theme

16 examples

Web · minimal

Web · editorial

Web · brutalist

Web · luxury

Web · playful

Web · corporate

Web · retro

Web · monochrome

Mobile · minimal

Mobile · editorial

Mobile · brutalist

Mobile · luxury

Mobile · playful

Mobile · corporate

Mobile · retro

Mobile · monochrome

Permissions request design tips

Show your explanation screen before triggering the system prompt, because a refused system prompt is hard to ask for again.
Preview real example notifications so people can judge the value and frequency for themselves instead of trusting a vague promise.
Ask at the moment the permission becomes useful, such as after someone follows a project, not during the first seconds of launch.
If someone declines, let the feature keep working where possible and offer a settings shortcut for turning permissions on later.

Questions

What is a permission priming screen?

It is an in-app screen shown before the system permission dialog that explains what access is for and what the person gains. Because operating systems limit how often an app can show the native prompt, priming helps people make an informed choice the first time.

When should an app ask for notification permission?

Ask when notifications clearly serve something the person has just done, such as booking, following or starting a task. Context makes the benefit obvious. Asking immediately on first launch, before any value is shown, gives people little reason to say yes.

What should happen if a user denies a permission?

The app should continue to work and explain, where relevant, what is unavailable without the permission. Offer a gentle path to the device settings later, at a moment when the feature is needed, rather than repeatedly nagging with modal prompts.

Browse by pattern

App screens

Dashboard
Data table
Analytics charts
Login
Sign up
Forgot password
Two-factor code
Welcome
Onboarding step
Permissions request
Home
Feed
List view
Detail view
Kanban board
Calendar
File manager
Search results
Editor toolbar
AI chat assistant
Chat list
Chat thread
Video call
Image viewer
Map view
Video player
Create post
Class schedule
Booking details
Booking confirmed
Product detail
Cart
Checkout
Order confirmation
Settings
Profile
Notifications center
Team members
Roles permissions
Audit log
API keys
Integrations
Billing plans
Invoice
Paywall upgrade
Cancel subscription
Empty state
404 error
Loading skeleton
Success confirmation
AI workspace
AI settings
Version history
Approval queue
Doctor directory
Telehealth visit
Clinic home
Music player
Playlist
Portfolio home
Case study
Security dashboard
Project tracker
Course dashboard
Multi-step form wizard
Bank onboarding
Product scan
Split view (master-detail)
Canvas editor
Floor plan
Voice call
Toast / snackbar with undo
Confirm dialog (destructive)
Side drawer
Command palette
Date range picker
Form validation errors
Sign-in error
Card declined at checkout
Find a pro (home services)
Book a home-service visit
Job tracker
Account email
Order email
Shift scheduler
Leave calendar
Time-off request
Multi-location operations dashboard
Inventory stock
Savings goal
Onboarding carousel

UI components

Tabs
Cards
Pagination
Popover
Tooltip
Dropdown menu
Accordion
Radio buttons
Breadcrumbs
Toggle switch
Stepper
Sidebar navigation
Loading spinner

Website sections

Website templates

Building with an AI coding agent? Every screen here is also in the free Made Good Designs MCP server: ask Claude, Cursor or ChatGPT to search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.