v2.6.0
Sub-accounts for resellers
- 5new
- 2improved
Resellers can now open one account per end customer, each with its own API key, bots, recordings, webhooks and calendar connections, while everything those customers spend is billed to the reseller. Reseller access is enabled on request — contact support if you want it on your account.
New Features
- Sub-accounts. Create, list, update, suspend and delete an account per end customer, rotate its API key, and read either one customer's usage or every customer's in a single call for invoicing. Each sub-account manages its own webhooks.
- A sub-account's data is its own: its bots, recordings and calendar connections are addressed only by its own key, and Meet, Teams and Zoom credentials never cross between a reseller and its customers or between two customers.
- Storage configuration resolves to the sub-account's own setting when it has one, falling back to the reseller's, so a customer who configures their own bucket actually gets it.
- Retention and artifact-access policy are read from the reseller at the point of use, so changing it applies to customers you already have.
- Daily bot caps and calendar limits apply across the whole reseller tree rather than per account, and suspending or deleting a reseller stops every account beneath it from spending.
Improvements
- Deleting a sub-account asks any bot currently in a meeting to leave, cancels its scheduled bots, revokes its calendar connections, removes its webhooks and disables its keys.
- A user arriving from an invitation joins the team they were invited to, instead of also being given a personal one.