Core Concepts

Core Concepts

Workspaces

A workspace (also called a cabinet) is the fundamental tenant boundary in Message Center. Every campaign, sender name, member, and audit record belongs to exactly one workspace.

Workspaces are independent:

• Members of Workspace A cannot see campaigns, sender names, or audit logs in Workspace B
• A user can be a member of multiple workspaces with different roles in each
• Billing, rate limits, and storage are managed per workspace

Special workspaces:

• Master — a read-only cross-workspace view available to super administrators. Useful for oversight without breaking tenant isolation.
• Archive — a view of archived campaigns across all workspaces a user belongs to.

Roles

Every workspace member has one of four roles:

Author Creates and manages campaigns. Can view sender names but cannot approve or create them. Campaigns created by an author enter the moderation queue and wait for approval.

Moderator Reviews pending campaigns and sender name revisions. Can approve or reject either. Cannot create campaigns or manage workspace membership.

Admin Full workspace control: creates campaigns, approves/rejects, manages members and roles, archives campaigns. Cannot create new workspaces (that requires super admin).

Super Admin Cross-workspace access. Manages workspaces, creates users, has visibility into all tenant data. Required for initial system setup.

Moderator flag An author can be granted a supplementary moderator flag that gives them approve/reject permissions in addition to authoring. This is useful in small teams where the same person creates and reviews campaigns.

Sender Names

A sender name is the alphanumeric identifier shown to SMS recipients as the message sender. In SMPP terms, this is the SADDR (source address).

Because sender names must be registered with carriers in most markets, Message Center manages them with a revision-and-approval workflow:

1. An author or admin creates a sender name
2. They submit a revision — the specific parameters (SADDR string, TON/NPI settings)
3. A moderator approves the revision
4. The approved revision becomes the active sender name, usable in campaigns

Every change creates a new revision. Approved revisions are immutable — you always know exactly which SADDR string was approved for any campaign.

Campaigns

A campaign is a batch SMS job with a list of recipient numbers and a message. Campaigns have:

• Mode — how delivery is timed (see below)
• Sender name — which approved SADDR to use
• Recipients — uploaded as a .txt or .csv file (one number per line)
• Delivery window — start/end times for scheduled and spread modes

Campaign modes:

Moderation Flow

Every campaign must be approved before it sends. There are no auto-start campaigns in Message Center by default.

The flow:

1. Author creates a campaign → status is New (pending moderation)
2. Campaign appears in the moderation queue visible to moderators and admins
3. Moderator reviews and either:
   • Approves → campaign moves to the SMS gateway queue (status: Building → Pending → Sending)
   • Rejects → campaign is cancelled; author sees the rejection reason
4. Author can optionally check "Start immediately on approval" to skip the manual start step

This flow applies identically to all campaign modes and sizes.

Audit Log

The audit log records every significant action: campaign lifecycle events, member changes, role assignments, sender name approvals, and administrative actions. It cannot be edited or deleted.

Each audit record captures: who, what, when, from where, and the before/after state of changed fields.

Retention period is configurable (default 90 days). Longer retention is available for compliance requirements.

Next Steps

• Getting Started — log in and navigate the interface
• Creating a Campaign — step-by-step campaign wizard guide
• Roles and Permissions — detailed permission matrix