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: Create Organizations in Dashboard and Create Agents in Dashboard are for resellers who provision through a partner portal. A Partner locks them on a reseller, and that reseller’s users can no longer create organizations or agents in the Dashboard — nor mint new API keys as a way around it. They are placeable on reseller and partner targets only.

​
Templates

The Templates rows control which of the ready-made agent templates an organization may create new agents from. Locking one hides that template in the new-agent wizard, in both the Dashboard and Connect, and rejects an equivalent request to the API.
Outbound Calling Agent governs call direction, not just one card. The Blank Slate template also offers an “Outbound (places calls)” choice, which creates exactly the same kind of agent. Locking Outbound Calling Agent therefore hides the Outbound template and removes that choice from Blank Slate, leaving Blank Slate available for inbound agents. This is intended: the lock means “this organization may not create agents that place calls”.The two are otherwise independent — locking Blank Slate Agent alone still leaves the Outbound template usable.
Listings Search ships locked for every organization, and every organization created later starts locked too. Organizations that already had an agent using it when it was released were left unlocked. A partner unlocks it for an organization by clicking that organization’s Listings Search cell. While it is locked, the function is hidden in the agent editors, and adding it or changing its listings page is refused. See Listings Search.

​
LLM Models

The LLM Models rows control which language models an organization’s agents may use. Locking one removes it from the model picker in both the Dashboard and Connect, and rejects an equivalent request to the API.
GPT-4.1 is deliberately absent from the matrix. Every agent must have a model, so if every model could be locked an organization would be unable to save an agent at all. GPT-4.1 is therefore always available and cannot be locked. It is also the model the API assigns when a request omits one.
These rows are the only model control. There is no separate per-organization “Available Models” card or “Model Selection” switch in the Customers section any more: every model in the catalogue, Claude Sonnet included, is available to an organization unless a Partner or Reseller locks its row here.At rollout, an organization-level Claude lock was seeded on every organization that had not previously been enabled for Claude Sonnet, so no organization gained or lost access. To give such an organization Claude, unlock its LLM: Claude Sonnet row.

​
TTS

The TTS rows control which text-to-speech providers an organization’s agents may speak with. Locking one removes all of that provider’s voices from the voice pickers in both the Dashboard and Connect, and rejects an equivalent request to the API.
Cartesia is deliberately absent from the matrix. Every agent must have a text-to-speech provider, so if all of them could be locked an organization would be unable to choose a voice at all. Cartesia is therefore always available and cannot be locked. It is also the provider the API assigns when a request omits one, and the provider cloned (custom) voices use — so locking MiniMax and Inworld together still leaves a working voice picker.
The provider follows the voice. There is no separate provider control in the agent editors: choosing a voice sets the provider it belongs to. Locking a provider is therefore best read as “these voices disappear from the picker”.

​
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.
  • Agent creation — A locked template does not appear in the new-agent wizard, and the create request is refused server-side even if the wizard is bypassed.
  • 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), the seven UCaaS agent functions (adding the matching tool to an agent’s extensions.tools), NS Password Reset (adding the Reset Password tool to an agent), templates (agentType on POST/PUT /v1/agents), LLM models and TTS providers (model and the TTS provider on POST/PUT /v1/agents), Email Template Manager (the Email Templates API — creating or editing a template, except an archive-only update, and newly binding a template to an agent), SMS Template Manager (the SMS Templates API — creating or editing a template, except an archive-only update, and newly binding a template to an agent), Screenshare (screenshareEnabled on POST/PUT /v1/agents), and Listings Search (adding a listings_search tool to extensions.tools, changing its listings page, or turning on deposit and fee reading).
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 using a UCaaS function keeps using it on calls, and the function stays editable and removable — this applies to all seven (Get Timeframe, Verify User, Lookup Directory, Set Call Forwarding, Send SMS, Check SMS Replies, Chat Notification), and to withdrawing the Netsapiens integration itself;
  • an agent already able to send password resets keeps sending them, and its Reset Password function stays editable and removable;
  • an agent already searching listings keeps doing so on calls, and its Listings Search function stays editable and removable;
  • an agent already created from a template keeps working and stays fully editable — locking a template only stops new agents being created from it;
  • an agent already running a locked LLM model or speaking with a locked text-to-speech provider keeps doing so, on calls and in the editor. Its model and voice stay visible and re-saveable, marked no longer available — so every other field on that agent remains editable, and it can always be moved to a model or provider the organization still has.
Screenshare is the exception to everything above. Locking it does not only stop new setup: while the lock is in place, no call in that organization is offered a share, on every agent, including agents that already had screenshare switched on. Nothing is cleared — each agent’s toggle and the organization’s policy stay stored and editable, and screenshare resumes as soon as the lock is removed. See Screenshare.
An agent’s call direction is fixed when it is created. Locking Outbound Calling Agent therefore never disturbs an organization’s existing outbound agents — but it also cannot convert them to inbound. To stop outbound calling that is already in place, lock the template and then disable or delete the affected agents.
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.