Platform & Operators
By Conversa Labs
By Conversa Labs
Super Admin (accounts, plans, license), installer/deploy, tenancy and operator topics. Operator-level content.
Platform operators overview
Overview This category is for platform operators — those who administer the installation as a whole, not just a single account. It covers Super Admin topics (accounts, plans, license), installation and deploy, tenancy and provisioning of auxiliary services. Prerequisites - Super Admin access to the installation. - Infrastructure access (server/cluster) for install and deploy tasks. Step by step 1. Open the Super Admin panel to manage accounts, plans and license. 2. Use the install/deploy articles to provision or update the platform. 3. Configure tenancy and auxiliary services (for example, the WhatsApp Web gateway). 4. Monitor installation health and license validity. Settings & options - Accounts and plans: creation, limits and per-account features. - License: activation and the installation's license state. - Infrastructure: images, environment variables and services. Use cases - Operate an installation serving multiple accounts. - Provision new instances and keep updates current. Tips, limits & best practices - Restrict Super Admin access to the minimum necessary. - Keep backups and a rollback plan before every deploy. Troubleshooting - I don't see Super Admin: confirm your user has the installation operator role. - Feature unavailable: check plan/license and environment variables. See also - Super Admin: accounts, plans and license - Installer and deploy
Super Admin: accounts, plans and license
Overview The Super Admin panel is where the operator manages the entire installation: create and manage accounts, define plans and features, and track the license state. Prerequisites - A user with the Super Admin role. - A valid license for the installation. Step by step 1. Open the Super Admin panel. 2. Under Accounts, create or edit accounts and adjust limits and features. 3. Under Plans, define the available plans and what each one enables. 4. Under License, check the activation state and validity. Settings & options - Per-account features: enable/disable modules per account. - Limits: agents, inboxes and other per-plan limits. - License: key, state and renewal. Use cases - Provision a new account for a customer. - Adjust an account's plan based on the contract. Tips, limits & best practices - Document each account's plan and features. - Monitor license validity to avoid interruptions. Troubleshooting - Account missing a module: check the features enabled on the plan/account. - Invalid license: verify the key and activation state. See also - Platform operators overview - Installer and deploy
Installer and deploy
Overview The operator provisions and maintains the platform through an automated installer and a deploy process based on versioned images. The goal is to bring up and update the installation predictably, with rollback on hand. Prerequisites - Infrastructure access (single server or cluster). - Image registry credentials and the domain's DNS/TLS. Step by step 1. Provision the infrastructure (single server or cluster) with the installer. 2. Configure domains, DNS and TLS certificates. 3. Deploy the platform's versioned image. 4. Run database migrations and verify service health. 5. For updates, deploy the new version with a gradual rollout strategy. Settings & options - Environment variables: installation secrets and parameters. - Versioned images: pin the version to deploy (avoid generic tags in production). - Migrations: run migrations as a controlled deploy step. Use cases - Stand up a new installation from scratch. - Update to a new version with rollback available. Tips, limits & best practices - Always have the rollback command written down before starting a deploy. - Update one service at a time and verify health before proceeding. - Never expose secrets in versioned files. Troubleshooting - Service won't start: check environment variables and service logs. - Migration failed: check database connectivity and run the migration in isolation. See also - Super Admin: accounts, plans and license - Tenancy and ZuckZapGo
Tenancy and ZuckZapGo
Overview The operator defines how accounts share (or don't) auxiliary services. A central example is the WhatsApp Web gateway (ZuckZapGo), which hosts the paired sessions used by WhatsApp Web inboxes. Prerequisites - A provisioned gateway service reachable by the platform. - The gateway admin token (kept backend-only, never exposed). Step by step 1. Define the tenancy model: a single gateway shared by the operator, or a gateway per account. 2. Configure the gateway URL and admin token in the installation. 3. When a WhatsApp Web inbox is created, the platform auto-provisions a user on the gateway. 4. Monitor session state (connected, pairing, disconnected). Settings & options - Tenancy mode: shared (operator) or per-account. - Credentials: admin token and gateway URL (encrypted/secured). - Webhooks: the gateway notifies the platform about session and message events. Use cases - Operate a single gateway for all accounts (self-hosted). - Let each account point to its own external gateway. Tips, limits & best practices - Never expose the gateway admin token in API responses or logs. - Monitor gateway health and the validity of paired sessions. Troubleshooting - Inbox won't pair: check connectivity to the gateway and the token. - Session drops often: check device/source stability and the webhooks. See also - Connect WhatsApp Web (QR pairing) - Installer and deploy