Meta Quest Parental Controls: Setting Up a VR Headset for a Teen

Choose the right account for the headset

Meta Quest parental controls start with your child’s own age-correct account. For a younger child, use a parent-managed account; for a teen, connect supervision. Then check app access, play time and communication separately. An approved game can still contain interactions the parent dashboard does not control.

Before setup, write down the headset model, country, child’s account name and date of birth, and the headset’s installed software version. Keep the parent and child identities separate. On a shared headset, verify which profile is active before judging a restriction. A rule attached to one child is not evidence about a different profile.

Meta’s age-account explanation supplies these general age bands. Parent-managed accounts are available for Quest 2, Quest 3 and Quest 3S; the device age policy excludes children under 13 from the original Quest and Quest Pro. The Quest 3S requirements also retain a country-specific age caveat. Do not assume an older headset has every current supervision feature.

Use the controls offered for the actual account and model. Store delivery countries, account age requirements and an individual app’s availability answer different questions. If an account or feature is unavailable locally, changing the birth date or region is not a setup fix. For other gaming hardware, use our console parental-controls guide.

Connect the child or teen in Family Center

To connect the family, open Meta Horizon on the parent’s phone and choose Menu → Family Center. Have the child’s correct account details ready. The two account arrangements need different setup steps; a pending teen invitation does not mean supervision is active.

The parent-managed setup instructions also provide a browser route: Family Center → Go to supervision → sign in as the adult → Add / Add family member → Create an account for a child. Follow the current sign-in prompts to continue with the child’s account, and check the selected profile before handing over a shared headset.

For teens, Family Center requires acceptance before a new supervision relationship starts. Meta’s shared supervision invitation can cover several services, so confirm Horizon specifically. If the teen is missing, check the recipient identity, invitation status and selected service before changing unrelated settings.

On a shared headset, use Meta’s passcode instructions to protect your own adult profile. The protection applies to that profile on that headset; it does not automatically lock every other profile. Keep adult credentials private and confirm the child’s active profile before testing a rule. Explain which settings you will manage and when you will review them together.

Set app access without confusing it with spending or chat

To control app access, review the request for the intended child and decide whether that experience is appropriate. For a parent-managed account, Meta documents Send request on the app page. The parent opens the notification or email’s View request, then chooses Review app → Allow or Block. Meta’s download-request instructions describe the child receiving a decision notification.

For teens, the age-restricted app request is an exception to the app’s age restriction. After approval the teen can download or buy it; that exception depends on remaining connected to the parent. Family Center also supports blocking apps and installation-related insights. Do not describe an age exception as universal parental approval for every purchase.

For a teen’s manual app block: the supervision overview directs browser users to Family Center → teen’s profile → Safety settings to block apps. In the mobile app, its documented entry is Menu → Family Center → teen → Supervision settings. Use the available app-blocking controls for your chosen free test app and read back the saved rule; the public overview does not name every subsequent button. Reopen that app in the teen’s profile: the expected result is denied access. If you cannot locate or confirm the rule, record it as unconfirmed. Separately check that approval for apps rated above the teen’s age remains enabled; blocking one app does not verify that setting.

In the younger-child flow, Meta lists Purchase for your child or Go to Store as a separate purchase step for that specific paid-app download after Allow. This does not establish a universal approval gate for later charges. Check the actual store and in-app payment settings, existing subscriptions and balances separately. You do not need to place an order or start a trial to record those settings.

Harmless access check: choose an age-appropriate free app you have already reviewed. For a parent-managed child, check that its request reaches the correct adult and the decision reaches the child. If you block a previously allowed test app, try reopening it from that child’s library. Record what happens; do not infer all app permissions from one notification. If the outcome differs, recheck the account and the current app rule before trying again.

Set daily limits and scheduled breaks

To set Quest play limits, select the child or teen in Family Center and open Manage time limits. Meta’s time-management instructions describe daily limits, different allowances by weekday and scheduled breaks. A daily allowance limits duration; a scheduled break reserves a time window when access should be unavailable. Update the headset first: Meta requires current Quest software for these restrictions.

Read the scope shown for the selected Horizon profile. Meta describes time across Horizon OS and Worlds play on different devices, so do not assume the total refers only to this headset. At the daily limit, its help describes a notification, a Quest restart and access being restricted for the rest of the day. Agree a limit that fits the family’s routine; this guide does not prescribe a medical screen-time allowance.

Check the break safely: save progress, then set a short test break together. Confirm the saved interval, observe access before and during it, and check availability after it ends. Record the result with the time and active profile. Test a daily allowance separately in a session with no unsaved work; a successful scheduled break does not prove the daily budget is configured correctly.

If the rule appears saved but is not enforced, compare the active headset profile with Family Center, read back the selected day and interval, and check the headset update instructions. Reopen the relevant settings after an update. If the expected control is absent or its behavior remains different, keep that check unconfirmed and use Meta support rather than expanding permissions to make the error disappear.

Check social permissions inside the experience

Social permissions need their own check because app approval does not determine every interaction inside an app. For younger children, following someone and making them an approved contact are separate actions. Meta’s contact instructions list Their connections → Followers and following → Review permissions → Add. Connecting two parent-managed children requires both parents’ approval.

For teens, Meta’s Block social features guidance describes a control for Meta chats and calls and Worlds voice chat. It explicitly does not block social features inside other apps. The mobile route continues from the selected teen’s Supervision settings to Block social features. Review the saved rule, then inspect the chosen app’s own communication rules. A successful block of a Meta call therefore does not establish that voice inside a different game is blocked.

An approved contact can support calls, messages and invitations to allowed experiences. Yet Meta explicitly warns that other people may also be present in an app or destination and may interact with the child, depending on that experience. Inspect its own voice, text, invitation and public-room settings. Do not read “approved contacts” as “only approved people can ever be encountered.”

Hypothetical example: you allow a free multiplayer game for an 11-year-old and approve a known friend. Those two decisions let the child enter the game and connect with that friend. They do not prove that the friend’s destination excludes everybody else. If the family’s condition is known people only, check the room’s actual membership and invitation rules, plus the app’s communication controls. If you cannot establish that condition, the app-access check can pass while the social check remains unconfirmed.

Use a private session with a known adult to observe the intended voice or invitation behavior. Never join an unsuitable public world or contact strangers to test a restriction. For Worlds, inspect the available destinations and age rules on the actual account and platform: historical launch ages and older screenshots do not prove current availability. The same caution applies to third-party social apps; their account and content rules need a separate assessment.

Know what the dashboard, Watch live and casting show

Family Center insights and a live view answer different questions. The supervision dashboard provides supported information such as time and contact lists, not the content of private messages. That limitation does not mean a parent can never see a current headset session: Meta documents a separate Watch live feature.

For Watch live, the parent uses their own account in Meta Horizon → Menu → Family Center → child or teen → Horizon, if more than one service appears, then Watch live → Continue. Meta says the parent can see and hear the session. The headset needs internet, and the phone and headset must share Wi-Fi; existing casting or streaming can prevent it from starting.

The child or teen receives a notification, and an indicator remains while viewing continues. Tell them before starting. In a harmless session, check that the indicator appears, end the view from the parent’s phone and confirm it disappears. This establishes one live-view session, not continuous off-site monitoring, a recording history or access to past private messages.

Ordinary casting starts in the headset: Navigator → Quick controls → Cast → Mobile or Web. Its receiving device uses the same Meta account as the casting profile and the same Wi-Fi network; Meta also lists Bluetooth for phone casting. That account requirement differs from the parent’s separate Watch live route. Follow casting troubleshooting for account/network mismatches and networks that block the connection.

Finish with a headset acceptance sheet

A useful setup record separates a saved rule from an observed result. Copy these context fields before checking: date; country; headset model; software version; parent identity; child identity and age band; account arrangement; app/version; intended use. For each row below, write confirmed, failed or unconfirmed, then the observation and what remains outside the control.

Repeat the affected rows after changing accounts, adding an app or seeing a changed setting. A birthday transition also matters: Meta’s parent-managed-to-teen guidance describes a transition period, automatic supervision after that transition and the ability for either party to remove supervision. Review the family arrangement rather than assume the younger-child rules remain unchanged.

Keep the sheet focused on the experience your child will actually use. A confirmed rule deserves credit for its demonstrated scope; it does not certify every future game, account or room. Our broader parental-controls guide explains how device limits fit alongside an agreed plan for asking for help.

Frequently asked questions