Keep parent access with the parent
The parent workspace is separate from this public website. Online parent sign-in is not available. The development workspace is available only where an operator has provisioned it; browsing this help center does not create an account.
Use parent credentials only on a parent-controlled device. A child’s device connection is not parent sign-in and must not give access to edit household rules or approve requests.
What a connection means
The local parent workspace can create a short-lived, single-use pairing code and manage device records. The shipped child apps do not yet provide an accepted, complete pairing and signed-settings workflow. A pairing code alone cannot enable the current extension or app.
Do not publish pairing codes or device credentials. An unfamiliar device record should be reviewed by the parent and revoked if appropriate. Revocation changes authorization; it is not proof an offline client has already reacted.
Saved settings are not active protection
A parent can save desired household settings in the local workspace. Release readiness also requires the child client to verify the settings, reject old or invalid updates, handle offline expiry, apply supported rules and report useful status.
These runtime paths are incomplete. No social-site rule is cleared for use. A saved revision or receipt acknowledgement must not be treated as evidence that filtering is active.
Requests and approvals today
The local workspace records requests, parent decisions and decision history. An approval currently records the decision only. It does not grant an exception, unblock a site or add time. Do not promise a child access based on the current approval screen.
When applied exceptions become available, parents will need to see their scope, duration, expiry and device result. Until then, manage any urgent access through the separately configured device controls.