Meta permissions and asset access

First, your PlugMind user needs access to the client workspace. Second, the Meta OAuth grant must include the permissions required for the action. Third, the signed-in Meta user needs access to the actual account, Page and related assets.

A connected account is not proof that every asset is usable. An ad account can be visible while its intended Page or Instagram identity is unavailable for promotion.

Run the account readiness workflow. It compares required and granted permissions and reports what is missing. Use the live result rather than relying only on scopes saved during an earlier connection.

If permissions have changed or expired, reconnect Meta from PlugMind using the appropriate login. Then rerun readiness and verify the intended account before preparing a fresh proposal.

List selectable Pages and available ad identities for the account. Choose an identity returned by the platform; do not invent IDs or assume a Page owned by another client can be used.

Lead-generation and conversion campaigns may need additional assets. Inspect only the assets required for the requested workflow. Personal lead answers are not needed for an account readiness check.

Successful permission checks do not guarantee that Meta will approve an ad or deliver impressions. Account restrictions, creative policy, billing and campaign settings can still affect the result.

Keep the exact Meta error code and message when a request fails. Resolve the cause, validate the updated proposal and obtain approval before retrying a write.