Setup and administration areas — numbers, people, roles and billing

Who this guide is for: customer ADMINISTRATORS (the business owner-administrator who manages numbers, teammates, roles and billing). Regular members are refused the admin actions described here.

ConvoTide groups its setup and administration screens into destination areas — the migration assistant's "destination" links (see the migration readiness guide) open these same areas. This guide covers the four areas the recorded evidence exercised: WhatsApp Account (your numbers), User Management (seats and invites), Role Management (custom roles) and the Billing Hub.

About the evidence. Every seat, invite, number, role and wallet row in the run behind this guide was seeded by the test. No live Meta number was bound, no real invite email left the machine, and no live payment or wallet movement occurred.

WhatsApp Account — the numbers bound to your business

This screen lists the WhatsApp/Meta numbers bound to your business, each with its display label. The list shows only your business's numbers (another business sees none of them), and a regular member can read it — this area is member-readable by design. What a number counts against your plan's allocation is the plan guide's subject.

User Management — seats, invites, acceptance and deactivation

The full invite life, as exercised over the real routes:

A member seat is refused these admin actions (scope denial). The on-screen version of issuing and revoking an invite — including the one-time invite code with its never-shown-again warning — is the seat invite/revoke guide's evidence; this guide adds the accept and deactivate steps, which that browser journey did not exercise.

Role Management — custom roles

Custom roles are full objects with their own life cycle: create, read, update, delete. Three honest refusals protect them:

Assigning a role is an either/or switch. Assigning a custom role to a teammate replaces their standard permission bundle — it is not added on top — and clearing the assignment returns them to the standard bundle. If a teammate "lost" a routine permission right after gaining a role, this switch is why: the role's permissions are now their whole set.

What you see What it means What to do
409 ROLE_IN_USE on delete The role is still assigned to a seat Unassign it from that seat first
A teammate missing routine permissions after a role assignment The custom role replaced their standard bundle (either/or) Add the needed permissions to the role, or clear the assignment
Member refused on seats/roles/billing actions These are administrator actions Sign in with an admin seat

Billing Hub — plan, catalog and the wallet statement

The Billing Hub answers four money questions:

  1. Plan and quota — what the business is on, and its allowances.
  2. The sellable catalog — what can be bought.
  3. The wallet statement — the row-by-row statement of the business's wallet.
  4. Reconcile truth — the statement reconciles against its underlying records rather than asserting a balance that cannot be checked.

Every one of these is admin-gated (the billing-manage permission is admin-only; a member seat is refused). No live payment occurred anywhere in the run; the wallet rows were seeded test truth.

What this guide does NOT claim (kept honest)


Evidence record (kept for honesty). The FULL3747-O14EV lane executed suite o14-ev3747-s4-campaigns-tpl-dest.pg.test.mjs — 24/24 cases passed — on the combined candidate checkout (C:/CT-ZC-FULL3747, branch codex/zcode-full3747), real compiled application over real loopback HTTP against a throwaway PostgreSQL 16 cluster. Verbatim case receipt: C:/CT-ZC-FULL3747/tools/zcode-integration3723/runtime/evidence/o14ev-s4/O14EV-S4-CAMPAIGNS-TPL-DEST-CASES.json (suite S4-campaigns-tpl-dest, started 2026-10-25T00:42:42.256Z); destination cases cover matrix rows O13.01–O13.06. Standing: local-candidate, test-harness evidence; Chief acceptance and publication OPEN; no live or Main-built runtime claimed. The browser-side seats journey is separately documented in the seat invite/revoke guide; the read-only plan screens are the plan entitlements guide.