Skip to main content

Shared Phone Control

Shared Phone Control lets a primary phone controller invite one other person to help manage the wearer's Android phones. Both controllers use the existing Phone Control screen.

The invited person does not need to be a secondary keyholder, and the phone session does not need a linked lock. Secondary keyholder access and phone access are separate permissions.

The wearer, primary controller, and invited person must all explicitly approve the same permissions before shared access starts. The wearer can decline. Screenshots and location are separate optional permissions, both off by default.

Invite a second controller​

The primary controller starts the invitation from an active Phone Control session:

  1. Open Device Control and select the wearer's phone.
  2. Open Overview → Session controls → Shared Phone Control.
  3. Search by username or choose someone from your chats. Select one person.
  4. Decide whether to enable Include live screenshots and Include location. Review what each option shares before enabling it.
  5. Read the permissions, check the approval box, and select Approve and invite.

Sending the invitation records the primary controller's approval. The wearer and invited person receive an invitation to review. All three approvals must be recorded within seven days; nobody receives secondary phone access while approval is pending.

Review and approve an invitation​

Open the Shared Phone Control invitation notification. Check the names, avatars, roles, and the requested permissions. Approval badges show who has accepted and who is still waiting.

To agree, check the approval box and choose Approve shared access. Choose Decline invitation if you do not agree. Approving a lock invitation or trusting the primary keyholder does not approve this phone invitation.

After all three approve, the secondary controller can open Device Control and select the shared phone. The wearer and controller views show a participant row identifying the wearer, primary controller, and secondary controller, with their avatars and usernames. The wearer can also see this information in the Android app.

What is shared?​

PermissionWhat the secondary controller can access
Shared phone controlsApp and browser restrictions, screen-time limits, pausing and resuming restriction checks, and still-image wallpaper changes.
Usage informationApp usage and browsing history disclosed in the invitation.
Live screenshots — optionalLive screenshots only while both this invitation's screenshot permission and the wearer's existing screenshot consent allow it. Earlier screenshot archives are not shared.
Location — optionalLocation only while both this invitation's location permission and the wearer's existing location consent allow it. History starts when shared access becomes active, and privacy zones still apply.

The secondary controller cannot transfer ownership, replace the primary controller, end the primary Phone Control session, invite further controllers, or change consent locks. Protected-app approvals, saved restriction profiles, video wallpapers, popup messages, blocking overlays, automation, and lock or device punishment settings remain primary-only.

Both controllers manage the same settings. Selecting another phone changes the device information you inspect; it does not create separate rules for that phone. Screen-time usage is counted separately for each phone. See Multi-Device Support.

If a settings change conflicts with a newer edit, refresh the view and try again.

Leave or end shared access​

Any of the three participants can end shared phone access.

  • Secondary controller: open Overview → Session controls, select Leave shared control beside Shared Phone Control, and confirm.
  • Primary controller: open Overview → Session controls → Shared Phone Control, choose End shared access, and confirm.
  • While an invitation is pending: use Decline invitation or Cancel invitation in its permissions view.

Ending shared access removes the secondary controller's future phone access. The primary session and saved restrictions remain in place. It does not remove a separate secondary-keyholder lock role, undo completed changes, or erase information already viewed.

Shared phone access also ends when the primary Phone Control session ends or its primary controller changes. Older invitations explicitly linked to a secondary-keyholder role also end when that linked role ends.

Rejoining or changing the agreed permissions requires a fresh invitation and approval from all three people.

Frequently asked questions​

Can I decline a second phone controller?​

Yes. Shared phone access cannot begin without your explicit approval as the wearer. Declining the invitation does not end the existing primary controller's session.

Does my secondary keyholder automatically get phone access?​

No. They need a separate Shared Phone Control invitation and all three approvals. Someone who is not a keyholder can also be invited.

Can I approve shared control without sharing screenshots or location?​

Yes. Both options start off and can remain off. If an invitation requests sharing you do not want, decline it and ask the primary controller to send a new invitation with those options disabled.

Does screenshot permission include verification or combination photos?​

No. Phone screenshots are separate from lock verification photos. Verification photo access requires its own secondary-keyholder permission; combination photos are excluded from the secondary-keyholder role.

Can the permissions be changed after approval?​

End the existing shared access and create a new invitation with the desired permissions. All three people must approve the new invitation. Turning off the wearer's existing screenshot or location consent also stops that sharing while it remains off.

Does approved access expire after seven days?​

No. Seven days is the deadline for accepting the invitation. Approved access lasts until it is ended or its Phone Control session conditions no longer apply.

Does leaving shared control unlock the phone?​

No. It removes only the secondary controller's access. The primary session and its saved restrictions stay in place.

For setup and Android permissions, see Device Control. For the separate lock role, see Secondary Keyholders.