Guides · social · Verification-gated

Meta App Review (advanced access)

Meta's review of how your app uses each permission and feature. Needed before people without a role on your app (or your business) can grant permissions or use features. You submit screen recordings and usage descriptions per permission, answer data handling questions after business verification, and Meta says to expect a decision in about a week.

Researched · not yet run liveLast researched 25 October 2026 · Meta · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.

Who owns what

App Review is per app. An admin of the app submits; approval attaches to that App ID. For advanced access the app must be connected to a business portfolio that has passed business verification.

  • Meta app (App ID) project owned by the company
  • Verified business portfolio organisation owned by the companyBusiness verification is required for advanced access to any permission.

Apps used only by people with a role on the app (or in the business that claimed it) don't need App Review.

Business-to-business apps (Tech Providers) may also need access verification for certain permissions.

Have ready

  • One screen recording per permission or feature, 1080p or better, English UI where possible, no audio, starting logged out and ending logged in, showing the permission being granted and the data being used. · Any permission or feature without a recording is not approved, and missing ones get the submission rejected. [3]Needed for: Write usage descriptions and upload recordings
  • A 1024x1024 app icon with no Meta trademarks or logos. · Required before submission. [2]Needed for: Finish building and make test calls
  • The app's public privacy policy URL, shown to users during Meta login. · Checked in the Complete App Settings step. [2]Needed for: Complete App Settings
  • A reachable app or website, plus written access instructions and any test credentials for your own (non-Meta) sign-up. · If reviewers can't access the app, the entire submission is rejected. [1]Needed for: Tell reviewers how to reach the app
  • For each permission, a specific, unique explanation of how the app uses it (no copy-paste between permissions). · Required usage descriptions. [2]Needed for: Write usage descriptions and upload recordings

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Finish building and make test calls

    Finish development, upload the 1024x1024 icon, and make at least one successful API call for every permission you will request (through your app or the Graph API Explorer) within 30 days of submitting.

    • Guided by hand
    If something goes wrong (1)
    • The Request advanced access button is greyed out.: Meta needs to log a successful API call for that permission first; logging can take up to 2 days. [2]

    Where: https://developers.facebook.com/tools/explorer/

  2. Choose permissions and features

    In App Review > Permissions and Features, request advanced access only for what the app needs.

    • Guided by hand
    • Human step: You press submit
    • After: Finish building and make test calls

    Where: https://developers.facebook.com/apps/

  3. Complete business verification if prompted

    Meta may ask you to start or finish business verification at this point. See meta/business-verification.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Choose permissions and features
    The provider says
    Meta's Business Help Centre says a business verification decision may take up to 14 working days (see meta/business-verification). [6]
  4. Answer the data handling questions

    After business verification is approved, answer the data handling questions; Meta evaluates the answers immediately (up to about 30 seconds).

    • Guided by hand
    • Human step: You press submit
    • After: Complete business verification if prompted
  5. Complete App Settings

    Check the app icon, privacy policy URL, app purpose (yourself or your own business vs clients), app category and primary contact email, which gets all App Review notifications.

    • Guided by hand
    • Human step: You press submit
    • After: Choose permissions and features
  6. Tell reviewers how to reach the app

    Say whether users log in with Meta, confirm platform settings and give reviewers access instructions. Reviewers use their own test accounts; never give your personal developer account credentials.

    • Guided by hand
    • Human step: You press submit
    • After: Complete App Settings
  7. Write usage descriptions and upload recordings

    For each permission and feature, write a specific description of how it is used and upload the matching screen recording.

    • Guided by hand
    • Human step: You press submit
    • After: Tell reviewers how to reach the app
  8. Submit for review

    Click Submit for Review and accept the Platform Onboarding Terms. Keep the app in Development mode until review is complete.

    • Guided by hand
    • Human step: You accept the terms
    • After: Write usage descriptions and upload recordings, Answer the data handling questions
    The provider says
    Meta says to expect a decision within about a week. [2]
    People report
    Older forum posts report two weeks to over a month and slow support responses (anecdotal, several years old) [to verify current experience]. [10]
    If something goes wrong (5)
    • Whole submission rejected because reviewers could not access the app.: Make the app publicly reachable or give clear access instructions and test credentials for non-Meta sign-up, then resubmit. [1]
    • A permission was denied because reviewers couldn't see why it is needed.: Re-record showing the full grant flow and the feature that uses the data, add captions for unclear UI, and make the usage description specific. [3]
    • Submission rejected because a permission or feature had no recording.: Add a recording for every listed permission and feature, or remove ones you don't need. [3]
    • Rejected for requesting permissions the app doesn't need.: Remove the unneeded permissions and resubmit with only what the app uses. [2]
    • App is already Live and you can't demonstrate a new permission.: Live apps can't use unapproved permissions; build the recording in a separate test app and include its App ID in the usage details [to verify current guidance]. [2]
  9. Complete access verification (Tech Providers only)optional

    If your app is used by other businesses and requests listed permissions (e.g. ads_management, pages_manage_posts, instagram_basic, whatsapp_business_management), a business admin fills in the access verification form under App Dashboard > Basics > Verifications.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Complete business verification if prompted
    The provider says
    A decision usually comes within about 5 days of submitting the form. [4]
    If something goes wrong (2)
    • API calls from other businesses fail with error code 100. (100): The business is not access-verified; complete business verification, make sure the business has no restrictions, then submit access verification. [4]
    • Access verification denied.: You can reapply if your use case changes. [4]

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can get you bannedThe rules say

Don't hand reviewers your own login

Reviewers use their own test accounts; Meta says not to provide your personal Meta developer account credentials. [2]

Can cost moneyThe rules say

Changes can trigger re-review

Changing Basic or Advanced settings after submitting may require re-review, and material changes to app functionality or data scope need a new App Review submission under the Platform Terms. [7]

Can cost moneyThe rules say

Missed Data Use Checkup means reviewing again

If an app is deactivated for missing its annual Data Use Checkup, its use cases, permissions and features must be re-approved through App Review. [9]

Worth knowingThe rules say

Unused permissions can lapse

Meta may end access to permissions or features you haven't used for 28 days. [7]

Worth knowingPeople report

Reviews can run long

Developers on Meta's own forum have reported reviews well beyond a week and support tickets going unanswered; older, anecdotal reports. [10]

Pricing

  • No fee for App Review is mentioned in Meta's App Review docs.

Source [2]

For agents

The same entry as JSON: /api/v1/entries/meta/app-review · requirements /api/v1/requirements/meta/app-review · terms /api/v1/terms/meta/app-review.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Meta App Review (advanced access), and how long will it take?"
  → tools/call requirements { "provider_id": "meta/app-review" }

Sources

  1. App Review (Meta for Developers) Who needs App Review; approved vs unapproved permissions/features; whole submission rejected if reviewers can't access the app; specific items denied if they can't be tested. · accessed 25 October 2026 · official
  2. App Review Submission Guide (Meta for Developers) Prerequisites (1024x1024 icon, one successful API call per permission within 30 days, logging up to 2 days), business verification at step 1.5, data handling questions after verification, app settings, reviewer access instructions, no personal credentials, unique usage descriptions, Platform Onboarding Terms, decision in about a week, keep Development mode until review completes. · accessed 25 October 2026 · official
  3. Screen Recordings (Meta for Developers) Recording requirements (every permission/feature, logged-out to logged-in, grant flow, data use, English UI, captions) and rejection consequences. · accessed 25 October 2026 · official
  4. Access Verification (Meta for Developers) Tech Provider access verification for apps used by other businesses requesting listed permissions; code 100 error if unverified; decision usually within about 5 days; requires business verification and an unrestricted business. · accessed 25 October 2026 · official
  5. Developer Platform requiring Business Verification for Advanced Access (Meta developer blog, 1 Feb 2023) Business verification required for advanced access to any permission. · accessed 25 October 2026 · official
  6. Verifying your business in Meta Business Suite (Meta Business Help Centre) Business verification decision may take up to 14 working days. · accessed 25 October 2026 · official
  7. Meta Platform Terms Material changes need re-submission through App Review; enforcement; unused permissions removable after 28 days. · accessed 25 October 2026 · official
  8. App Modes (Meta for Developers) Live mode only allows approved permissions and features; switching to Live after App Review. · accessed 25 October 2026 · official
  9. Data Use Checkup FAQ (Meta for Developers) Annual checkup; deactivated apps must have use cases, permissions and features re-approved through App Review. · accessed 25 October 2026 · official
  10. Why App Review is taking so long? (Meta Developer Community Forum thread, older posts) Developer reports of reviews taking two weeks to over a month, unanswered support tickets, and rejections they believed were made without watching screencasts. Anecdotal and several years old. · accessed 25 October 2026 · community

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Meta is not affiliated with verapli.