How-To Guides / Admin
Add a member, and manage seats
An invitation is the only way into a Telara organization. This covers inviting someone, choosing their role, what happens when the seats run out, and where the plan and usage figures live.
Before you start
Where this happens, and who can do it
Starting screen: in the Telara dashboard, open Organization → Members in the left sidebar.
You must be an organization administrator. A member or viewer who opens the page sees a restricted notice instead of the member list, not a partially filled screen.
There is no self-service sign-up. People do not create their own accounts and request to join — an administrator invites them, and that invitation is the account. If someone says they cannot register, that is the product working as designed and the answer is an invitation from this screen.
Steps
How to invite a member
Full access. Only an administrator can grant this role, so an admin cannot be created by someone who is not already one.
Standard access. The default for someone who will use Telara rather than administer it.
Read-only.
Seats
When the seats run out
The Seat Usage bar escalates before it blocks you. At 80% of the maximum it turns amber; at the limit it turns red, Invite Member is disabled, and an Upgrade Plan control appears beside the bar. Upgrading from there refreshes the seat count and the invite control in place, without a reload.
If the seat figures fail to load, the page keeps the member list and shows a degraded-data notice rather than inventing a seat state from missing numbers. A missing bar means the seat read failed, not that you have unlimited seats.
Plan and usage
Where the numbers behind the plan live
Organization → Billing is the usage and cost view. It opens on the current month and can be switched to the previous month, with a three-month trend below.
What it meters, each as its own component: user seats, automation usage with a success rate, resources, integrations, sync horizon, MCP configurations, headless agents, and AI credits split into a per-user allowance and an organization pool. A period with nothing recorded says so explicitly — an empty cost view is a statement that nothing was metered, not a loading failure.
Deletion
Deleting the organization
Permanent deletion lives on its own screen, Organization → Delete organization, deliberately apart from the member list — it is the only thing that page does. Administrators only; anyone else sees a restricted notice. It removes member access and the API keys tied to the tenant, and the provisioned tenant infrastructure under platform policy. It asks for explicit confirmation and it cannot be undone.
Result
What you should see when it worked
A new row in the member list marked Pending, with its expiry and the name of whoever sent it, and a Seat Usage count that has gone up by one. When the person accepts, the row stops being Pending and they can sign in at their assigned role.