TSG GLOBAL/Developers
Campaign Manager Sandbox

Staff superadmin keys

Configure named staff access, explicit grants, and the correct company target for each business operation.

Sandbox environment

Brand and campaign submissions are simulated. Nothing reaches The Campaign Registry and no carrier charges are incurred. Use credentials issued for this environment.

Issue a staff grant

An ordinary admin key issued under TSG still only accesses TSG's company records. To review another company's campaigns, a superadmin issues a staff superadmin key from the company-detail API-key section. The key has a named active superadmin owner, an expiry, explicit permissions, and either an allowed company list or an explicit all-companies grant. The secret is shown once; store it in a secret manager. Revocation, staff deactivation, demotion or expiry stops access.

Select a company and act within scope

  1. Grant companies:read, brands:read, campaigns:read, campaigns:review and campaigns:submit for a review-and-submit integration. Reconciliation and deactivation require their own separate permissions.
  2. Call GET /companies without a company header. Choose the correct company from the returned opaque references.
  3. Send X-Company-Ref: <company-ref> on every business request. The same header is required for MCP tool calls; it is not a tool argument. If your MCP client fixes headers per connection, configure one connection per company or update its headers when switching targets. Company-bound partner and admin keys must omit it.
  4. Read the campaign and verify its content. POST /campaigns/{ref}/approve requires both campaigns:review and campaigns:submit because approval also attempts upstream submission.
  5. Inspect the result: submitted_to_tcr=true means sent upstream, not carrier-approved. Otherwise inspect tnid_error and campaign status. Mutations are audited with the staff owner, key, target company and outcome.

Separate review and submission authority

Use a separate key with only review permissions when its holder must not send anything upstream. For 10DLC, that key can return a campaign for revision but cannot call the combined approve-and-submit action. POST /campaigns/{ref}/resubmit rewrites disclosures in the campaign content before sending it upstream, so staff keys need both campaigns:write and campaigns:submit. A review-and-submit key without write permission cannot use that combined action. Staff-created legacy records still use the key owner's user account; agree on customer ownership before granting legacy creation permissions.

Staff campaign reads preserve the saved content, including when the key also has write permission. Existing company partner/admin reads retain their platform-default normalization for editable drafts.

Operator rollback requirement: revoke or disable every staff superadmin key before rolling back to code that predates staff-key support. Earlier authentication code does not understand the new access level or keys without a company binding. Preserve the audit history; the staff-key migration intentionally refuses an automatic downgrade.