Use Case — Content Providers

Use Case — Content Providers

Content providers — subscription services, media companies, mobile VAS platforms, digital service aggregators — frequently need to send SMS on behalf of multiple clients or brands from a single technical infrastructure. Message Center's workspace model is purpose-built for exactly this: one installation, many isolated tenants, each with their own team, sender names, and audit trail.

The Challenge

Content providers operating on behalf of multiple clients face structural problems that single-tenant SMS tools cannot solve:

• Brand isolation — Client A must not be able to see Client B's campaigns, recipient lists, or delivery reports
• Independent sender names — each client has their own carrier-registered SADDR; cross-contamination is a regulatory risk
• Separate billing evidence — each client needs their own usage report for invoicing
• Per-client team access — Client A's marketing team should log in and see only Client A's data
• Centralized oversight — the content provider's operations team needs visibility across all clients for support and compliance
• Compliance per client — some clients have stricter moderation requirements than others

How Message Center Handles It

One Workspace Per Client

Each client gets a dedicated workspace:

Client A workspace    → Client A team, Client A sender names, Client A campaigns
Client B workspace    → Client B team, Client B sender names, Client B campaigns
Client C workspace    → Client C team, Client C sender names, Client C campaigns
Platform workspace    → Internal testing, content provider's own sends

Workspace slugs can be named after the client (acme-corp, beta-media) or given internal codes. Members of one workspace cannot see any data from another workspace — this isolation is enforced at every API call, not just in the navigation UI.

Billing Evidence Per Workspace

Every campaign in a workspace generates a complete audit record:

• Campaign created (with creator attribution)
• Moderation approval (with approver attribution)
• Recipient file uploaded (with file size and line count)
• Delivery status per recipient (available via Recipients API)

The campaign detail's Export tab provides delivery reports as downloadable files. The Audit tab provides the full action history. Together, these give content providers the evidence needed for per-client billing reconciliation without manual tracking.

The workspace_total field in the campaigns API response gives the total count of campaigns in the workspace — useful for usage metering.

Moderation Per Client

Some clients require strict content review; others have pre-approved message templates they trust implicitly. Message Center supports both patterns within the same installation:

• Clients with dedicated compliance teams can have their own moderator role holders
• Clients without moderation staff can delegate the moderator role to the content provider's own review team
• Content provider staff can be admins in multiple client workspaces simultaneously (each membership is independent)

Super Admin Cross-Workspace View

Content provider operators — support staff, account managers, platform admins — can be assigned the super admin role. Super admins have read visibility across all workspaces:

• View any workspace's campaigns and delivery status without joining the workspace as a member
• Run backfill or diagnostic scripts that span all workspaces
• Assist a client whose moderator is unavailable by promoting a temporary reviewer

Super admins cannot be mistaken for client-workspace members — the cross-workspace view (/w/master) is a distinct scope.

Client Onboarding Flow

Content provider operations team
        │
        ▼
1. Create workspace (admin panel) → workspace slug = client identifier
2. Create workspace admin account for client's technical contact
3. Create approved sender name revision for client's SADDR
4. Client's team invites their own authors and moderators
5. Client team starts creating campaigns
        │
        ▼
Ongoing
6. Client team creates and approves campaigns independently
7. Content provider reviews usage via master workspace or audit API
8. Monthly billing: pull exports + audit records per workspace

Isolation Guarantees

Message Center enforces workspace isolation at three independent layers:

1. MongoDB query layer — every DAO query includes workspace_id as a mandatory filter; cross-workspace queries are only possible for super admins via explicit synthetic scope
2. BFF API layer — getWorkspaceContext() throws notFound() if the authenticated user is not a member of the requested workspace (super admin exception applies)
3. URL layer — workspace slug is part of every URL (/w/[workspaceSlug]/campaigns); navigating to a workspace you don't belong to returns 404

There is no configuration toggle that weakens this isolation — it is architectural, not a policy setting.

Summary

Next Steps

• Core Concepts — workspace model explained
• Settings and Members — onboarding client teams
• Roles and Permissions — role assignments and the is_moderator flag