Meta Advanced Access: Requirements and How to Get It

Meta's documentation draws the line by who the user is. With Standard Access, a permission "can only be requested from app users who have a role on the requesting app." With Advanced Access, it "can be requested from any app user," and features with Advanced Access are active for everyone who uses the app.

Any app that publishes or reads on behalf of people outside your own team. A social-publishing SaaS is the clearest case: none of your customers have a role on your Meta app, so Standard Access covers none of their traffic. Permissions like instagram_business_content_publish and pages_manage_posts only work for those accounts once they carry Advanced Access.

The exception is an internal tool. Meta's Business Verification documentation says apps used only by people with a role on the app don't need verification, so a script that posts to your own company accounts can stay on Standard Access. Consumer apps have one more rule: they must be in Live mode before they can request Advanced Access permissions from users without a role.

From Meta's access levels page and its App Review submission guide, a request needs all of this:

• A verified business connected to the app. An app admin connects the app to a business portfolio in the App Dashboard. Someone with an Admin role in that business completes verification.
• One successful API call per permission. Meta asks for at least one successful call using each permission you request, made within 30 days of submitting. The call data is logged within 2 days, so don't make the call and submit the same afternoon.
• A screen recording per permission or feature. Any requested permission without one will not be approved. Meta asks for 1080p or better, a monitor width of 1440 or less, and no audio.
• Answers to the data handling questions, when the request prompts for them.
• A reachable app. Reviewers test the app against your recordings. If they can't get in, the whole submission is rejected.

Business Verification has been the gate since Meta's February 1, 2023 announcement: developers must verify their business to get Advanced Access for any permission. Existing apps had to be linked to a verified business from May 1, 2023, and Meta said apps without one would have advanced permissions revoked. The same post says individual verification is no longer accepted once business verification is done. The Meta API deprecations timeline puts that rule next to the other dated changes.

Verification is a separate process from App Review. You connect the app in the App Dashboard, but the verification itself happens in Meta Business Manager, and only a business admin can finish it. Meta keeps the list of accepted documents in its Business Help Center. Make sure the legal name and address you enter match those documents exactly before you upload anything, because a mismatch sends you back to the start.

Start this the week you create the Meta app. Verification doesn't depend on your code, and an unverified business can't receive Advanced Access however good the App Review submission is.

The flow in Meta's App Review submission guide, in order:

1. Open App Review, then the Permissions and Features tab, in your app dashboard.
2. Search for each permission or feature you need and click Request advanced access on it.
3. Click Continue the Request when every permission is on the list.
4. Complete Business Verification if you are prompted and haven't done it yet.
5. Answer the data handling questions if you are prompted.
6. Upload one screen recording for each permission or feature, showing how to test it in your app.
7. Click Submit for Review and accept the Platform Onboarding Terms.

Ask only for permissions the shipped product uses. Each one is reviewed and granted on its own, so approval for Instagram publishing says nothing about Page publishing. What reviewers check in the recordings, and the usual rejection reasons, are in the App Review walkthrough.

Plan for two clocks that run one after the other. Business Verification comes first, and Meta doesn't publish a turnaround for it. App Review comes second: the submission guide says you should receive a decision within a week after you submit. Add the 2 days Meta needs to log your test API calls before you submit.

Teams that budget only for App Review usually find that verification is what moves the launch date, most often because of a document that doesn't match the business details on file. Budget for at least one rejection and resubmission on the review side too.

Approval is not permanent paperwork. Apps with Advanced Access must complete Data Use Checkup, which Meta describes as an annual certification of how the app uses its APIs. Switching a permission from Advanced back to Standard immediately deactivates it for every user without a role on your app. If access was removed, the Get Advanced Access button in App Review, under Permissions and Features, is where you restore it.

Advanced Access also doesn't keep customer tokens alive. It decides which users can grant a permission. Each grant still produces a token with its own lifetime, and an Instagram long-lived token expires after 60 days unless you refresh it. Those are two separate failure modes, and both look like "publishing stopped working" from the customer's side. Our guide to getting an Instagram access token covers how each grant produces that token.

Everything except the final live call. With PostGate, a pg_test_ key runs the full publishing lifecycle against a sandbox adapter: validation, queued jobs, per-target status, delivery logs, retries and webhooks all behave as they do live, and no social network is called. See test mode and sandbox. Once Meta approves your own app, you can store its credentials as a bring-your-own provider app, which keeps its quotas and approval status isolated to your organization (a plan-gated feature).