Operator and agency manual

For people who sell the platform to others: agencies (client workspaces under one login) and operators (a white-label platform with its own plans and customers). The platform owner section covers the installation itself.

1. The hierarchy

platform owner (the installation)
└── operator            sells plans to agencies and businesses, under its own brand
    ├── agency          manages client workspaces
    │   └── workspace   one client business
    └── workspace       a business that signed up directly

Branding is inherited downward; the closest level that sets a value wins. Each level sees inside the level below only through explicit access.

2. Agencies

Clients

Clients → New client creates a workspace, invites its owner by email and gives your agency admin access. The client list shows plan, members, live funnels, leads and visitors in the last 30 days, open incidents and pending approvals.

On a client page:

• Staff: assign agency members to the client with a role.
• Support access: open the client for a set time with a reason. The owner is notified and the access is logged.
• Roll out: copy a funnel to several clients at once.
• Duplicate: start a new client from an existing one: funnels, pipelines, templates, fields, scoring and workflows (as drafts), without contacts.
• Report: a client report of traffic, leads and orders.
• Export: the client's workspace package, for a move to another installation.
• Suspend / reactivate.
• Delete: schedules the client workspace for deletion (name and your password); the owner is emailed, and you or the owner can restore it during the grace period.

Approvals

Ask the client for approval from the client page. Only the client's owner can decide; agency and support members cannot approve on the client's behalf.

Plans and billing for your clients

Plans (agency): create plans for your clients with monthly or yearly prices, trials, limits (members, funnels, domains, contacts, emails, automation runs, AI spend, storage) and usage prices above the limits. Billing lists subscriptions and invoices. Invoices are created at the end of each period with the base price and usage lines, numbered per seller, printable. Mark them paid when the money arrives; overdue invoices set the subscription to past due.

Not built: collecting the money by card, tax lines on platform invoices, email reminders for overdue invoices.

Your brand

Settings → Branding at agency level applies to every client unless the client sets its own values. With the white-label flag on your plan you can set your own app domain, so clients sign in at your address.

Templates for clients

Templates saved in the agency are offered to all client workspaces.

3. Operators

Customers → New customer creates an agency or business, optionally with a plan and an owner invitation. The operator does not become a member of the customer; it sees inside only when the customer's owner invites it.

Plans: the operator's plans for agencies and businesses, with the same fields as agency plans plus flags (agency, white label, custom code, AI). Create the example plans fills five starting plans (Starter, Growth, Agency, Agency Pro, Enterprise) whose prices are meant to be changed.

Billing: subscriptions and invoices of all customers; CSV exports of customers, subscriptions and invoices.

Sign-up on the operator's app domain creates the new account under that operator.

4. Platform owner

Platform administrators see Platform in the sidebar.

Licenses

Licenses are signed with the private key on the owner's server (npm run license:keygen once; keep .license-keys/private.pem out of every repository and image). Issue license: type, edition, licensee, limits on workspaces and users, domains, version range, rights, validity and grace period. Revoked serials go into a signed revocation list that installations can fetch (LICENSE_REVOCATION_URL). See Licensing.

Sales website and demo

On the vendor's own installation, SALES_SITE=on serves the sales website at /. npm run demo:seed builds the read-only demo workspace opened from /demo; npm run demo:seed -- --reset rebuilds it (for example nightly). DEMO_ACCESS=off closes the demo entry.