Admin Hub — Help

What this hub does

A registry of deployed client Workers. One row = one {client}.portaluse.com Cloudflare Worker with its own D1 database. The hub does not dispatch calls — it stores credentials and a clickable link to each client's console.

Adding a new client gate

1. Copy clients/cyberbacker/dispatch-manager/ to clients/<new-client>/dispatch-manager/.
2. Edit wrangler.toml: change name and routes.pattern to <sub>.portaluse.com.
3. npx wrangler d1 create <name>-db, paste the database_id into wrangler.toml.
4. npx wrangler d1 execute <name>-db --remote --file=schema.sql.
5. Set secrets: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, optionally SETUP_TOKEN, RESEND_API_KEY.
6. npx wrangler deploy.
7. Add https://<sub>.portaluse.com/api/auth/google/callback as an authorized redirect URI in the GCP OAuth client.
8. Click + New Gate here and fill in the fields. The Client Worker stores its own credentials separately — the keys saved here are for your reference only.
9. Visit the gate URL and create the first admin account (password or Google OAuth).

Auth

Password + Google OAuth. Google sign-in only works for emails that already have an admins row (bootstrapped via password-first signup or direct D1 insert). Sessions are 7 days, HttpOnly, SameSite=Strict.

What is NOT in this hub

• Call placement. Happens inside each client Worker.
• Contact data. Each client Worker stores its own contacts in its own D1.
• Bland API keys of record. The client Worker reads them from its own D1 config table (or Cloudflare secrets).
• Authoritative pathway IDs. Each campaign in a client Worker stores its own pathway_id.

Deleting a gate

The Delete button only removes the row from this registry. To fully decommission a client, also:

• npx wrangler delete inside the client directory.
• npx wrangler d1 delete <name>-db to drop the database.
• Remove the redirect URI from GCP OAuth client.