iPad Guided Access: Complete Setup Guide for Visitor Sign-In

A receptionist on her first day, an iPad mounted at the lobby with a sign-in app open, and a 6-digit passcode taped to the inside of a drawer behind the desk. That is iPad Guided Access doing its job. The visitor cannot exit the sign-in app, cannot swipe to Safari, cannot read the previous visitor’s name. Anyone authorized triple-clicks, types the passcode, and the iPad goes back to a normal device.

iPad Guided Access is the fastest way to put a single iPad into kiosk mode. It is free, built into iPadOS since iOS 6, and takes about 90 seconds to enable end-to-end. This guide walks the full setup for visitor sign-in scenarios, the Options panel toggles Apple’s help docs skim past, the passcode and biometric hygiene that decides whether a forgotten passcode is a 30-second fix or a full force-restart, and the limits you should know before you trust it for an unattended kiosk.

9:41

Reception · Building 1

Welcome

Tap below to check in or check out. We’ll let your host know you’re here.

Sign in Sign out

Returning visitor

What iPad Guided Access is — and what it isn’t

Guided Access is an iPadOS Accessibility feature that locks the iPad to a single app from inside that app. You triple-click the side button (or the Home button on older iPads) and the device refuses to leave that app until you triple-click again and authenticate. Apple ships it on every iPad and iPhone, free, no admin tooling required. The official feature page lives at support.apple.com.

What Guided Access is not: a managed kiosk lock. It does not require the iPad to be supervised, which means it cannot use the com.apple.app.lock payload that Single App Mode is built on. It does not survive a reboot. It does not block screenshots by default. It cannot be deployed remotely — every iPad has to be touched once to enable the feature and once again to start each session. If your deployment needs any of those, you want Single App Mode instead, and the iPad kiosk mode pillar lays out the full decision tree.

For a single iPad in a small office lobby, an event check-in table, or a pilot before a fleet rollout, Guided Access is the right starting place.

Enabling Guided Access on the iPad

This is the one-time setup. You only do it once per iPad. After this, starting a Guided Access session is a triple-click.

1. Open Settings on the iPad.
2. Tap Accessibility. It is roughly the eighth row, between Display & Brightness and Wallpaper.
3. Scroll down to the General section near the bottom. Tap Guided Access.
4. Toggle Guided Access on. The screen expands with new options.
5. Tap Passcode Settings, then Set Guided Access Passcode. Enter a 6-digit passcode and confirm it on the next screen.
6. (Optional but recommended) Toggle Face ID or Touch ID on. With biometrics enabled, authorized staff end the session with a double-click and a glance instead of typing.

A few details Apple’s help page glosses over. The Guided Access passcode is independent of the device unlock passcode — set it to something different, because anyone watching a receptionist type the device passcode would otherwise also have the kiosk-exit passcode. The Mirror Display Auto-Lock toggle is the one most people miss. Off by default, it lets the iPad’s normal Auto-Lock timer end the Guided Access session by sleeping the screen. For a sign-in iPad you want this off — you want the iPad to stay awake and locked to the app, not sleep itself out of kiosk mode every two minutes.

Starting a Guided Access session on the visitor sign-in iPad

With Guided Access enabled in Settings, here is the per-session flow you (or the receptionist) run each time the iPad needs to be put into kiosk mode.

1. Open the app you want to lock the iPad to. For visitor sign-in, that is InstaCheckin, on its welcome screen.
2. Triple-click the side button. On iPads with a Home button, triple-click the Home button instead. The Guided Access setup panel slides up.
3. The screen shows a preview of the locked app with a header reading “Guided Access.” Two buttons sit at the bottom: Options on the left, Start on the right.
4. Tap Options to fine-tune the session. (See the next section for the full breakdown of every toggle.) Make your selections, then tap Done.
5. Tap Start in the top-right.

The iPad is now locked. The Home indicator is gone. Swipes from the bottom and the right edge are disabled. Control Center and Notification Center are unreachable. The visitor can use the app and only the app.

To end the session: triple-click the side or Home button, authenticate with the passcode (or Face ID / Touch ID if you toggled it on during setup), and tap End in the top-left of the Guided Access panel. Tap Resume in the top-right if you want to stay in the session — useful if you triple-clicked by accident.

The Options panel: every toggle explained

The Options panel is the part of Guided Access most quick-start guides skip, and it is where the actual kiosk hardening happens. Tap Options before tapping Start, and you get this list of session-level toggles. Apple’s docs show the screenshot but do not say much about which toggles matter for visitor sign-in. Here is the full set.

• Sleep/Wake Button. Toggle on (which disables the button) for a wall-mounted iPad you don’t want a passing visitor to sleep. Combined with Mirror Display Auto-Lock off, the screen stays on indefinitely — fine on AC power, hard on a portable iPad battery.
• Volume Buttons. Disables the physical volume rocker. Recommended on for visitor sign-in — there is no reason for a visitor to need volume control, and curious hands find the rocker.
• Motion. Disables rotation and motion sensors. Useful when the kiosk is mounted in a fixed orientation. Most sign-in apps lock orientation in code, but this is belt-and-suspenders.
• Software Keyboards. Disables the on-screen keyboard. Leave off for sign-in — visitors type their name and email. Useful only for pure tap interfaces (a status board, signage).
• Touch. Disables touch entirely. Same as above — leave off for sign-in.
• Time Limit. Ends the session after a chosen duration. For a 9-to-5 lobby kiosk leave it off and re-engage manually each morning. For an event check-in table that runs 8 a.m. to 11 a.m., set Time Limit to 3 hours and the iPad ends the session for you.
• Dictionary Lookup. Lets a visitor select text and look it up. Toggle off — no visitor signing in needs to define a word, and the lookup popover is a small attack surface.

You can also draw a circle around a region of the screen in the same Options sheet. Anything you circle is excluded from touch input for the session — useful to ring-fence the Safari address bar if you ever lock the iPad to a single URL.

Passcode hygiene and biometric setup

The Guided Access passcode is the single point of failure for the entire kiosk. Treat it with the same discipline as any shared password.

• Use 6 digits, not 4. The passcode prompt accepts both, but 4 digits is now uncommon enough that it draws attention.
• Make it different from the device unlock passcode. Anyone shoulder-surfing the receptionist would otherwise have both passcodes from one observation.
• Document it once, in your office password manager. Not on a sticky note inside the iPad case.
• Rotate it when staff with access leave the company. This is annual at most for a small office and rare enough that it is easy to miss.

Toggle Face ID or Touch ID on during the one-time setup. With biometrics on, an authorized staff member double-clicks the side button and authenticates with their face or finger. The Guided Access passcode is the fallback for when biometrics fail (a new staff member whose face is not enrolled, a glove on a manufacturing floor). Biometrics are the daily path; the passcode is the recovery path.

What Guided Access does NOT do

Plainspoken about the limits, because they decide whether Guided Access is enough or whether you need to step up to Single App Mode.

• Guided Access does not survive a reboot. If the iPad force-restarts, the battery dies, or iPadOS reboots for an update, the device boots back to the Home Screen and the kiosk is off. Someone on-site has to re-engage it.
• Guided Access does not block screenshots by default. The volume-up + Sleep/Wake gesture still fires unless you disable both buttons in Options. Real screenshot blocking is a Restrictions payload, not a Guided Access feature.
• Guided Access cannot be pushed remotely. Every iPad has to be touched once to enable the feature and once per session to start the lock. There is no MDM payload for Guided Access. Fleets outgrow it for this reason alone.
• Guided Access does not block AirPrint, AirDrop, or iCloud. Lock these down with a managed Restrictions profile if it matters.
• Guided Access does not stop iPadOS update prompts. A visitor can be greeted by an “iPadOS X.Y is available” banner. Defer updates via Settings → General → Software Update, or via MDM.

None of this is a reason to avoid Guided Access for a single front-desk iPad. It is a reason to plan the upgrade path before you have 10 iPads across 4 offices.

When to upgrade to Single App Mode

The threshold is roughly: more than 2 iPads, more than 1 location, or any iPad that sits unattended overnight. Past those, you want a managed lock that survives reboots and can be pushed remotely. That is iPad Single App Mode, deployed via Apple Configurator 2 (free, USB-tethered to a Mac) for handfuls of iPads, or via an MDM (Microsoft Intune, Jamf Pro, Mosyle, ManageEngine, Kandji) for fleets.

Single App Mode requires the iPad to be supervised — a one-time factory-erase-and-prepare step. Once supervised, the iPad accepts the com.apple.app.lock payload, boots directly into your kiosk app on every restart, and ignores the Home button until an admin removes the profile. The pillar iPad kiosk mode guide covers all four mechanisms — Guided Access, Apple Configurator Single App Mode, MDM-deployed Single App Mode, and Autonomous Single App Mode — with a comparison table that makes the right choice obvious for your deployment size.

For visitor sign-in specifically, InstaCheckin’s office visitor management and event check-in deployments use Guided Access for pilots and small offices, then graduate to MDM-deployed Single App Mode with Autonomous Single App Mode allowlisting once the install footprint passes 5 to 10 iPads.

Troubleshooting: forgot the Guided Access passcode

The iPad refuses the passcode three times in a row, the receptionist is stuck, the lobby has a line. Here is the recovery sequence. The exact gestures depend on whether the iPad has Face ID or a Home button.

iPads with Face ID (iPad Pro 11-inch, iPad Pro 12.9-inch 3rd gen and later, iPad Air 4th gen and later, iPad mini 6th gen and later, iPad 10th gen):

1. Press and release Volume Up.
2. Press and release Volume Down.
3. Press and hold the top button until the Apple logo appears (about 10 seconds). Keep holding past the Slide to Power Off slider.
4. Release when you see the logo. The iPad reboots out of Guided Access.

iPads with a Home button (older iPads, iPad 9th gen and earlier):

1. Press and hold the Home button and the top button (or side button) together.
2. Keep holding for about 10 seconds, past the Slide to Power Off slider, until the Apple logo appears.
3. Release. The iPad reboots out of Guided Access.

Once the iPad is back at the Home Screen: open Settings, tap Accessibility, tap Guided Access, tap Passcode Settings, and tap Set Guided Access Passcode to set a new passcode. The receptionist can now re-engage Guided Access on the sign-in app and reopen the lobby. Apple’s force-restart reference is worth bookmarking on the office laptop.

Two related gotchas. If the iPad is in Lost Mode via Find My, force-restart will not bypass Lost Mode — you need the Apple ID password too. If the iPad’s device passcode is also forgotten, you are past Guided Access and into a Recovery Mode restore through Apple Configurator 2, which factory-erases the iPad. Document the device passcode in the same password manager.

Once the kiosk is back up, re-engaging Guided Access takes fewer than 30 seconds — open the app, triple-click, tap Start. Worth practicing the recovery sequence once before the iPad goes live, so the first time it happens is not also the first time anyone has tried it.