Test 06
Use these exact URLs, descriptions, and screens in the Meta submission. Every permission is tied to one visible action and one real Graph API result.
Reviewer access
Copy-ready overview
1. Open https://sds-hub.encore-system.com/social-hub. The public Dashboard opens immediately; no login, password, access code, payment, or SDS administrator account is required.
2. In Public Meta content, confirm that the official Encore Systems Facebook Page is visible and open https://www.facebook.com/61588710962284 using the Original Meta Content link.
3. Return to Dashboard and select Fetch fresh oEmbed HTML. The server calls Meta's oEmbed Page endpoint and renders the returned HTML as the primary preview. Expected result: “Live oEmbed HTML” and 2/2 green oEmbed checks. If the feature is pending, please enable Meta oEmbed Read for this review attempt and repeat the action.
4. Open Connect a Page, continue with Facebook, approve the listed Page permissions, and select a Meta reviewer test Page. Social Hub disables Messenger AI and Order Bot before and after connection; comments always remain agent handled.
5. Complete Test Messenger, Test Comments, and Test Replies in order using the unique reviewer code shown in Social Hub. Each screen displays the exact captured or delivered Meta event.
6. Return to Dashboard. A successful end-to-end test shows every live readiness item in green.
Copy-ready oEmbed submission
Social Hub uses Meta oEmbed Read only to render public Facebook Page content inside a front-end reviewer and social-channel dashboard. When the public Dashboard opens, the server sends the configured official Encore Systems Facebook Page URL to Meta's oEmbed Page endpoint using the app access token. The returned embed HTML and basic metadata are rendered in the Public Meta content section beside a direct link to the original Facebook Page.
This gives Social Hub users an in-context preview of the exact public Page associated with their social-channel setup before they test Messenger, comments, and replies. The feature is necessary because the public Meta content must be displayed inside the Social Hub interface; without oEmbed Read, users would have to leave the application and could not verify the selected public Page in context. No private content is requested or embedded.
Least privilege
Meta oEmbed ReadDashboardPurpose: Display a public Facebook or Instagram post or video on the Social Hub dashboard.
API proof: GET /oembed_video, /oembed_post, /oembed_page, or /instagram_oembed based on the supplied public URL.
Expected result: The returned Meta embed HTML is rendered beside a direct link to the original public content.
pages_show_listConnect a PagePurpose: Show the authorizing user the Facebook Pages they can connect to Social Hub.
API proof: GET /me/accounts
Expected result: The reviewer selects one Page returned by Meta.
pages_manage_metadataConnect a PagePurpose: Subscribe the selected Page to Messenger and feed webhooks.
API proof: POST /{page-id}/subscribed_apps
Expected result: The selected Page is connected and webhook events can be received.
pages_read_engagementTest CommentsPurpose: Read recent public posts from the selected Page so the reviewer can choose the exact post used for the comment test.
API proof: GET /{page-id}/feed
Expected result: Recent Page content appears inside Social Hub.
pages_read_user_contentTest CommentsPurpose: Receive and display a user comment made on content owned by the connected Page.
API proof: Page feed webhook
Expected result: The matching reviewer-code comment appears in the session event log.
pages_manage_engagementTest RepliesPurpose: Let a human agent reply to a captured Page comment from Social Hub.
API proof: POST /{comment-id}/comments
Expected result: The manual reply is delivered below the original Facebook comment.
pages_messagingTest Messenger and Test RepliesPurpose: Receive a customer Messenger message and let a human agent send a reply during the permitted messaging window.
API proof: Page messages webhook + POST /{page-id}/messages
Expected result: The inbound message is captured and the manual reply is delivered in Messenger.
Screen recording
Record the exact Social Hub screen named for the requested feature or permission. Keep the address bar visible so the website URL can be verified.
Start before the action, complete the Facebook or Social Hub action, and keep recording until the real result appears on screen.
Upload a readable recording for Meta oEmbed Read and each requested Page permission. Reuse the same connected test Page, but demonstrate the specific action described above.
Use the same menu names, order, reviewer code, expected result, and reviewer URL shown on this page.
Before submitting, confirm the Meta App icon, category, contact email, Privacy Policy URL, Data Deletion Instructions URL, data handling answers, and business verification are complete in the Meta dashboard.