Family Link Not Blocking Apps? Check These Settings

Start by identifying the child’s device. You can manage Family Link from a parent’s iPhone, but Family Link cannot enforce device-wide app blocking on a child’s iPhone or iPad.

Check Whether App Blocking Applies

Google supports app management on compatible supervised Android devices and Chromebooks. Some essential system or supervision apps cannot be blocked. Check Google’s app-blocking documentation before treating an unavailable control as a fault.

Also check the exact app. A website, a second browser or a separate Lite version can provide access to similar content without opening the app you blocked. Test the named app itself before changing more rules.

Set and Check an App Block

1. Open Family Link on your own device and select the correct child.
2. Open Screen time → Time limits → App limits.
3. Choose the app and change its Allowed toggle to Blocked, then save with Done.
4. Connect the child’s device to the internet and give it time to receive the change.
5. With your child present, check whether that exact app still opens.

Google says a block normally applies in about five minutes or when the device connects. An app already in use receives a one-minute closing warning. An offline phone cannot demonstrate whether a newly saved remote rule has arrived. The block should apply across that child’s supervised Android devices and Chromebooks, rather than only the phone on which you first checked it.

If a Time Limit Is the Problem

A timed allowance lets an app remain available until its allowance is used. A complete block prevents access instead. Review which outcome you actually selected before changing supervision. Google’s screen-time guidance explains daily limits, schedules and exceptions.

Unlimited time is a specific exception, not the same as switching an app’s own limit off. Google documents it for supervised Android 7+ devices, excluding Google Kids Space. It can keep an app usable after the daily device limit. Its availability during Downtime, School Time or manual lock depends on separate settings. Check the state you actually use instead of assuming every type of lock treats an exception alike.

Daily device allowances are not necessarily a single shared budget for the whole household. Check the allowance and actual behaviour on each device. Write down which control failed: an app block, an app allowance, the daily device allowance or a scheduled restriction. That detail matters when seeking help.

Separate app exceptions from a device’s remaining time

Use the exact app’s App limits screen to distinguish four intentions: no individual timer, a timed allowance, Unlimited time and a complete block. Write down the status that the parent app actually shows. If your intention is no access, a generous timer or an Unlimited time exception is not an equivalent choice. Some system and supervision apps deliberately do not expose the same controls.

Next inspect the device-level daily allowance. Google’s example gives each supervised phone or Chromebook its own daily budget; it is not automatically a single pool shared across devices. A child using a second supervised device therefore does not by itself prove a timer failed. Compare the device and the allowance, then use app-specific rules when those fit the family’s real goal.

Treat school hours and a manual lock as separate checks. Before a restriction begins, agree which essential tools must remain available and review that state’s exception settings. Do not turn every app into an exception to solve one schoolwork problem. A short bonus allowance may be a better fit for extra device time, while a specific blocked app still needs its own separate decision.

If an app is allowed but a feature fails, inspect its permissions or the service’s own child-account rules. An app block controls use of the app; it does not approve microphone access, a purchase or a game’s contact feature. Keep those jobs separate so a successful app test does not become an unsupported claim that all content and spending are controlled.

Confirm the Device and Account Are Supervised

Under the child’s profile, inspect the signed-in devices and compare the account with the account on the affected device. A school-managed Google Workspace for Education account is not a personal Family Link account. Google’s setup requirements describe supported devices and account limitations.

If supervision is missing, follow the official setup process with your child. Do not repeatedly remove and restore supervision to test a single block. That changes the wider parental-control setup and can create a period without the intended controls.

For an existing Google Account, use Google’s instructions for adding supervision. Restarting an affected device and checking available app and system updates are reasonable low-disruption checks, but neither guarantees that a block will begin working.

Download Approval Is a Separate Setting

In Family Link, the child’s Controls → Google Play section contains purchase and download approval options. Review which content requires permission using Google’s purchase-approval instructions. These approvals cover Google Play billing, not every purchase route on the internet.

Previously approved or installed apps, and eligible Family Library apps, may not require another approval to download. That is an approval exception, not proof that the installed app cannot be blocked. If you want to stop use of an installed app, check its separate block setting.

Check Content Access Separately

If the blocked app stays closed but equivalent content opens on a website, the app block has done its narrower job. Review the browser and service controls relevant to that content. Do not assume that restricting an app automatically restricts every website, embedded player or other account.

For a child’s iPhone, use Apple’s device controls rather than trying to fix a Family Link feature that is not supported there. For mixed-device families, choose controls around each child’s actual device and the task you need to manage.

When to Ask for Help

If the exact app still opens after a confirmed block, note the child profile, device model, software version, app name, time of the change and whether the device was online. Capture only the relevant settings and hide personal account details before sharing screenshots.

Use the Help option in Family Link or Google’s family support pages. Avoid factory-resetting a phone, deleting an account or installing a third-party monitoring tool just to test one unexplained block. Those changes add disruption without establishing the cause.

If Family Link does not cover the devices or features your family needs, our parental-control app comparison explains alternatives and their platform limitations. Resolve a configuration problem before paying for a replacement.

Prove Which Family Link Control Is Failing

Use a small test log instead of repeatedly toggling supervision. Record the child, device, exact app and the result you expect. For an app block, the expected result is that this app cannot be used after the updated rule reaches the supervised device. For a daily allowance, it is that use stops when that device’s allowance is exhausted. A download-approval request tests a different control again.

With your child present, choose a non-essential app and check its actual status in the parent’s App limits screen. Record when you save the change, then connect the child’s device. Google allows about five minutes or reconnection for a block to arrive; an app already being used gets a brief closing warning. Do not declare a failure immediately after pressing Done on an offline phone.

If the named app stops but the same service remains accessible in a browser, record that as a content-access gap rather than a failed app block. Review the appropriate website and service settings. A separate app edition is also a separate target. Keep the child involved in identifying which route they actually used; guessing from an icon can send you toward the wrong control.

Check each supervised device without assuming a household-wide timer. Google explains that daily limits apply per device: a daily allowance on a phone does not necessarily mean that the same total is shared with a Chromebook. App rules and device allowances are related but distinct. Write down which device continued working and whether it was the exact blocked app, an unlimited-time exception or another route.

If the issue concerns availability after a daily limit or schedule, inspect Unlimited time and the settings for that particular restriction. Do not use manual lock as a substitute test and assume it has identical exception rules. Keep essential contact needs in mind and explain any temporary changes. Never remove a necessary supervision or system app because its blocking control is unavailable.

Once the test works, restore any temporary allowance and tell other caregivers which rule changed. Check the other supervised devices that actually matter to your household. Record a successful block separately from a successful content restriction or purchase approval. Passing one does not establish that all three are configured correctly.

If the same app remains usable after the supported wait on an online, supervised device, preserve the evidence for Google’s Help route: app name, child profile, device/software version, status shown, change time and observed outcome. Hide identifying details before sharing. Leave working supervision in place while seeking help; removing and re-adding accounts introduces new variables and can disrupt other protections.

Frequently Asked Questions

Sources and image credits

Google app blocks and exceptions; device screen-time limits; supported devices. Control diagram: Impulsec.

Share this article

WhatsAppLinkedInRedditFacebookX