docs(facebook): guide users past the Meta app use-case wizard

[giladresisi]

What

Updates the self-host Facebook provider setup guide for Meta's current app-creation wizard:

• Adds a step showing the "Add use cases" screen (with the "All" filter selected) and a new screenshot.
• Clarifies that no use case should be selected: the working path is "Other" under "Looking for something else?" at the bottom of that screen.

Why

Meta's wizard now funnels new apps into "use cases" (e.g. "Authenticate and request data from users with Facebook Login"). Apps created through a use case cannot request the permissions Postiz needs; the OAuth dialog fails immediately with "Invalid Scopes" listing every requested scope (pages_show_list, business_management, pages_manage_posts, pages_manage_engagement, pages_read_engagement, read_insights). This is the root cause of gitroomhq/postiz-app#1578, which reports this error for both Facebook Page and Instagram (Facebook Business). Users who follow the current docs can easily miss the "Other" option since the wizard hides it below the fold.

Testing

Tested against a local Postiz with three freshly created Meta apps, same Facebook account and environment, differing only in creation path:

1. "Other" -> Business: full success end to end - OAuth consent, channel connect, page selection, and a real publish to the page (Development mode, standard access only, no business portfolio).
2. Facebook Login use case: immediate "Invalid Scopes" on all six scopes, before any consent screen.
3. "Create an app without a use case", then adding the Facebook Login use case (the only OAuth route it offers): same "Invalid Scopes" failure.

Also verified the updated page and the new screenshot render correctly in a local Mintlify preview.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated Facebook app setup instructions to explain how to display all use cases.
  • Clarified that no use cases should be selected before choosing “Other” as the app type.

[postiz-agent]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1e4ebaaf-4d99-4eeb-b23f-e15e40746857

📥 Commits

Reviewing files that changed from the base of the PR and between 2d66e13 and edda7c9.

⛔ Files ignored due to path filters (1)

• images/providers/facebook/All-use-cases.png is excluded by !**/*.png

📒 Files selected for processing (1)

• self-host/providers/facebook.mdx

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The Facebook setup guide adds a step to display all app use cases. It clarifies that users must choose “Other” without selecting a use case first.

Changes

Facebook setup

Layer / File(s)	Summary
Clarify app-type selection self-host/providers/facebook.mdx	Adds instructions to show all app use cases and choose “Other” before selecting a use case.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to edda7

This change updates setup guidance and adds a verified screenshot without changing product behavior. No actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: egelhaus

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the update to guide users through Meta's app use-case wizard.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/facebook-use-cases-screen

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}