Check the child account, family-group relationship, request type, and approval status in Microsoft Family Safety before troubleshooting email. This is the right first move when a child’s app access, extra screen time, or purchase request appears to be missing or stuck.
This guide is for parents checking whether an app access request was submitted.
It also helps guardians handling screen time or purchase approvals with no visible status change.
Family account managers can use it to separate an in-app request from an email notification.
Last updated October 30, 2026. The process and update details were checked against Microsoft’s September 8, 2026 Family Safety announcement and current Microsoft Support guidance.
2026 Microsoft Family Safety parental approval not showing: start with the request type
Microsoft’s 2026 announcement says the app access, screen time extension, and purchase approval processes have improved and are faster than before. It does not promise that every request will appear immediately, that every device will behave the same way, or that every request is delivered by email. Keep the request record separate from a notification about that request.
| Request type | What to check first | What approval affects | What not to assume |
|---|---|---|---|
| App access | The child account, app name, and pending request in Family Safety | The requested app access | That approval clears every other account or device restriction |
| Extra screen time | The child’s request and its displayed status | The additional time requested through Family Safety | That a device prompt and an email are the request record |
| Purchase | The purchase request and applicable family spending settings | The purchase approval process | That email is the only place to find a request |
Use the row that matches the child’s action before changing a family setting. Microsoft describes family roles and permissions separately from spending limits and screen time settings. For example, changing a limit directly is not the same action as responding to a child’s request. The Family Safety roles and permissions guidance explains how family roles relate to management.
A parent can check Family Safety in the app or on the web. In either view, select the same child account before interpreting the status. A request associated with one child should not be judged from another child’s page or an adult’s account view.
App access and extra screen time need different checks
When an application request is missing
Start with the exact app and the child who asked to use it. Open Family Safety and inspect the area for the matching request. If nothing appears, compare the web view before concluding that the request failed.
Confirm that Family Safety is set up for the relevant family account and that the child is associated with the expected group. Microsoft’s Family Safety setup instructions cover the service setup. For membership, its family-group instructions explain how to add people and check group membership.
If the request is visible and marked approved but the app still will not open, treat that as a different issue from a missing request. Check that the approval belongs to the correct child and app. Then note the current device message and review the applicable family settings. An approval record does not establish that every other restriction on the account or device has also been cleared.
When the child asks for more time
A child’s request for extra time is not the same as a parent changing a screen time limit. First check the child’s request and the status displayed for it. If the parent edited a limit directly, verify the current setting across the relevant device view. Microsoft’s instructions for setting screen time limits across devices describe that settings workflow; it should not be mistaken for a response to a pending request.
| What appears on screen | Distinction to verify | Next check |
|---|---|---|
| The child sees a request prompt, but the parent sees no pending item | The parent may be viewing a different child or request category | Select the child who initiated it and inspect the matching request area |
| The parent changed a time limit, but the request still looks unresolved | A settings change and a request response are different actions | Check the request status separately from the current limit |
| The request looks approved, but the device still shows a restriction | Approval status and the device’s current access state may differ | Compare the account, device message, and applicable setting |
These are troubleshooting checks, not claims about a universal Family Safety defect. Microsoft’s announcement describes an overall process improvement, not a guarantee that every status synchronizes immediately.
Purchase approval is a separate workflow
A purchase request is not an app access request or a screen time extension. Select the correct family member, inspect the purchase-related area, and review the family’s spending settings. Microsoft’s spending limits and purchase notification guidance is the reference for that workflow.
Do not infer that a purchase request was never made just because an email is missing. The official information cited here does not establish email as the exclusive delivery method for every purchase request. A message about account verification is not proof that a purchase is awaiting approval, either. Keep the request category clear while checking.
For follow-up, record the child account selected, request type, device involved, status shown in Family Safety, and exact on-screen message. This gives support concrete details to investigate without guessing about a delay or notification channel.
Compare the available checks before changing settings
| Check | What it can clarify | Advantage | Limitation |
|---|---|---|---|
| Child account and family-group membership | Whether the parent has selected the right family member | Helps avoid investigating a request under the wrong account | Does not approve a request |
| Request category and status | Whether the issue concerns app access, extra time, or a purchase | Keeps the parent in the matching workflow | A visible approval may not explain every device restriction |
| Family Safety app and web view | Whether the available views show different statuses | Makes it easier to identify what is currently visible | A mismatch alone does not explain its cause |
| Email inbox | Whether a notification arrived at the expected address | Provides a secondary signal | No email is not proof that no request exists |
For an initial check, use the first three rows in order. Email can help, but it is supporting evidence—not the approval system itself. If the status remains inconsistent, use Microsoft’s Family Safety troubleshooting guidance and provide the details already recorded.
Follow a consistent sequence when an approval is missing
- Select the child who made the request. Confirm the account shown in Family Safety instead of relying on the device name or a remembered email address.
- Verify family-group membership. Check that the child and approving adult appear in the expected group and that the adult has the relevant role. The roles and permissions reference above explains the distinction between family members and managers.
- Name the request category. Write down whether the issue is app access, extra screen time, or a purchase. Do not use a purchase setting to troubleshoot an app request.
- Inspect the matching status in Family Safety. Check the app, then compare the web view if available. Keep the same child selected in both.
- Separate a request response from a direct settings change. For screen time, note whether the child asked for extra time or the parent edited a limit. For app access and purchases, inspect the corresponding request instead of assuming another setting answered it.
- Compare the device message with the parent view. Record what the child sees and what Family Safety shows. Avoid changing unrelated limits just to make a device prompt disappear.
- Escalate with a concise record if the views still disagree. Include the account, request category, device, status shown in each view, and exact message. Use the official troubleshooting route rather than guessing at a notification delay or cause.
This sequence limits unnecessary setting changes. It also gives support a clearer description than “the email never arrived” or “approval did not work.” If the child’s device is shared, note which child account was active when the message appeared. That small detail can help distinguish an account-selection issue from a request-status issue.
Frequently asked questions
Where should a parent look for an approval request?
Open Family Safety, select the family member who made the request, and check the section that matches its type. App access, additional screen time, and purchase approval are separate workflows. If a request is absent in one view, compare the other view before treating an email inbox as the definitive record. Keep the child account selected consistently while checking.
Why can a child still be blocked after an app request was approved?
An approval may not remove every restriction on the device or account. Confirm that the status belongs to the correct child and application, then check the relevant family settings and the message shown on the device. If access still fails, record those details and follow Microsoft’s troubleshooting guidance rather than changing unrelated controls or assuming that the approval was reversed.
Do purchase requests always arrive by email?
Do not treat email as the only notification channel. Check the purchase request in Family Safety and confirm which adult account is responsible for approvals. Review the family spending settings as well. Microsoft’s support information describes spending limits and purchase notifications, but an absent email by itself does not establish that no request was submitted.
What should a parent do if a screen time request is missing?
First verify the selected child and the family-group relationship. Then distinguish a child’s request for extra time from a parent changing the limit directly. Compare the Family Safety app with its web view, keeping the same child selected. If neither shows the expected status, save the device, account, and on-screen message details before contacting Microsoft Support.
What the 2026 update confirms—and what it does not
Microsoft said on September 8, 2026, that app access, screen time extension, and purchase approval processes had improved and were faster than before. That is a general statement about the process. It is not a promise of immediate results in every household, and it does not confirm that all requests are delivered by email.
The practical response is still to check the family member, request category, and status in Family Safety. If the record remains missing or inconsistent, document what appears and use Microsoft Support. Do not bypass parental controls or platform rules to work around a display problem.
Keep family approval separate from the email address
Family Safety approvals depend on the family account, group membership, and the platform’s request workflow. An email address by itself does not approve an app, extend screen time, or authorize a purchase. It also cannot replace an account that must remain accessible for ongoing family management. If group membership needs review, use the family-group instructions linked above.
For a child’s ordinary, short-term service signup, a temporary inbox can serve a narrower purpose: separating a low-continuity registration from the household’s main address. It should not replace a long-term family account, a recovery address, or an address needed for ongoing school and safety notices. Families weighing that option against an alias can read this guide to temporary email and email aliases. The PostTmp privacy guide can help assess whether temporary email suits a particular signup.
When a child only needs an address for a short-lived, nonessential service, PostTmp offers a way to keep that signup separate from the household’s main inbox. Keep Microsoft Family Safety and any account used for continuing family management on a stable, accessible address. Temporary email is for separating low-continuity registrations, not replacing parental approval or long-term account access.
Frequently asked questions
Where should I look for a Microsoft Family Safety approval request?
Open Family Safety or its web view, select the family member who made the request, and check the section relevant to the request type. App access, extra screen time, and purchase approval are separate workflows. If the request is absent in one view, compare the other before treating an email inbox as the definitive record.
Why can a child still be blocked after an app request was approved?
An approval may not remove every restriction on the device or account. Confirm that the approval belongs to the correct child and application, then check the current request status and the applicable family settings. If the app still cannot open, record the displayed message and device details and use Microsoft's troubleshooting guidance rather than changing unrelated controls.
Do Microsoft Family Safety purchase requests always arrive by email?
Do not treat email as the only notification channel. Check the purchase request and family spending settings in Family Safety, and confirm which adult account is responsible for approvals. Microsoft's support information describes spending limits and purchase notifications, but an absent email alone does not establish that no request was submitted.
What should I do if a child's screen time request is missing?
First verify the selected child and family-group relationship, then distinguish a child's request for extra time from a parent changing the time limit directly. Compare the Family Safety app with its web view. If neither shows the expected status, save the device, account, and on-screen message details before contacting Microsoft Support.
Task lasting more than a day? Give it a controllable alias
Forward long-term messages to your real inbox, then pause or delete the entry point when needed.