Skip to main content

Tenant Management

The following multi-tenancy concept is based on a technical foundation in azuma doa and implemented across all azuma products.

Idea​

Most products are defined to store and access data based on the currently logged-in user.

The current user can e.g. be identified via

  • identity id (user data)
  • organization id (organization data)
  • department id (partial organizational data)
  • ...

In the health industries, there are many cases in which the individual account could belong to multiple organizational instances, e.g.

  • a doctor might work in multiple practices
  • a supervisor in a hospital might also advise further hospitals as well as have his own practice
  • ...

Solution​

To support the requirements mentioned above, azuma doa implements the following concept

  • Users(user accounts) can belong to multiple tenants
  • Users(user accounts) can belong to multiple departments within a tenant
  • Users(user accounts) can have different roles in different tenants / departments
  • Users(user accounts) an have different licenses in different tenants (coming soon, see Roadmap

Products implementing the concept of azuma doa can choose how to map tenant-data based on their requirements.

Tenant​

A tenant in azuma doa is either a practice or an organization with the following required data:

  • Name
  • Address (Selection of the correct Address is powered by google maps)
  • (Optional) Specific data for 'Practice'
    • BSNR ('Betriebsstättennummer')
    • NBSNR ('Nebenbetriebsstättennummer')

Integration scenarios​

Scenario 1: User mapping​

The most simple integration scenario maps application data to an individual user. For that, only the association between application data and identity id of the user is required.

Every account/identity' in azuma doa has an unique identity id, which can be used for this integration scenario.

Scenario 2: Single tenant mapping​

A standard integration scenario is to support only one single tenant.

tip

This scenario is very easy to implement, but very hard to change to a multi-tenant scenario.

In azuma doa you can achieve this scenario, by

  • selecting the tenant automatically, if the user has exactly one tenant
  • asking the user to select a tenant from his list of assigned tenants
tip

Even if you plan on only supporting single tenants, from a technical standpoint we strongly advise you to consider/implement the multi-tenant scenario below.

Scenario 3: Multi-tenant mapping​

The more advanced integration scenario maps an application to a multitude of tenants. This scenario still supports the single tenant usage scenario, but also allows to work with multiple tenants simultaneously.

Example​

Coming soon.

Technical Implemenation​

Coming soon.