Making Screen Time settings stick

The question parents ask after the first weekend: how do I set this up so my child cannot change it themselves?

The answer is not a single setting. It is a sequence.

A Screen Time passcode set after the limits only protects what is locked at that moment.

It does not reach back into settings configured earlier and never re-saved under the lock [source: apple-screen-time].

Order is the lock.

This article assumes the basic setup already exists. You need a child Apple Account inside the family’s Family Sharing group. Screen Time is turned on. The child’s device shows up under the parent’s Family entry.

If that is not yet true, follow the steps in Set up Screen Time on iPhone first. What follows here is the second pass.

Why this matters

Parents frequently report setting limits. The limits are gone three days later.

Two things cause this. Only one of them is in the parent’s hand:

1. A setting was changed on the device. Screen Time settings live on the device.

   Anyone who can unlock the phone can edit them.

   Apple documents that limits, app restrictions, and privacy controls live behind a separate passcode that is different from the device passcode [source: apple-screen-time].

   If the two match, or if the Screen Time passcode was never set, the limits are a suggestion rather than a rule.

2. A setting was never locked to begin with. Apple instructs families to confirm Screen Time is locked after setup.

   When the lock step is missed, the report on the parent’s device still shows use. The limits are simply not enforced [source: apple-screen-time].

   Independent testers call out this pattern as a current weakness of Screen Time [claim: wirecutter-parental-controls].

   The Wall Street Journal reported in 2023 that Apple acknowledged restrictions failing to stick for some families [source: wsj-screen-time-bug].

   That bug report is historical. It is not evidence the defect persists.

   The setup step that would have prevented it is the same one that prevents it today.

The rest of this article is the setup step. It is in the order it must happen.

Prerequisites

Before going further, confirm these. Without them the steps below apply, but the lock does not.

• The child has a child Apple Account inside your Family Sharing group. Standalone Apple Accounts for children cannot be managed through Screen Time [source: apple-screen-time].
• Screen Time is already turned on for the child’s device. Apple documents the activation flow under apple.screentime.root.
• You have a Screen Time passcode that is different from the device passcode. If the two match, the child can edit limits by unlocking the phone [source: apple-screen-time].
• The organizer of the Family Sharing group is the one setting this up. Organizer-side controls (including passcode recovery) only work on the organizer’s device [source: apple-passcode-recovery].

Steps

The order is the lock. Do these in order. Later steps protect the earlier ones.

1. Open Screen Time for the child on your own device. Apple documents the family-side path as the entry point for limits, restrictions, and passcode management [source: apple-screen-time].

   The screen is referenced as apple.screentime.root.

   The exact menu labels vary by iOS minor release. They are kept current in the UI-string resource rather than in this article.

2. Turn on App & Website Activity first. Reporting is the foundation for every other check.

   Without activity on, the parent cannot see what was used. The child cannot be told which limit they hit [source: apple-screen-time].

   The screen is referenced as apple.screentime.app_website_activity.

3. Turn on Content & Privacy Restrictions. This is the container that holds purchases, content ratings, web content, and privacy changes [source: apple-parental-controls].

   Each setting inside the container is independent. Turning the container on does not configure any of them.

   The screen is referenced as apple.screentime.content_privacy_restrictions.

4. Configure each area inside the container, in this order. Each step has its own UI key.

   These are not menus you type out. They are the screens the build resolves for you:

   • App ratings, under apple.screentime.content_privacy_restrictions.apps.
   • Web content (the three levels Apple publishes: Unrestricted, Limit Adult Websites, Only Approved Websites).
   • Purchases and downloads, inside the same container.
   • Privacy changes, under apple.screentime.content_privacy_restrictions.account_changes. This row controls whether the child can sign out of their Apple Account, change the passcode, or turn off Find My [source: apple-parental-controls].

5. Lock Screen Time last. Apple documents Lock Screen Time Settings as the step that asks for the Screen Time passcode.

   It freezes the configuration against edits from the device [source: apple-screen-time].

   This step is the difference between the limits exist and the limits stick.

   If the lock prompt did not appear at the end of setup, the configuration was saved without a lock.

6. Confirm the lock from the parent side. Open Screen Time on the organizer’s device. Select the child. Verify that Lock Screen Time Settings reports the configuration as locked.

   If the field reads Unlock Screen Time Settings, the lock is in place [source: apple-screen-time].

The order — activity, container, contents, lock — is the order Apple documents. Reversing it produces a working report and unprotected settings.

What each setting locks — and what it does not

Parents sometimes expect one switch to fix everything.

The iOS control surface is layered. Each layer protects a different thing.

The list below is what each one buys you. It also shows what each one does not buy you.

• Family Sharing membership. This determines who can manage the child.

  It does not, by itself, set any limit [source: apple-family-sharing].

  The lock only works inside a family group.

• App & Website Activity. This turns on reporting.

  It does not restrict anything. It shows what happened after the fact [source: apple-screen-time].

• Content & Privacy Restrictions (the container). This is the switch that enables content, purchase, and privacy controls.

  It does not configure any of them. With the container on and nothing inside it configured, you have a wall with no doors [source: apple-parental-controls].

• Inside the container: web filter. Apple documents three settings.

  The default after turning the container on is the most permissive [source: apple-parental-controls].

  The filter is what blocks or limits adult websites. It is not a substitute for supervision of other browsers or in-app web views.

• Inside the container: purchases and downloads. These prevent installs, deletes, and in-app purchases from the App Store.

  They do not govern alternative app marketplaces, gift cards, or web-based payment flows [source: apple-parental-controls].

• Inside the container: account and passcode changes. This row is what stops the child from signing out of their Apple Account or resetting the Screen Time passcode from the device [source: apple-parental-controls].

• The Screen Time passcode. This is the lock itself.

  It is set inside Lock Screen Time Settings. It applies to changes from the device. The passcode does not change settings on the parent’s device. The parent does that on their own device [source: apple-screen-time].

• Communication Safety. A separate feature that blurs sensitive images in supported surfaces.

  It is not a parent-notification tool. It does not show the adult what the child saw. Apple says analysis happens on device [source: apple-communication-safety].

• Screen Distance. A separate eye-strain feature.

  Available on TrueDepth-camera devices. Default-on for under-13 children in Family Sharing [source: apple-screen-distance]. It is unrelated to content limits.

What none of this covers: cellular carrier controls, DNS-level filtering, school-managed devices, and any payment route outside the App Store in-app purchase system [claim: apple-parental-controls].

Those belong to other layers. Layered defense is the documented Austrian Safer Internet Centre guidance [source: saferinternet-technischer-kinderschutz].

Common gaps

This section names the gaps parents hit most often.

Each one is a separate record in our trick database (PM-NNN). Look up the full detection text and fix if you need to.

None of the entries below describe how a child gets around a setting. They describe the configuration that left the setting open.

• PM-003 — Screen Time settings not locked. The most common cause of limits that vanish.

  Apple documents the lock as a required step at the end of setup. Skipping it leaves every other setting editable from the device [source: apple-screen-time].

• PM-001 — Content & Privacy Restrictions not enabled. A configured-but-unprotected device.

  The container is off. None of the content, purchase, or privacy switches inside it apply [source: apple-parental-controls].

• PM-002 — App & Website Activity not enabled. No reporting, no diagnostic.

  Parents learn what happened from the child’s word [source: apple-screen-time].

• PM-004 — Over-broad web-access choice. The default after turning the container on is the most permissive setting.

  Choosing that explicitly and moving on is a common configuration gap [source: apple-parental-controls].

• PM-005 — App-age restriction omitted. The container is on, but the app-rating row inside it was never set.

  Age-rated content remains at App Store defaults [source: apple-parental-controls].

• PM-006 — Purchase / download restriction omitted. Installs and in-app purchases are governed by a separate row inside the container.

  The container being on does not configure it [source: apple-parental-controls].

• PM-007 — Privacy-change restriction omitted. The row that stops the child from signing out of their Apple Account, changing the passcode, or disabling Find My is one row among several.

  It is easy to miss [source: apple-parental-controls].

• PM-008 — Family Link used outside supported device scope. A cross-platform note.

  Apple iPhones cannot be supervised through Family Link. Screen Time and Family Sharing are the supported channels on iOS [source: google-family-link-getting-started].

  On iOS this gap shows up the other way: parents who only set up Family Link and assume Screen Time is also configured.

• PM-021 — Controls not reviewed after updates or age changes. The long-term gap.

  iOS settings change with major releases and with the child’s account-age transitions.

  Independent guidance is that controls be reviewed and updated regularly [source: consumer-ftc-parental-controls].

The trick records not addressed here (PM-009, PM-010, PM-011, PM-012 through PM-020) are Android-specific or belong to other platforms and apps — YouTube, TikTok, Roblox, Chrome, Family Link.

Those are separate articles in this wiki and have their own setup flows.

If a setting was changed anyway

The lock is not absolute.

Three signals mean a change happened despite it:

1. The child knows the Screen Time passcode. Either you told them, the device passcode matched the Screen Time passcode, or the passcode was never set [source: apple-screen-time].

   The fix is a new Screen Time passcode. Set it on the organizer’s device, not the child’s.

2. A Screen Time passcode prompt was never asked. Setup was completed without the lock step.

   Apple documents the lock as a required end-of-setup confirmation [source: apple-screen-time].

   The fix is to walk the steps above again, this time including the lock.

3. The child signed out of the Apple Account on the device. Screen Time controls pause when the child is signed out [source: apple-parental-controls].

   The container itself must block this row. That is why the privacy-change row is part of the sequence above and not an optional extra.

If you have forgotten the Screen Time passcode, Apple documents a recovery path.

The path lives on the organizer’s device, not the child’s.

The recovery is referenced as apple.screentime.passcode.change in the UI-string resource.

The underlying account used at setup is required for the recovery to succeed [source: apple-passcode-recovery].

If a setting keeps reverting despite the lock, that is an iOS-side glitch rather than a configuration gap.

Independent testing documents occasional glitches, particularly when devices in a family group are not all on the same iOS minor release [claim: wirecutter-parental-controls].

Updating every family device is the documented remedy [source: apple-screen-time].

Talking about it

A lock that the child does not understand is a lock they will work to remove.

Three small habits make the technical lock land without becoming a surveillance story:

• Tell them the lock exists and what it does. Not what it catches them at, but what it covers and what it does not.

  The lock covers device-side changes to Screen Time. It does not read their messages. It does not see their photos. It does not report their location. Communication Safety is a separate feature with its own scope [source: apple-communication-safety].

• Agree an exception route before the lock is set. A child who knows how to ask for five more minutes on a homework app does not have to bypass the limit to ask.

  Apple’s “Ask for more time” flow inside an App Limit is the documented route. The exact button is not in the menu strings Apple publishes and is verified live on the device. apple.screentime.app_limits.exception_request is intentionally unverified for that reason.

• Use the review cycle to grant autonomy as well as to close gaps. When the configuration is re-checked after an iOS update or at the child’s next birthday, decide what is appropriate for the child’s present age.

  Do not just repeat what was appropriate when the lock was first set [source: consumer-ftc-parental-controls].

  The control-versus-competence framing — structure for younger children, clear limits plus skill-building for school-age, and proportionate openly-communicated safeguards for teens — is the editorial stance this wiki takes.

The lock protects the configuration. The conversation protects the relationship. Both are needed.

Sources

• apple-screen-time — Apple Support, “Use Screen Time to manage your child’s iPhone or iPad”. The primary source for the lock-after-setup instruction and the lock’s scope [source: apple-screen-time].

• apple-parental-controls — Apple Support, “Use parental controls to manage your child’s iPhone or iPad”. The primary source for the container structure and for the rows inside it [source: apple-parental-controls].

• apple-passcode-recovery — Apple Support, “If you forgot the Screen Time passcode for an iPhone or iPad”. The organizer-side recovery procedure [source: apple-passcode-recovery].

• wirecutter-parental-controls — Wirecutter / NYT, 2026 review. Independent test reporting of confusing setup and intermittent re-enabling [claim: wirecutter-parental-controls].

• wsj-screen-time-bug — Wall Street Journal, 2023. Historical reporting on a settings-not-sticking defect that Apple acknowledged. Historical evidence, not evidence the defect persists [source: wsj-screen-time-bug].

• saferinternet-technischer-kinderschutz — Austrian Safer Internet Centre. The documented layered-defense guidance [source: saferinternet-technischer-kinderschutz].

• consumer-ftc-parental-controls — U.S. FTC. The documented periodic-re-review recommendation [source: consumer-ftc-parental-controls].