Skip to main content
Feature Administration lets you control which product features are available to the accounts beneath you — partners, resellers, and organizations — from a single matrix. A gate set high in the hierarchy is inherited by everything below it, so you can turn a capability off for an entire reseller (and all of its organizations and agents) with one click.
Feature Administration is rolled out gradually. If you don’t see it, it has not yet been enabled for your account. Enabling and disabling the feature globally is controlled by Telzino.

​
The hierarchy

Availability resolves top‑down through four levels:
1

Super Admin

Telzino. Can gate any feature for any partner.
2

Partner

Your account. Gates features for the resellers and organizations you own.
3

Reseller

A group of organizations. Inherits partner gates; can be gated individually.
4

Organization

The tenant an agent belongs to. Inherits every gate above it.
A feature is available to an organization only if it is not locked at that organization or at any level above it. The most senior lock in the chain wins, and lower levels cannot re‑enable something an ancestor has locked.

​
Categories

The matrix groups features into rows by category:

​
Reading the matrix

Each column is one of your children (a reseller, or — when you drill in — an organization). Each cell shows that feature’s effective state for that child:
  • Available — usable by the child and its agents.
  • Locked here — you locked it directly on this child. Click to unlock.
  • Locked upstream — inherited from an ancestor lock. Read‑only at this level; change it where it was set.
Click a child’s name to drill into its organizations.

​
Locking and unlocking

  • Click a cell to toggle a single feature for a single child.
  • Lock all / Allow all at the top of a child’s column applies to every feature for that child at once.
  • Lock all children / Allow all children on a feature row applies that feature across every child in the current view.
“Allow all” only removes locks you set at the current level. Locks inherited from an ancestor (shown as Locked upstream) are not affected — unlock those at the level where they were created.

​
How gates take effect

Gates are enforced consistently across every surface:
  • Agent configuration — In the Dashboard and in Connect, a locked integration or capability is hidden or disabled when configuring an agent, for the agent’s own organization. This includes gates inherited from a parent reseller or partner, not just the account.
  • API — Requests that enable a locked feature are rejected with 403 forbidden, so a gate cannot be bypassed programmatically. This covers integrations, Knowledge Base (ragEnabled, and the /v1/knowledge-bases endpoints), Warm Transfer, Custom Voices (POST /v1/custom-voices and assigning a clone to an agent), Business Listing (googlePlaceId and GET /v1/places/search), Card Payments (Stripe onboarding and enabling the agent payment tool), and SMS Messaging (adding the Send SMS or Check SMS Replies tool to an agent).
Because availability is resolved for each agent’s own organization, a lock placed on a reseller correctly hides the feature for every organization and agent underneath it.

​
Locks apply to configuration, not to running agents

A lock stops a feature from being set up or turned on. It does not reach back into agents that are already configured:
  • an agent already linked to a Google business listing keeps using it on calls;
  • an agent already taking card payments keeps working, and in-flight charges always complete;
  • an agent already assigned a cloned voice keeps speaking with it;
  • an agent already set up to text keeps sending and reading SMS, and its Send SMS and Check SMS Replies functions stay editable.
In every case the existing value stays visible so it can be removed — clearing a field is never blocked, so a lock can never leave an organization stuck with configuration it cannot undo. To stop a feature that is already in use, lock it and then turn it off on the affected agents.

​
Example

Suppose you lock Google Calendar on the reseller Acme Resold:
  1. Every organization under Acme Resold immediately shows Google Calendar as Locked upstream.
  2. When anyone edits an agent in one of those organizations — in the Dashboard or in Connect — the Google Calendar integration no longer appears.
  3. An API call setting Google Calendar credentials on such an agent is rejected.
  4. Organizations under other resellers are unaffected.
To reverse it, open the matrix, find the Acme Resold column, and click the Google Calendar cell (or use Allow all on that column) to remove the lock.