What Is Guided Access on iPhone — and How Does It Work?
Guided Access is a built-in iOS accessibility feature that locks an iPhone (or iPad) into a single app and lets you control exactly which parts of that app someone can interact with. Once activated, the device won't respond to the Home button, won't allow app switching, and can be configured to disable specific areas of the screen or hardware buttons entirely.
It's one of those features most people never discover — until they need it — and then it becomes indispensable.
The Core Idea: One App, Controlled Access
When Guided Access is running, the iPhone essentially becomes a single-purpose device. The user can't swipe to the home screen, open the app switcher, or jump to another app. The session continues until someone with the passcode (or Face ID/Touch ID, depending on settings) exits it deliberately.
This makes it useful in situations where you want to hand someone your phone — a child, a customer, a patient, a student — without giving them access to everything on it.
How to Set Up Guided Access
Setting it up takes about two minutes:
- Go to Settings → Accessibility → Guided Access
- Toggle Guided Access on
- Tap Passcode Settings to set a dedicated Guided Access passcode, or enable Face ID/Touch ID to end sessions
- Optionally configure Time Limits to set audio or screen lock alerts when a session expires
To start a session, open the app you want to lock to, then:
- Triple-click the Side button (Face ID iPhones) or Home button (older models)
- Tap Guided Access in the menu that appears
- Adjust options, then tap Start
To end a session, triple-click the same button again, authenticate, and tap End.
What You Can Restrict During a Session 🔒
Before starting a session, Guided Access gives you a set of granular controls:
| Restriction | What It Does |
|---|---|
| Touch | Disables all touch input on the screen |
| Motion | Prevents the device from responding to physical movement |
| Keyboards | Blocks the keyboard from appearing |
| Volume Buttons | Locks the physical volume controls |
| Sleep/Wake Button | Prevents using the side button to sleep the screen |
| Screen Areas | Draw a circle over parts of the screen to disable taps there |
The screen area restriction is particularly powerful. If you open a web browser and want to prevent someone from tapping the address bar, you can draw a region over it. Taps in that zone simply won't register.
Who Actually Uses This Feature?
Guided Access was originally designed with accessibility in mind — specifically for users with cognitive or attention-related needs who benefit from a focused, distraction-free interface. But real-world use has expanded well beyond that.
Common use cases include:
- Parents locking a child into a single game or video app without access to Safari, the App Store, or messages
- Teachers and schools restricting students to a testing or learning app during exams
- Retail and kiosk environments where a tablet or phone is set up for public use — a menu browser, a sign-in form, a product catalog
- Healthcare settings giving patients access to a specific app without exposing other data
- Demos and presentations where you want to show one app without accidentally switching away
Each context puts different demands on the feature. A parent setting up a toddler's iPad session cares about simplicity and speed. A business deploying kiosk mode at a trade show cares about reliability across longer sessions and whether the feature holds up if the battery drops low.
Variables That Affect How Useful It Is for You
iOS version matters. The feature has been refined over time — Time Limits, Face ID exit authentication, and some restriction options were added in later releases. Devices running significantly older iOS versions may have fewer options.
Device model plays a role in how you trigger and exit sessions. Face ID devices use the Side button for triple-click; Touch ID devices use the Home button. This is simple but matters when setting up for someone unfamiliar with the device.
Use case complexity determines whether Guided Access alone is enough or whether you'd be better served by Screen Time restrictions or a Mobile Device Management (MDM) solution. Guided Access is session-based — it doesn't persist through restarts automatically. If you need persistent, policy-level app locking across a fleet of devices, MDM tools offer that at a different level entirely.
Passcode management is a real consideration. If you set a Guided Access passcode and forget it, exiting the session becomes a problem. For shared or institutional devices, who holds the passcode and how it's communicated matters more than it might seem.
Guided Access vs. Screen Time: Not the Same Thing 📱
These two features are often confused. Here's the practical difference:
- Guided Access is a temporary, session-based lock to a single app — you start it manually each time
- Screen Time offers persistent, policy-level restrictions — app limits, content filters, downtime schedules — across the whole device
They solve different problems. Guided Access is hands-on and situational. Screen Time is structural and ongoing. Some users run both.
Where the Real Decisions Start
Understanding how Guided Access works is straightforward — Apple built it to be accessible. But whether it solves your specific problem cleanly depends on factors only you can evaluate: how long sessions need to run, who's managing the device, whether a forgotten passcode would be a minor inconvenience or a serious operational issue, and whether session-based locking fits your workflow or whether a more persistent solution makes more sense for your setup.