Skip to content

Admin Guides

Workspaces & roles

Your organization can hold multiple workspaces (e.g. one per brand). Roles: owner (everything), admin (manage workspaces), member (create content), client_viewer (read-only, for client approval workflows - Phase 2).

Your plan sets how many workspaces you can have active at once (Starter 1, Pro 1, Business 3, Agency unlimited). Owners and admins create a new workspace from the New workspace control in the workspace switcher. If you reach your plan's limit, upgrade to add more.

Downgrading and archived workspaces

If you switch to a plan with a lower workspace limit, we never delete anything: your extra workspaces are archived (newest first), and your primary workspace always stays active. Archived workspaces simply disappear from the switcher. After you upgrade again, open the Billing page and use the Archived workspaces card to restore any you want back - restoring is blocked only if you're already at your new plan's limit.

Billing states

Accounts move through: trial -> active -> past-due (grace period with warning banner) -> suspended (login allowed, only the billing page works) -> reactivated instantly on payment.

Platform staff tools

These tools are only visible to CampaignHQ platform staff (not customer accounts), under Admin. Each customer's detail page lets staff:

  • Toggle feature flags per organization (e.g. AI funnel builder, public API, SMS marketing, white-label reports) - useful for enabling a capability for a single account.
  • Grant or revoke staff access for any member of that organization. You can't remove your own staff access.

The Admin home also shows a System health panel: live job-queue counts and the most recent webhook delivery failures, so staff can spot stuck queues or billing webhook problems at a glance.

Staff can also View as customer from a customer's detail page — a read-only window (2 hours) onto that account to see exactly what the customer sees while troubleshooting. Nothing can be changed in this mode (a clear banner stays on screen, and the server blocks every edit), and account secrets such as API keys are never revealed.

Every staff action is recorded in the organization's audit log.

API keys & security

  • Social logins and AI keys are encrypted at rest and never displayed after entry.
  • Sessions use secure httpOnly cookies; logging out invalidates the session server-side.