Ask to Browse Not Working in iOS 27? Check These 5 Dependencies
Share
Ask to Browse in iOS 27 is not a single switch. It is a chain: the child needs the right account and website-filtering mode, the family needs the new Screen Time setup, and the approval request needs a valid route to a parent or guardian. If one link is missing, the symptom can look like “Ask to Browse is broken” even when Safari itself is working normally.
This guide focuses on that chain. If your goal is simply to block or allow a site, see our website blocking guide. If the problem is specifically that Ask to Browse is missing, a request never arrives, or an approval does not behave as expected, start with the symptom below.
First, identify where Ask to Browse is failing
| What you see | Most useful first check |
|---|---|
| No Ask Permission option on the child’s device | Confirm the family has upgraded to the version 27 parental-controls experience and that website filtering is set to Approved Websites Only. |
| The child can request a site, but the parent receives nothing | Check that the organizer or parent/guardian is in the child’s Contacts. |
| The request arrived earlier but is gone or no longer actionable | Have the child send it again; Apple says unanswered requests expire after 24 hours. |
| A site was approved but later needs to be blocked | Use the site entry under Settings > Family > child > Apps & Websites and block it there. |
| Some family devices show the old Screen Time layout | Check Settings > Family > View Family Devices for devices that still need an update or are listed as legacy devices. |
1. Make sure the family actually moved to the iOS 27 parental-controls system
This is the easiest dependency to miss after an update. Apple says Ask to Browse requires the updated parental controls, and all devices in the Family Sharing group need version 27 of the relevant operating system to use the redesigned experience. Updating only the child’s iPhone is therefore not the same as upgrading the family’s parental controls.
On the parent’s iPhone, open Settings > Family > View Family Devices. Apple uses this screen to show devices that can still be updated. If the family has finished updating, Apple directs parents to Settings > Family > Get Started to transfer existing controls or set up the new controls.
If an older device cannot run version 27, Apple lists those devices under View Family Devices > Legacy Devices. Those devices can continue using the earlier Screen Time system, but that is different from having the complete version 27 parental-controls feature set.
That distinction matters because repeatedly toggling Safari settings on the child’s phone will not repair a family setup that has never completed the version 27 Screen Time migration.
2. Check the child’s account before changing browser settings
Apple’s prerequisites are specific: the child should have their own Child Account in the Family Sharing group rather than sharing another family member’s Apple Account. If the child is signed into a shared adult account, troubleshoot the account arrangement first instead of treating Ask to Browse as a Safari failure.
Ask to Browse is also age-sensitive. Apple says it is on by default for children with a Child Account under 13, while Limit Adult Websites is on by default for children under 18. Apple notes that ages can vary by state, country, or region. In other words, do not use another family’s age threshold as proof that your own settings are wrong.
For a U.S. family, use the controls shown for the child’s actual account and age rather than trying to force a menu to match an older tutorial.
3. Verify the setting that actually produces Ask to Browse
In iOS 27, the current path on a parent’s iPhone or iPad is:
Settings > Family > [child’s name] > Apps & Websites > Restrictions > Websites > Filtering
Apple’s current Ask to Browse documentation says to choose Approved Websites Only when you want the child to request approval for new websites. The alternative, Limit Adult Websites, is a different browsing policy. It is designed to filter adult content rather than require approval for every new website.
This is an important diagnostic split. If the child can browse ordinary new sites without seeing Ask Permission, first confirm which filtering policy is selected. A missing prompt is not automatically a notification bug.
Apple says Ask to Browse works in Safari and other supported browser apps on iOS 27, iPadOS 27, and macOS 27 after Screen Time has been upgraded. Avoid assuming that every third-party in-app browser implements the same experience; reproduce the issue in Safari first. That gives you a cleaner test of the Apple-controlled part of the chain.
4. If the request sends but never arrives, check Contacts
This is the dependency that can make a correctly configured child device look broken. Apple specifically instructs families to make sure the Family Sharing organizer or a parent/guardian is added to the child’s contacts list so requests can be sent for approval.
If the child sees Ask Permission and can submit the request, stop changing the website-filtering mode. At that point, the child-side restriction is already doing its job. Check the approval route instead.
On the parent side, Apple says the organizer or parent/guardian can approve or decline an Ask to Browse request from an iPhone, iPad, or Mac. The request appears as a message that the parent opens to review the website and choose whether to approve it.
You can also approve on the child’s device when appropriate: on the blocked website, tap Ask Permission, then Enter Screen Time passcode and follow the onscreen steps. That is useful as a diagnostic because it separates “website approval works” from “remote request delivery works.”
5. Treat a 24-hour-old request as expired, not stuck
Apple documents a specific timeout: if the parent does not respond within 24 hours, the child needs to make the request again. That gives you a clear cutoff.
If yesterday’s request is no longer available, do not spend time resetting Messages, Safari, or network settings just to revive it. Send a fresh request from the child’s device. If the new request arrives, the earlier one likely aged out as designed.
If a fresh request still does not arrive, return to the two dependencies that affect delivery most directly: whether the adult is an organizer or parent/guardian in the Family Sharing group, and whether that adult is in the child’s Contacts.
What an approval actually changes
Approving a request adds that website to the child’s allowed list. Apple says the child can then access the website unless you block it later. That is different from temporarily bypassing the restriction for one page load.
To reverse a previous approval on iPhone or iPad, go to Settings > Family > [child’s name] > Apps & Websites, select the website, tap Block Website, and confirm. This is also the place to inspect whether a site you thought was still restricted is already in the Allowed list.
Do not troubleshoot Ask to Browse like an ordinary Safari problem
Clearing Safari history, resetting network settings, reinstalling a browser, or changing unrelated privacy settings are poor first moves for this particular failure. Ask to Browse depends on family membership, account type, the version 27 Screen Time migration, website filtering, and the parent-request route. Those dependencies can be checked directly and are less destructive than broad resets.
A useful order is: family software state → child account → filtering mode → request delivery → request age. Only after those checks pass does it make sense to investigate a broader software problem.
When the old Screen Time instructions no longer match
iOS 27 redesigned parental controls. That means instructions written for iOS 26 can point to a different menu hierarchy even when the underlying goal is similar. Our older iOS 26 website-blocking guide remains useful for understanding the difference between broad adult-content filtering and an allow-list, but use Apple’s version 27 paths above when diagnosing Ask to Browse.
Apple’s current documentation also provides a useful fallback for mixed-device families: devices that cannot update can continue to use the earlier Screen Time and Family Sharing settings. That does not mean the new Ask to Browse workflow is guaranteed on those legacy devices.
The shortest reliable diagnosis
If Ask to Browse is missing, first confirm that the family completed the version 27 parental-controls upgrade and that the child is using a Child Account in Family Sharing. Then check Settings > Family > [child] > Apps & Websites > Restrictions > Websites > Filtering and use Approved Websites Only for Ask to Browse. If the child can send a request but the parent never receives it, verify the parent or guardian is in the child’s Contacts. If the request is more than 24 hours old, send a new one.
Those checks follow the dependencies Apple documents for the feature and avoid turning a narrow parental-control problem into a full-device troubleshooting exercise.