Skip to main content
The Facebook OAuth Integration page is used to connect Facebook Pages to the platform for inbox, engagement, and automation use cases. This setup allows businesses to manage Facebook conversations and Page interactions from one shared workspace.

​
Why This Integration Is Required

Many Messenger and Page engagement workflows depend on a connected Facebook Page. Facebook OAuth is required to:
  • authenticate the business owner
  • list and select available Facebook Pages
  • subscribe pages for webhook events
  • enable Page-level messaging, comments, posts, and insights
Without approved Facebook permissions, Page connection and related inbox/automation features will not work in production.

​
Required OAuth Scopes

These are the scopes the platform requests when a user connects a Facebook Page:
  • pages_show_list
  • pages_manage_metadata
  • pages_messaging
  • pages_read_engagement
  • pages_read_user_content
  • pages_manage_engagement
  • pages_manage_posts
  • read_insights
  • business_management
  • public_profile
Request only these scopes (and any additional ones your deployment actually uses). Extra unused permissions increase Meta review risk.

​
Review Submission Pack

​
1) App Use-Case Description

Use this when Meta asks: “Please provide a detailed description of how your app uses the permission or feature requested, how it adds value for a person using your app, and why it’s necessary for app functionality.”

​
Overall Description

Our platform is a customer communication and automation system used by businesses to manage Facebook Page interactions from a unified team inbox. Facebook OAuth is used so a business user can securely connect their own Facebook Page, authorize required permissions, and enable messaging, engagement, publishing, and insights workflows. Each requested permission maps to a visible feature in our product, such as selecting a Page, reading engagement and user content, managing comments, subscribing webhook events, sending replies, publishing posts, and viewing insights. These permissions are necessary for app functionality and are only used after explicit user consent.

​
2) Scope-by-Scope Justification

​
pages_show_list

Required to display Facebook Pages the authenticated user manages, so they can select which Page to connect to our platform.

​
pages_manage_metadata

Required to subscribe and maintain Page webhook metadata so message and engagement events are delivered reliably to our platform.

​
pages_messaging

Required to send and receive Facebook Page messages through the platform inbox and automation rules.

​
pages_read_engagement

Required to read Page engagement context (such as comments and interactions) used for inbox visibility, moderation, and engagement workflows.

​
pages_read_user_content

Required to read user-generated content on the Page (for example comment text and related content) so agents and automations can respond accurately.

​
pages_manage_engagement

Required to manage Page engagement actions such as moderating or responding to comments from the platform.

​
pages_manage_posts

Required for businesses that use our platform to create, publish, or schedule Page posts and related workflows.

​
read_insights

Required to retrieve Page insights so users can analyze performance and engagement inside the platform.

​
business_management

Required to access business assets and complete account/page linkage securely during connection.

​
public_profile

Required to display basic account identity for secure session and connection confirmation.

​
3) Screen Recording Checklist

Meta may ask for a recording that proves each permission is used exactly as described.

​
What to Record

  1. Show your platform URL and sign in.
  2. Open Platform Settings -> Facebook OAuth (or channel connection settings).
  3. Start Facebook connection flow and show OAuth consent.
  4. Select a Page and confirm successful connection.
  5. Demonstrate feature usage tied to requested permissions:
    • show page list selection (pages_show_list)
    • show messaging action (pages_messaging)
    • show engagement or comment visibility (pages_read_engagement, pages_read_user_content)
    • show comment moderation/reply (pages_manage_engagement)
    • show event/webhook readiness (pages_manage_metadata)
    • show publish action (pages_manage_posts)
    • show insights screen (read_insights)
  6. Show final connected state in your platform.

​
Video Quality Checklist

  • Use one continuous recording (recommended 4-10 minutes).
  • Include captions or voice-over explaining each permission usage.
  • Mask secrets and personal information.
  • Use production-like UI, not mock screens.

​
4) Upload Instructions

  1. Upload video to Google Drive (Anyone with link can view) or unlisted YouTube.
  2. Open Meta App Dashboard -> App Review -> Permissions and Features.
  3. Open each permission request and provide:
    • permission description
    • reviewer test steps
    • video link
    • test account credentials if requested
  4. Verify privacy policy URL, terms URL, and domain are live before submitting.

​
5) Pre-Submission Checklist

  • Permissions requested in Meta exactly match the Required OAuth Scopes list above.
  • Page connection and webhook flow are working before review submission.
  • Video shows one real action per requested permission.
  • Privacy policy, terms, and domain verification are complete.
  • Reviewer steps and test credentials are included when required.

​
Important Notes

  • Keep requested scopes minimal and feature-matched.
  • Mismatch between requested permissions and recorded flow is a common rejection reason.
  • If a scope is not used in your current product flow, remove it before submission.
Last modified on August 7, 2026