---
title: "LORIOT's Multitenancy Concept"
canonical: "https://docs.loriot.io/space/NMS/6033522/LORIOT's%20Multitenancy%20Concept"
format: markdown
---
'Software Multitenancy' or 'Multitenancy' for short generally refers to an architecture in which multiple applications or 'tenants' share an environment but are otherwise logically isolated.
On LORIOT's Network Servers, we enable Multitenancy by allowing multiple users to coexist and operate on the same server instance, be it a privately-owned server or a LORIOT-managed Public Server. This is made possible by the core aspects of LORIOT's Multitenancy concept:
### **Organizations**
---
Organizations are environments that allow users on a given server to share access to their applications and networks between users of the same organization while isolating their data from anyone else. No account contained in one organisation can access or view any function/resource from another Organization.
> ℹ️ Read more about them [in the documentation article about Organizations.](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6033555)
### **Account Profiles**
---
LORIOT's** **Network Servers allow for varying degrees of access to the server and management privileges depending on the user's role. Account Profiles are a quick and easy way to define a user's role on the server.
The following table describes the available Profiles and their respective permissions on the server.
| | | | | | | |
| --- | --- | --- | --- | --- | --- | --- |
| **Profile ** | **Read ** | **Write** | **Invite users** | **Create new Organizations** | **Transfer Account Resources** | **Change server configuration** |
| Server Admin | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Server Operator | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| Organization Admin | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| Standard User | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ |
| Read-only User | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ |
> ℹ️ In this context "**Read**" means viewing the data, devices, networks, etc. already available on the user's account. "**Write**" means being able to create, register or otherwise modify data, devices, networks, etc. on the user's account.
### User Levels
---
When using our Admin API the parameter "**level**" will sometimes appear in relation to any user-related API calls. These levels are fixed numbers that correspond with the different account profiles.
This table describes the relation between user level and account profile.
| | |
| --- | --- |
| Level | Profile |
| 0 | Read only User |
| 0 | Normal User |
| 50 | Organization Admin |
| 55 | Server Operator |
| 100 | Server Admin |
### Account Hierarchy
---
The account profiles and the roles they represent are subject to a well-defined hierarchical structure. Generally speaking, the higher up the chain the more privileges a role will have.
The table below shows a visual representation of the account hierarchy on a LORIOT Network Server.
