Set up your Meta app for Facebook Messenger and get the Page permissions approved.
Tenants connect a Facebook Page through Embedded Signup (Facebook Login) or Manual Connect (Page ID and Page Access Token). Embedded Signup runs on your Meta app, so the app needs the Messenger product, a Facebook Login for Business configuration, and Advanced Access to the Page permissions listed below.
Until App Review is approved, the permissions work only for people who hold a role on your app (admins, developers, testers). Use this to test the connection before you submit for review.
The platform requests these permissions when a tenant connects a Page. Include all five in your Facebook Login configuration.
Permission
What the platform uses it for
Access level
pages_show_list
Lists the Pages the tenant manages so they can choose one to connect.
Standard. No App Review needed.
pages_messaging
Sends and receives messages in the Page’s Messenger conversations.
App Review
pages_manage_metadata
Subscribes the Page to your webhook so events reach the platform.
App Review
pages_read_engagement
Reads the Page profile (name, category) shown in the tenant’s channel list.
App Review
business_management
Lets tenants connect Pages that are owned by a Business Portfolio.
App Review and Business Verification
pages_messaging and pages_manage_metadata are the two that matter most. Without both, a Page cannot be subscribed to the webhook and no messages arrive.
The platform subscribes to these Page events. You do not select them in the Meta dashboard — Connect Webhook registers them at the app level, and each Page is subscribed when a tenant connects.
The seven Page events the platform subscribes to
Event
Sent when
messages
A customer sends a message to the Page.
messaging_postbacks
A customer taps a button, Get Started, or a persistent menu item.
message_deliveries
A message sent by the Page is delivered.
message_reads
A customer reads a message sent by the Page.
message_echoes
The Page sends a message, including messages sent outside the platform.
messaging_handovers
The conversation is handed over between apps (Handover Protocol).
messaging_referrals
A customer starts a conversation from an m.me link or a click-to-Messenger ad.
In the App Dashboard, go to App Review → Permissions and Features.
2
Request Advanced Access
Request Advanced Access for pages_messaging, pages_manage_metadata, pages_read_engagement, and business_management.
3
Describe each permission and attach the video
For each permission, describe in one or two sentences how tenants use it on your platform, and upload the screencast.The video must show the Facebook Login dialog granting the permission and the feature in use — for example, connecting a Page and replying to a customer message.
4
Provide reviewer instructions
Provide step-by-step instructions and a test login (a tenant account on your platform) so Meta’s reviewer can repeat the flow.
Meta rejects the whole submission if the reviewer cannot log in and test the integration. Do not use your personal Facebook credentials as the test login.
5
Complete Business Verification
Finish Business Verification in your Business Portfolio if it is still pending.
Meta notifies you by email and in Developer Alerts. Review typically takes from a few days to a few weeks.
Manual Connect does not go through Facebook Login, so it does not use the configuration from Step 3 above. Tenants supply a Page ID and a long-lived Page Access Token, generated in their Meta Business Suite under System Users → Generate Token with the pages_messaging permission scoped to the Page.Enable it from Settings → Channels → Messenger if you want to offer this option alongside Embedded Signup.
