KoolAssist for Site Admins

Operate the whole KoolAssist platform — every customer organisation, from one place.

Getting started

1 · Sign in as site admin

The site admin (super-admin) account manages the entire server — all customer organisations, not just one.

  1. Sign in at koolassist.com/login with the super-admin account.
  2. You see the full menu, including organisation management that customer admins don't have.

The admin panel overview · narrated

How-to

2 · Create customer organisations

Each customer is a self-contained organisation (tenant) — its own users, devices and address books, fully isolated from every other customer.

  1. Open Tenants (super-admin only).
  2. Click Add, enter the organisation name and its seat/device allowance, and save.
  3. Create that organisation's first customer admin account — they take it from there for their own team.
Isolation is enforced server-side. A customer admin only ever sees their own organisation's data — never another customer's.
How-to

3 · Set seat limits

Every organisation has a seat limit (how many team logins it may create) tied to its plan.

  1. Open the organisation under Tenants.
  2. Set the seat and device allowance to match their plan, and save.
  3. Once they hit the limit, further additions are blocked until you raise it.
Basics

4 · Admins & roles

KoolAssist has three roles:

  • Site admin — you. Runs the platform and all organisations.
  • Customer admin — runs one organisation's team and devices.
  • User — a technician or end user within an organisation.

Assign the least privilege that does the job — most people are users or customer admins.

Operations

5 · Server & relay health

KoolAssist runs on your own infrastructure — a rendezvous (ID) server and a relay server.

  • Check that both services are running and reachable on their ports.
  • Confirm clients show Ready (green) — that means they reached the ID server.
  • The relay only carries encrypted traffic when a direct peer-to-peer path isn't possible; it never sees session contents.
How-to

6 · Single sign-on (OIDC)

You can let an organisation sign in with its own identity provider (Microsoft Entra, Google, Okta, etc.) via OIDC, so accounts bind automatically to the right organisation.

  1. Register KoolAssist as an application in the customer's identity provider and copy the client ID/secret and issuer URL.
  2. Add the OIDC provider in the panel and bind it to that organisation.
  3. Users signing in through it are placed in that organisation automatically.
Operations

7 · The client download

The branded KoolAssist client is served from koolassist.com/remote. It's pre-configured to point at your servers, so customers download one file and it just works — no manual server settings.

Security

8 · Security & data policy

KoolAssist is built on a zero-trust, no-data footing:

  • Self-hosted. IDs, relay and the panel all run on Kool Telecom infrastructure — no third-party cloud.
  • End-to-end encrypted. Session media is encrypted between peers; the relay only passes ciphertext.
  • Tenant isolation. Each organisation's data is walled off server-side.
  • Least data. We keep what's needed to run the service and audit access — nothing about the contents of your sessions.

Read the customer-facing summary at koolassist.com security.