Account and workspace setup
SFMC Connection Readiness for Salesforce Marketing Cloud teams.
How Campaign Builder prepares Salesforce Marketing Cloud account, credential, business-unit, and workspace context before agents or Factory workflows run.
What it supports
Concrete workflow support, not generic AI copy.
This use case is grounded in implemented Campaign Builder routes, agents, shared SFMC clients, and documented review boundaries.
Campaign Builder can store account-scoped SFMC server-to-server credentials after validating the token response and token context.
Web-app launch configuration can register an SFMC enterprise and business unit installation for workspace-aware app launches.
Business units can be mapped to Campaign Builder workspaces so agent and Factory workflows resolve the intended tenant and workspace context.
Account admins can review workspace mapping status before SFMC-facing execution paths are evaluated.
Implementation map
What technical evaluators can trace.
`POST /api/v1/settings/sfmc-connect` validates S2S clientId, clientSecret, and authUrl, calls `/v2/token`, reads `/platform/v1/tokenContext`, derives the REST URL, encrypts the client secret, and stores connectedAt metadata.
`POST /api/v1/settings/sfmc-connect` can upsert SFMC installation records with enterpriseId, businessUnitId, tenantId, REST/auth base URLs, credential source, and autoProvisionWorkspaces settings.
Workspace settings routes require account-admin access before listing workspaces, resolving mapping status, or connecting a workspace to an SFMC businessUnitId.
BU mapping helpers reject conflicts when the same SFMC business unit is already connected to another account or active workspace unless reassignment is explicitly allowed.
SFMC signed_request launch helpers extract enterprise ID, business unit ID, SFMC user identity, and signed launch context before applying tenant and workspace claims.
Review boundaries
Where Campaign Builder stops before launch risk.
Boundary
Connection readiness does not grant every agent or Factory tool; route-level entitlements still decide which workflows can run.
Boundary
Connected credentials remain server-side and encrypted at rest rather than exposed to browser workflows.
Boundary
Business-unit mapping prevents silent cross-account or cross-workspace reuse of an SFMC BU connection.
Boundary
Passing the connection checklist does not send campaigns, activate journeys, or approve SFMC production writes.
FAQ
Evaluation questions for SFMC Connection Readiness.
What does Campaign Builder verify when SFMC credentials are connected?
The settings route validates required S2S fields, requests an SFMC access token, reads token context for user/account details, derives the REST URL, encrypts the client secret, and stores connection metadata for the authenticated account.
How are SFMC business units tied to Campaign Builder workspaces?
Workspace settings routes connect a workspace to a businessUnitId after account-admin checks, then BU mapping helpers ensure the business unit is not already active for another account or workspace unless reassignment is allowed.
Does a connected SFMC account bypass review boundaries?
No. Connection readiness only establishes account, workspace, credential, and BU context. Agent entitlements, confirmed write paths, Factory prerequisites, and manual Journey activation boundaries still apply.
Next step
Review this workflow against your SFMC setup.
Bring one existing campaign, journey, email, Content Builder process, or Data Extension workflow to the demo so the evaluation can stay concrete.