Parents use approval prompts to control what kids can download or install. When those prompts fail to arrive, it can feel like you’re flying blind. This guide breaks down practical, step by step fixes you can try today. We’ll define what parental approval requests mean in common apps like Apple Screen Time, Google Family Link, and other parental controls. Then we’ll walk through quick checks, platform specific paths, and reliable test methods so you can get back to supervising your child’s digital world.
Parental approval requests appear when a child tries to download an app, make a purchase, or access certain features that require a parent’s permission. On iPhones and iPads, this often shows up as an approval request inside Screen Time or the Family Sharing flow. On Android devices, Family Link handles their own version of the prompt. If the parent never sees the alert, you won’t know whether the request is blocked by a setting or simply not routed to the right device. That distinction matters, because the fix is usually straightforward and fast.
Let’s start with a practical, no-nonsense approach. The goal is to verify connections, confirm alerts can travel, and identify the moment the path breaks. Keep in mind that every family setup has its quirks. A small misconfiguration can block a message that should reach a parent’s phone in minutes. With the steps below, you’ll have a clear checklist and a plan to restore smooth delivery.
Check the basics that impact delivery
Platform gaps often hide in plain sight. The fastest route is to confirm that the approval system is linked to the correct parent account and that notifications can travel to the right devices. Start with these two high leverage checks.
Confirm the approval system is linked to the correct parent account
- Open the parental control app on the parent device. This could be Screen Time on iOS or Family Link on Android.
- Verify the account shown as the parent is the one you actually use to approve requests. Look for the email address or the Apple ID / Google account name.
- Make sure the child device is in the same family group. If the child is listed under a different family or a secondary profile, requests may route to the wrong person.
- Check whether you have multiple devices signed in with the same service. A parent may be logged in on a tablet or another phone with a different profile.
- Watch for a common mistake: signing into the wrong profile or using a different email than the one tied to the child’s account.
- Simple checklist you can follow:
- Confirm the parent account in the app matches the account you use for purchases.
- Confirm the child is linked to the same family group in the app.
- Check all devices you use for approvals; ensure the primary device is ready to receive requests.
Review notification settings and do not disturb modes
- Check app notification permissions on the parent device. On iOS, go to Settings > Notifications > [App name] and enable notifications. On Android, Settings > Apps > [App name] > Notifications, then turn on allowed alerts.
- Ensure alerts are enabled within the parental control app itself. Some apps have a separate in app toggle for push notifications.
- Do Not Disturb or Focus modes can mute prompts. Make sure these modes are off or configured to allow alerts from the parental control app.
- For iOS users, also check that the notification style is set to banners or alerts, not just sounds.
- For Android, confirm that the parental control app is not hidden by a battery saver mode or a low power setting that blocks background activity.
- Quick check tips:
- If you’ve recently updated the OS, recheck notification permissions because some OS updates reset certain toggles.
- Test a pretend request to see whether a banner appears within a minute.
Platform specific issues that block delivery
Differences between iOS and Android paths mean you may see the same problem from different angles. Here are targeted checks for each ecosystem, focused on what typically blocks delivery and how to fix it quickly.
iOS Family Sharing and Screen Time delivery path
- Start with Settings > your name > Family Sharing. Confirm that Family Sharing is active and that the child’s account shows under the family group.
- Check that Screen Time sharing is enabled for the child. In some setups, Screen Time is configured for the family but not shared with the parent.
- If the parent’s device doesn’t receive the request, re-link the accounts. On both devices, sign out of the Family Sharing and Screen Time apps, then sign back in with the correct accounts.
- Verify that Ask to Buy or permissions prompts are correctly configured for the child. In Settings > Family Sharing > [Child] > Ask to Buy, toggle on if needed. If the prompt isn’t shared, enable the feature and try again.
- Common culprits include mismatched Apple IDs or an empty or stale family group. Fix them by removing the child from the family and re-adding, then reattempt the approval flow.
- Quick gains: make sure the child device has Screen Time enabled and is set to share requested approvals with the parent. This is often overlooked but essential for the signal to reach the parent.
Android Family Link and notification routing
- Open Google Family Link on the parent device and verify the child profile is correctly linked. If the child’s device isn’t showing up, re-link the accounts.
- Check notification access for the Family Link app. On Android, go to Settings > Apps & notifications > See all apps > Family Link > Notifications, and ensure notifications are allowed.
- If alerts fail to surface, examine whether a work profile or a restricted profile is isolating the app. Some devices split apps into personal and work spaces, and one space may not push alerts to the other.
- Ensure the parent device is set to receive requests. In some setups, notification routing is tied to a specific device, so you may need to enable notifications on an alternate phone or tablet used by a parent.
- If the child device uses a restricted mode, ensure the Family Link app on that device can still initiate requests and transmit them to the parent device. A blocked background service can stop the signal from leaving the child device.
- Practical steps you can take now:
- Confirm both sides of Family Link are up to date.
- Re-authorize notification access for the Family Link app.
- If you use a secondary device for approvals, test both devices to verify parity.
Test delivery and what to do if it still doesn’t arrive
When basics and platform paths are clear, a controlled test helps confirm where the breakdown lies. A methodical test also shows you whether the system finally delivers a prompt or if you must escalate.
Run a controlled test and verify receipt
- Set up one parent account and one child device. Use a simple approval request like installing a free app or changing a settings option that requires approval.
- On the child device, attempt the action and watch the screen for the prompt. If it does not appear, move to the parent device and check the corresponding app for a pending request.
- On the parent device, check the app’s activity log or history for a new request. Some apps show a time stamp and a status such as Pending, Approved, or Denied.
- Check the notification center on the parent device immediately after the attempt. If you don’t see a prompt, review the app’s internal logs to determine whether the signal was created but not delivered.
- Conduct the test across networks. Try again on both WiFi and cellular data to rule out a connectivity issue.
- If the test succeeds on one device but not the other, it points to a device level setting (notification permissions, DND, or background activity).
What to do if the test still fails
- Start with a clean slate: re-link the child and parent accounts. Remove the child from the family group in the app, then re-add with the correct IDs.
- Update every related app on both devices. App updates fix known delivery bugs and improve compatibility with the OS.
- Check network conditions. A weak or unstable connection can delay or block prompts.
- Sign out and back in on both devices. A fresh sign-in often resolves authentication mismatches that stop requests from routing.
- Review each device for a conflicting mode or setting. Look for Do Not Disturb, Focus, or battery optimization features that block background tasks.
- If the problem persists, collect data for support. Note the OS version, app version, the time and date of the test, the type of request, and the devices involved. Screenshots of the settings pages can speed up troubleshooting.
Decision tree for common symptoms
- No prompt on parent device after a request on child:
- Is the parent app showing the request in history? If yes, focus on notification permissions on the parent device; if no, re-link both accounts.
- Prompt appears but no notification:
- Check notifications on the parent device and ensure the app is allowed to push alerts; verify Do Not Disturb is off for the app.
- Request shows in app but not on the child device:
- Confirm the child device is in the same family group and that Family Link or Screen Time sharing is enabled for the child; re-link if needed.
- All else fails:
- Reach out to support with a concise report of tests, settings, OS, and app versions. A support specialist can examine backend routing and account linkage.
Conclusion
Parental approval prompts rely on a chain of correctly linked accounts, permissions, and device settings. When one link in that chain is weak, messages can vanish or sit in limbo. Start with the basics by confirming the parent account and the notification paths. Then tackle platform specific issues for iOS and Android. Finally, run a controlled test and follow a clear recovery path if delivery still stalls.
To keep things simple, use this quick checklist after any change:
- Verify the correct parent and child accounts are linked.
- Confirm notifications are allowed on both devices.
- Check Do Not Disturb and Focus settings for both devices.
- Update all related apps and re-link if needed.
- Run a test that mirrors real use and review the app activity log.
By following these steps, you’ll restore reliable approval delivery and regain confidence in your child’s digital boundaries. If you need more guidance, share your device types, OS versions, and the apps you use, and we’ll tailor the steps to your setup. And if you’ve got a smartphone buzzing with family alerts again, you’ll know exactly where to look and what to tweak next.