> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linkiasoft.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform administration

> Managing plans, growth packages, tenants and entitlement overrides. For platform operators, not workspace admins.

<Note>
  This page is for whoever **operates** Linkiasoft, not for administrators of an individual
  workspace. These screens are not visible to a workspace admin, however senior — the
  permission is a separate, platform-level one.
</Note>

## Manage Plans

**Platform → Manage Plans.** Create and edit the subscription plans workspaces can be put
on, and the growth packages they can buy.

A plan defines:

| Setting                   | Controls                                                            |
| ------------------------- | ------------------------------------------------------------------- |
| **Units per month**       | The shared pool for active contacts and AI replies                  |
| **Max channels**          | How many channels can be connected                                  |
| **Allowed channel types** | Which kinds of channel are available                                |
| **Max users**             | Team size                                                           |
| **Feature flags**         | Whether AI, campaigns, automations and calling are available at all |

**Growth packages** are bulk unit top-ups, optionally with bonus units at larger sizes. They
add to the pool without changing the plan — the right instrument for a customer having one
unusually busy month.

## Manage Tenants

**Platform → Manage Tenants.** Every workspace on the platform: assign a plan, view usage,
and set entitlement overrides.

### Entitlement overrides

Per-tenant exceptions to their plan — extra channels, extra users, a higher unit ceiling,
SMS credits — without inventing a bespoke plan for one customer.

<Warning>
  Overrides are invisible from the customer's side: their billing page shows the effective
  limits, not the fact that they were overridden. Six months later nobody remembers why one
  tenant has twice the channels. Record the reason and the expiry somewhere your team will
  actually look.
</Warning>

Prefer moving a customer to a different plan when their needs are permanent; use overrides
for genuine one-offs and temporary arrangements.

## Diagnosing a customer's problem

The tenant view is the fastest route to most "it stopped working" reports:

<Steps>
  <Step title="Check usage against the plan">
    An exhausted unit pool stops outbound sending. It presents to the customer as messages
    silently not going out.
  </Step>

  <Step title="Check feature flags">
    A feature the customer expects may simply not be on their plan.
  </Step>

  <Step title="Check channel and user counts">
    At the cap, "add channel" and "add user" fail with what looks like a bug.
  </Step>
</Steps>

Only after those three is it worth looking at the workspace's own configuration — roles,
channel grants and [assignment settings](/help/routing/how-assignment-works).