Organizations, MSPs and the hosting provider
One YARMA server can hold many organizations (tenants). Each has its own users, devices, policies, audit log and sign-in settings; nothing is shared between them.
| Kind | What it is | License |
|---|---|---|
| Organization | a company managing its own devices | its own |
| MSP | a service provider with client organizations | its own; covers its clients' devices |
Client (msp_client) |
an MSP's customer | covered by the MSP's license |
| Provider | the operator of a cloud server (for YARMA Cloud: Avadeja), parent of the organizations and MSPs it hosts | a provider license: unlimited devices; each hosted organization still needs its own |
The provider
A server's provider is the organization of the company running it. It becomes provider by installing a provider license (Settings → License), which only the License Center operator issues (operator console → customer → Actions → Provider license). Because the license is signed, a self-hosted installation cannot make itself a provider; on self-hosted servers organizations are ordinary organizations or MSPs.
The provider sees and opens every organization it hosts, but each hosted organization is licensed separately and its devices never count against the provider's license.
Managing organizations
Customers → Organizations (providers and MSPs, needs msp.access) lists every
organization under you with:
- devices and how many are online, users and how many signed in during the last 30 days, the last sign-in;
- the license (plan, device limit, state) — for MSP clients "covered by your license";
- status (active or suspended).
From there:
- Open switches into the organization to support it; every switch is audited in both organizations. The header shows which organization you are acting in.
- New organization / New client creates one with a first administrator and shows the initial password once. Providers choose between an organization and an MSP; MSPs create clients. A provider-hosted organization needs a license before devices can enroll.
- Suspend signs out everyone in the organization and blocks sign-in until Resume. Devices stay enrolled and keep their configuration.
API: GET /v1/organizations, POST /v1/organizations, PATCH /v1/organizations/{id}
({"disabled": true|false}), POST /v1/msp/switch.
Cloud customers are set up automatically
On YARMA Cloud, a customer who buys a cloud plan on the website gets an organization without anyone lifting a finger: the License Center queues the job, the cloud server creates the organization under the provider with a license bound to it, and the customer's administrator receives an email with a one-time link to choose a password (valid 7 days). Details: License Center operations.
Documentation for Yarma 0.1.0-alpha.4. Something unclear? .