A SaaS platform with a separate tenant for each customer organisation.

When the product serves several organisations in the same application, each organisation's data stays in its own space. We build the tenant, the roles, export and delete rights, then the administration console and the subscription. Application hosting can stay with CyberIT.

Isolation between organisations

Separate tenant, shared administration

The customer organisation sees its own users and documents. The administration console sees all of them.

Tenant A

Users, export and delete rights, only in this space.

Tenant B

It does not find tenant A's documents. They are not in its space.

Platform administration

Sees both organisations. An ordinary user does not.

What a tenant contains

Each organisation has users, data, export and a clear rule for who can delete. The subscription is set after this separation is operational.

A user from the first organisation searches for a document of the second and does not find it, because the document does not exist in that user's space. The platform administrator sees both organisations. An ordinary user sees only the tenant they are invited to.

Where it is used

A new product

The first and the second organisation start in separate spaces.

A service run by email today

The flow that currently leaves by email enters the platform, with accounts and history.

Administration console

The platform operator sees the organisations. Each customer stays in their tenant.

Questions

Does hosting sit in the same project?

It can stay with CyberIT, on a plan fit for an application. The plans published for a site are on the hosting page and are chosen separately from the platform.

Continue