Get partner access to a client's Facebook Page

Confirm the Facebook Page representing the business or location being managed. Ask the client to identify the account they actually use for the work in scope, rather than choosing from a familiar-looking name. Also agree whether the immediate objective is assessment, configuration or ongoing delivery. These details determine which permission is reasonable and what your team will check afterward. If the client is unsure which asset belongs to the project, resolve that ownership or account-selection question before they approve access to an unrelated account.

The request needs the person with full control of the intended Page. Send the instructions to that person or ask the client to involve them. A staff member who can read a dashboard may still lack permission to invite an agency. Repeating the same request with the same insufficient role will not fix that distinction. The authorized person should review the requested asset, recipient and permission before proceeding, and retain their own independent access after the agency is added.

Content and messages support publishing and community work; insights support review. Ads task access is distinct from ad-account access, and full control is not requested. Start by naming the actions the agency must carry out, then match the role to those actions. If the team only needs to inspect Facebook Pages, explain why a viewing role may be sufficient. If a later task requires more authority, make that a deliberate scope decision with the client. Avoid requesting the broadest available role simply to prevent a possible future question; the current engagement should explain the permission being requested.

The client selects the Page in Meta’s dialog and Agency Pilot assigns the agency portfolio as a partner with the chosen task access. Read the status in the context of that workflow. An invitation, a client confirmation and usable Facebook Pages access are related milestones, but they do not always happen at the same moment. Assign responsibility for the next step before marking delivery as ready. This prevents an agency teammate from arriving at a scheduled task and discovering that a required acceptance or platform action is still outstanding.

Use the agency Meta business portfolio, followed by its authorized team members. Verify it before creating or sending the onboarding request, especially when the agency works through more than one account. Ask the actual recipient to confirm the identity they will sign in with. A forwarded email or a similar display name is not reliable proof that the correct account has been added. For a staffing change, arrange the replacement person’s appropriate access and remove obsolete assignments through the relevant platform process.

After the platform action, open the shared Page through the intended agency portfolio and check its public identity before assigning the content or community team. Record who performed that check and whether any required work remains blocked. Prefer a harmless viewing check over an unnecessary live edit. If a teammate cannot reach the asset, compare the actual recipient and role with the original request before asking the client to start again. Completion should mean the right person can reach the intended asset with the agreed capability, rather than only that a message or notification was received.

The Page flow grants task access. It should not be confused with Meta Ads reporting or treated as an automatic connection to every asset associated with the brand. Keep the client’s reporting expectation explicit in the service brief. If a metric is needed for a report, identify its source, date range and definition before promising that it will appear. A successful access step establishes only the capabilities described for this particular integration. It should not be used as evidence that another platform, a separate dataset or an unrelated source of business results has also been connected.

If the Page is missing in Meta’s dialog, ask its full-control administrator to connect. If the Page was added to an existing onboarding request later, the client may need to reconnect and select it. Start with account identity and authority because those determine what the client can share. Write down the exact stage where the flow stopped rather than repeatedly recreating the same request. If Facebook Pages shows an account-specific restriction, the appropriate platform administrator may need to resolve it first. Avoid broadening permissions or switching to another asset just to make a completion indicator appear; verify the intended account instead.

The Page-sharing flow does not automatically grant the linked Instagram account. If the engagement includes Instagram work, the client should share the required Instagram asset through the appropriate Meta business settings. Record the two assets separately and verify each. That avoids discovering during a scheduled content task that the team can work on the Facebook Page but lacks the intended Instagram permission.

Yes. A Page-only engagement can request the Page without adding an ad-account request. Choose the task permissions that fit content, community or review responsibilities. If advertising work is added later, coordinate that account separately with the client. Keeping the initial request focused makes it easier for the business owner to understand which activities the agency is being enabled to perform.

If the client previously connected before the Page was part of the request, the new asset may need to be selected in Meta’s dialog. Explain which Page is now needed and why, then verify the resulting assignment. A prior Meta connection should not be taken as evidence that every subsequently requested asset has already been shared with the agency portfolio.

Agree the brand voice, escalation contact and boundaries for public replies. Clarify which questions the agency can answer independently and which require the business’s decision. Page message permissions enable access but do not provide those business instructions. For multi-location organizations, confirm the correct Page and local details before replying so a helpful response does not give a customer information for the wrong branch.

The source documents support for Pages outside a portfolio through the permission Meta requires for that situation. The connecting person still needs the appropriate Page authority. If the Page is not offered in the dialog, verify that person’s access rather than assuming it is missing because of the Page name. Review the final partner assignment on the exact intended Page.

Remove the agency partner from the Page and review the Meta business integration connection. Remove ad-account or Instagram permissions separately if they were also granted. Agree a handover point before removing access that is still needed to finish approved work. Confirm the business retains the people and permissions it needs after the agency leaves. Keep permission removal separate from decisions about delivered work or historical reporting data; those are different questions. Record which Facebook Pages assignments were removed and which, if any, remain for an explicitly agreed support period, with a clear owner for the final review.

Review the Page’s current business details and the content or community task approved by the client. Confirm how sensitive replies and time-sensitive updates will be escalated before responding publicly. If the project includes advertising or Instagram, verify those separate assets with their owners. The first useful result may be an approved content plan or a corrected business-detail draft; Page task access by itself does not supply the brand instructions needed to publish or reply on the business’s behalf.