Facebook Page Authorization SOP
Purpose
Obtain durable, password-free management access to a client's Facebook Page so SC can post, respond to messages, run ads, and connect the Page (and any linked Instagram account) to the client's platform sub-account.
Trigger
A client engagement requires SC to manage the client's Facebook presence, and SC does not yet hold access to the Page through Meta Business Manager.
Operator role
Account Manager (drives the process, client communication). Steps inside SC's Business Manager require a person with admin access to SC's Meta portfolios — see Meta Business Portfolio Overview for who manages them and the portfolio IDs. Never hard-code portfolio IDs into tickets or client emails from memory; copy them from that doc.
Output
The client's Page is shared to SC's Business Manager with management-level (non-ownership) permissions, SC operators have task-level access, and the Page is connected inside the client's platform sub-account. The client retains full ownership and can revoke at any time.
Principles (non-negotiable)
- No passwords. Facebook Page access never involves exchanging the client's personal login. If a client offers credentials, redirect to this process. (Contrast: Instagram currently has no partner-access equivalent for direct login integrations; IG credential handling follows the client-self-service-access working rule — out of scope here.)
- Business Manager access only. All Page access flows through SC's verified Business Manager portfolio (see the portfolio overview doc for the current ID). The unverified portfolio is not used for client access.
- No email-based "add this address as admin" requests. Meta authorization is BM-to-Page/BM-to-BM, not email-based. (
setup@symphonycore.comis the Google Business Profile convention only — do not quote it for Facebook.) - Isolation. Client Pages connect only in the client's own sub-account, never in the SC agency sub-account. The connecting identity's Page roles drive what GHL's picker shows — see Meta / Facebook Integration & Account-Isolation Standard.
1. Choose the path
| Client situation | Path |
|---|---|
| Page is managed from a personal profile; client has no Business Manager (most small businesses) | Path A — SC-initiated Page access request |
| Client has their own Meta Business Manager containing the Page | Path B — client adds SC as Partner |
| Neither works (e.g., approval notifications unreachable) | Path C — direct admin invite (fallback only) |
If unsure which situation applies, run the detection procedure in §1.5 before committing to a path.
1.5 Determine the current management setup
Whether a Page sits inside a Meta Business Portfolio (Business Manager) is not determinable from the outside. Page Transparency renders only for logged-in viewers, and anonymous fetches of facebook.com return empty shells — do not spend cycles on web checks or scrapers; they cannot answer this. Use these three steps, cheapest first:
- Logged-in Page Transparency check (any SC operator's own account): open the Page > About > Page transparency. If it lists a confirmed Page owner or "Organizations that manage this Page", a portfolio exists — note the organization name. Absence is inconclusive (only verified portfolios surface here).
- Ask the Page admin: "When you manage the Page, do you go through business.facebook.com / Meta Business Suite with a business portfolio, or do you manage it directly from your personal Facebook account?" Small businesses often don't know the distinction — treat an uncertain answer as unresolved, not as "no portfolio".
- Definitive check, with the admin, on a screen-share: logged in as the admin, open Business Suite > Settings > Business Assets (or business.facebook.com > Settings > Accounts > Pages). If the Page is listed under a portfolio, identify whose portfolio it is — the client's, a former owner's, or a former vendor's. That answer picks the path:
| Detection result | Consequence |
|---|---|
| No portfolio; personal-profile administration only | Path A. Consider a client-owned portfolio (§4.5) if the admin is not the current business owner. |
| Portfolio owned by the client | Path B. |
| Portfolio owned by a third party (former owner, ex-vendor) | That portfolio's admin must release the Page or approve access — see §7 troubleshooting. Do not proceed on Path A assumptions. |
Record the detection result (date, method, answer) in the client's digest before sending any access request.
2. Path A — SC-initiated Page access request
Use when the Page is owned/administered from a personal profile (the admin may be the owner, a family member, or a predecessor — identify who actually holds the admin role first; that person approves).
SC side (BM admin):
- Go to business.facebook.com and select the verified SC portfolio.
- Open Business Settings (gear icon) > Accounts > Pages.
- Click Add > Request access to a Facebook Page.
- Enter the Page URL or name (confirm you have the exact Page with the client first — check the vanity URL).
- Select the permissions to request: content/posts, messages, community activity (comments), insights. Do not request full control/ownership — the client keeps that.
- Submit. The request shows as pending under Business Settings > Pages.
Client side (Page admin): the request appears as a notification on the Page and under the Page's settings (Page access / partner requests). The admin reviews and clicks Approve. Prep them before you send it:
- Tell them (or the person forwarding to them) to expect a request "from Symphony Core" and what it asks for.
- Share the client-facing KB article as the explainer:
https://help.symphonycore.com/client-essentials/grant-meta-business-manager-access(verify the URL loads before sending — per the customer-KB working rule). - Requests expire if unanswered (typically after some days); if it lapses, cancel the pending request and resend.
3. Path B — client adds SC as Partner
Use when the client operates their own Business Manager.
- Send the client the KB article above plus SC's Business Manager ID (from the portfolio overview doc).
- Client: Business Settings > Partners (under Users) > Add > "Give a partner access to your assets" > enters SC's BM ID > selects the Page (plus ad account / WhatsApp if in scope) and the access level per asset (management level, not full control).
- SC side: the incoming partner grant appears in SC's Business Settings; accept it. The Page then lists under Pages with "Partner" provenance.
4. Path C — direct admin invite (fallback, discouraged)
The Page admin invites a specific SC-controlled Facebook identity to a Page role from the Page's own settings. Only use when Paths A/B fail (e.g., BM UI issues on the client side). Drawbacks: ties access to an individual identity instead of the SC portfolio, pollutes that identity's GHL picker (isolation standard), and complicates offboarding. If used, migrate to BM-based access at the first opportunity and record the exception in the client's digest.
4.5 Client business portfolio — when and how to create one
A client-owned Meta Business Portfolio is recommended, not required. Path A works fine without one. Create one when:
- The Page is administered only from the personal profile of someone other than the current business owner (prior owner, ex-employee, family member, old vendor) — a portfolio owned by the current owner is the durable fix for the ownership posture, independent of SC's access.
- The client plans to run ads at scale, needs multiple staff with roles, or wants a clean container for an eventual ownership handover.
Rules:
- The client's own Facebook account creates the portfolio. SC never creates it — a portfolio created under an SC identity or inside SC's BM is SC-owned, which violates the same no-ownership principle as the rest of this SOP. SC's role is a guided screen-share, nothing more.
- Inputs the client should have ready: legal business name, a business email address, business address.
Steps (client drives, SC guides):
- Client logs in to Facebook with their personal account and goes to business.facebook.com > Create a business portfolio; enters business name, their name, business email.
- In the new portfolio: Settings > Accounts > Pages > Add > "Add a Page" > enters the Page. If the client's profile is already a Page admin, the add is immediate; otherwise the current Page admin receives and approves the request.
- Once the Page sits in the client's portfolio, SC access proceeds as Path B (client adds SC as Partner).
The portfolio is free and changes nothing about the public Page. Send the client the business-accounts KB article for the client-facing walkthrough.
5. Post-authorization
- Task-level access: in SC's Business Settings > Pages > select the Page > assign the SC operators who need it (management tasks only). Operators access the Page via Meta Business Suite thereafter.
- Verify: the Page appears under SC's BM; open it in Business Suite; confirm you can view content and the inbox.
- Connect in the client's sub-account: in the client's platform sub-account (never the agency account): Launchpad > Facebook Connect (or Marketing > Social Planner > Add Socials > Facebook). Authenticate with a connecting identity that has a role on this client's Page per the isolation standard; select only this client's Page in the picker.
- Linked Instagram: if the client's Instagram Business account is linked to the Page, add it via the Facebook-linked option in Social Planner at the same time (this supersedes a direct-login IG integration once available).
- Record: note the grant (date, path used, permissions) in the client's meeting-facts digest or technical-access doc, and close the tracking ticket with a screenshot of the Page under SC's BM as evidence.
6. Verification checklist
- Page listed in SC Business Settings > Pages (partner/requested provenance, not ownership)
- SC operators have task access; test open in Business Suite
- Page connected in the client sub-account; conversations/posting available in the platform
- No client Page visible in the SC agency sub-account picker
- Client confirmed they retain admin/ownership and know how to revoke
- Grant recorded in client docs; ticket closed with evidence
7. Troubleshooting
| Symptom | Fix |
|---|---|
| Client can't find the approval notification | Approve from the Page directly: Page profile > Settings > Page setup / Page access > pending partner requests. Screen-share on a call if needed. |
| Request expired before approval | Cancel the pending request in SC Business Settings and resend; coordinate a same-day approval window with the client. |
| Page admin is a former owner/employee | The current admin must approve or transfer the admin role first. If truly unreachable, the client pursues Meta's Page ownership recovery (business.facebook.com help); do not work around it with shared logins. |
| Page is owned by a third party's portfolio (former owner's or ex-vendor's BM) | The Page UI cannot fix this — that portfolio's admin must either approve the partner/access request or remove the Page from their portfolio so the client can claim it (§4.5). If the portfolio admin is unreachable or refuses, the client pursues Meta's ownership-dispute/support path with business documents; never work around it with shared logins. |
| Duplicate or auto-generated place Page exists (common after a relocation or rename) | Auto-generated Pages rarely appear in external search engines — check with a logged-in Facebook place search for the business name variants and former addresses. If found, claim it via "Is this your business?" from the official Page's admin, then merge (Page settings > merge Pages; both must be in the same portfolio/admin). Do this before running ads so check-ins and reviews consolidate. |
| 2FA blocks a client-side step | The code goes to the Page admin's device/email; schedule the approval when they can relay it live (client call or WhatsApp). SC never stores client 2FA seeds. |
| Client is in professional mode / has no Page | A Page must exist first — send the business-accounts KB article (help.symphonycore.com/client-essentials/..., see the customer-education folder) and create the Page before authorization. |
| GHL picker shows other clients' Pages | Connecting identity holds too many Page roles — stop and fix per the isolation standard. |
8. Revocation and offboarding
- Client-initiated: the client removes SC under their Page settings (Page access / partners) or, in BM, under Partners. Access ends immediately.
- SC-initiated (disengagement): remove operator task access, remove the Page from SC's BM, and disconnect the Page from the client's sub-account if SC is relinquishing platform management. Record the removal date in the client docs.
Related documents
- Meta Business Portfolio Overview — SC portfolio IDs, verification status, who manages them
- Meta / Facebook Integration & Account-Isolation Standard — connecting identity + picker isolation rules
- Customer KB: Grant Meta Business Manager Access (client-facing companion for Path B / general explainer)
- Customer education:
07-customer-education/fundamentals/setting-up-facebook-instagram-business-accounts.md(clients without a Page / with personal-profile setups)
Document History
| Date | Version | Change | Author |
|---|---|---|---|
| 2026-08-06 | 1.0 | Initial SOP — three authorization paths, post-auth platform connection, isolation guardrails, troubleshooting, revocation. Prompted by a live engagement where an email-based "add as admin" ask (the GBP convention) was quoted for Facebook. | Symphony Core Systems Team |
| 2026-08-10 | 1.1 | Added §1.5 detection procedure (portfolio status is not externally determinable — Transparency check, admin question, screen-share asset check) and §4.5 client-owned portfolio creation (client creates, SC guides; never SC-created). New troubleshooting rows: third-party-portfolio-owned Page, duplicate/auto-generated place Pages. | Symphony Core Systems Team |