Repair parental controls when the right accounts and platform are still in place and only a narrow setting or device is failing. Replace the setup when the family still needs controls but the current account structure, platform coverage, or recovery path cannot reliably enforce them. Retire a control only when the underlying need has ended or moved to a verified successor, not merely because one device stopped obeying it.
Repair a narrow, understood failure
Choose repair when you can name the affected child account, adult account, device, control, expected behavior, and actual behavior. Examples include one app permission, one outdated device, a schedule applied to the wrong profile, or a missing parent role. Verify the current setting from the official parent interface, make one change, and test on the child's device.
Google's Family Link permission guidance says permissions may need to be configured separately on each child device and that disabling a permission can stop an app from working correctly. A single-device mismatch is therefore a reason to inspect scope before replacing the whole system.
Replace a structurally unreliable setup
Replacement is appropriate when controls repeatedly fail because accounts are shared, the supervising adult cannot recover the management account, important devices are unsupported, multiple platforms have conflicting rules, or no one can explain which setting is authoritative. Define the successor first: named adult owners, separate child accounts, supported devices, required limits, emergency communication needs, recovery contacts, and a rollback plan.
Do not assume one product covers every device. Google's device-supervision guidance says most Family Link supervision tools work on supported Android devices and Chromebooks but not on iPhones, iPads, or most computers. Apple’s Screen Time guidance ties family-managed controls to the child's Apple Account and Family Sharing. Replace by tested platform scope, not by brand familiarity.
Pilot the new setup on one noncritical rule. Confirm the adult can change it, the child device enforces it, approved communication remains available, and recovery works. Only then migrate additional limits. Keep the old controls active until the replacement has passed these checks, unless running both creates a documented conflict.
Retire a control deliberately
Retirement can be appropriate when a child has reached the applicable age or family milestone, the device is permanently removed, a service is no longer used, or a verified successor now owns the requirement. Review app access, purchase approval, content filters, communication limits, location settings, and account recovery separately; they may not all end at the same time.
Retiring a management app does not necessarily remove settings already applied on a device. Test the resulting state, remove obsolete adult access, preserve needed account-recovery information, and explain the change to the family. Never delete a child account or family group as an improvised troubleshooting step.
Use a six-part decision check
Score enforcement, device coverage, account ownership, recovery, family fit, and platform support as pass, repairable, or failing. Repair when failures are isolated and reversible. Replace when several structural controls fail but the need remains. Retire only when the need has ended or a tested successor has taken over. Record the decision, responsible adult, affected devices, evidence, rollback, and next review date.
Sources
- Manage your child's app permissions — Google
- Learn which devices can be supervised — Google For Families Help
- Use Screen Time to manage your child's iPhone or iPad — Apple Support