Existing Page connections
Maintain connection metadata for Facebook Pages already authorized to the current deployment.
Meta integration
A controlled path to Meta authorization
Goodwin CRM separates already-authorized private-beta connections from future external onboarding. The interface explains who initiates access, where consent happens, and which steps remain gated.
Verification requiredConnection states
Two connection states, labeled separately
These states cannot be combined into a single availability claim. Existing private-deployment connections and future customer onboarding carry different evidence and release gates.
External Page selection
Allow an eligible customer to select a Facebook Page during a future controlled onboarding flow.
Approval-bound Page tools
Page reading, publishing, comments, locale, and Human Agent access stay locked until their separate Meta approvals and product validation are complete.
Illustrative authorization
Six visible steps from request to connection
A controlled onboarding path should explain each decision without suggesting that external Page selection is currently available.
This flow is illustrative. External customer onboarding has not been validated and remains gated by Meta verification and approval.
Consent boundaries
Authorization must remain understandable and revocable
An eligible user should see the requested access in Meta’s authorization surface and choose whether to continue. Goodwin CRM must not ask a user to send passwords, access tokens, credentials, or other secrets through its inquiry form.
Disconnecting an integration and requesting deletion are separate controls. The request route and verification process must remain aligned with the effective privacy notice and the service’s actual operations.
Pair authorization with data responsibility
The data-handling page explains limited use, access responsibilities, disconnection, and deletion-request boundaries.