Client onboarding links with access you can verify

Collect the client's business name, the services in scope, the platforms involved and the agency identities that need access. Also identify someone with permission to share each asset. This keeps the request specific and helps the client understand why a particular account or role is being requested.

Not necessarily. An audit usually needs the ability to inspect information, while management may require changes. Choose roles based on the actual tasks agreed with the client. If the engagement expands later, review the access deliberately rather than requesting the broadest permissions at the start.

Inspect the individual grantee results to identify who received access and who failed. The grant runner keeps those outcomes and supports retrying the missing grant. A successful user does not establish that every teammate has permission. Confirm the intended property and each required agency identity before relying on the connection for delivery.

Plan onboarding as a set of platform-specific steps rather than a single event everyone must finish together. Review the link's current progress and follow up on the outstanding items. For guided steps, confirm the actual invitation or access in the platform after the client indicates completion.

Stop and confirm the correct business property before relying on its data. Similar names can make selection confusing, so compare the site's identity and account details with the client. Reporting from the wrong property can produce plausible numbers that have nothing to do with the engagement.

Explain that the business ID identifies the agency business portfolio that will receive partner access. The client should select the intended assets and review the permissions in Meta's own flow. Keep the explanation practical: which business is receiving access, to what asset, and for what agreed work.

Treat it as a signal to verify access. The client may have sent an invitation that still needs acceptance, selected a different identity or chosen a role that cannot perform the task. Open the platform using the intended agency account before marking the operational dependency resolved.

An access request cannot settle who controls a business asset. If the client lacks the required authority, they need to resolve that through the platform and the existing owner or administrator. Document the dependency and adjust the kickoff plan rather than repeatedly requesting access from an unauthorized person.

Specify the website, the invitation method, the agency email and the permissions required for the agreed work. Include clear instructions for the website system the client uses. Avoid requesting passwords in free-text answers; an invitation or collaborator account gives the access a clearer identity and removal path.

A reusable link is suitable when the person completing it needs to provide business details and create the client record as part of the flow. A client link belongs to an existing client. Choose the type that fits the handoff, and review limits and expiry before distributing it widely.

Use an expiry when the request has a defined completion window, such as a prospect review or a scheduled onboarding round. Tell the recipient the deadline in plain language. Without an expiry, maintain a routine for reviewing active links and revoking requests that are no longer needed.

First establish which assets the client owns and what each agency is responsible for. Request only the access needed for your scope, using the client's authorized process. Avoid assuming the other agency's login should be shared or that their removal is necessary for your work to begin.

Your team can open the intended assets with the intended identities, perform the agreed tasks, and see the expected reporting sources. The client knows what was shared and what happens next. Any outstanding exceptions have a named owner instead of being hidden inside a completed kickoff meeting.

List the agency users and partner relationships granted in each platform, along with reporting connections and active onboarding links. Coordinate removal through the platform owners. Revoking a link or disconnecting reporting should not be treated as proof that every separately granted platform permission has been removed.

Send one clear request with the scope, intended recipient and explanation of each platform step. Review progress before following up, then ask only about the unresolved dependency. A targeted message about a missing property invitation is easier to act on than a generic request to complete onboarding again.