---
title: "LoRaWAN® Network Provider"
canonical: "https://docs.loriot.io/space/NMS/6033657/LoRaWAN%C2%AE%20Network%20Provider"
format: markdown
---
**Business background**
LoRaWAN® Network providers are investing heavily to build coverage across a certain region with the intention to sell this coverage to their customers. The LORIOT Network Management System (NMS) provides all the necessary features to achieve this from a technical and commercial perspective. LoRaWAN® network providers are responsible for setting up and controlling the network coverage across the server in order to ensure stable gateway connectivity they are selling to their customers.
**Main goal**: ensure stable server network coverage and provide LoRaWAN® coverage for their customers.
**Recommended articles**: [Community access](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031837), [Gateway Status Alerts](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6033239), [Server Operator Alerts](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032955), [Gateway Management - Best Practices](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031545)
### How to manage organizations and resources across the server
---
Due to some essential features only being available on private servers (e.g. community access), it is highly recommended to have a private server deployed, hosted on-premise or by LORIOT. The outlined options are only examples of many on how to manage the best organizations and resources on the LORIOT NMS but might be implemented differently according to each use case requirement.
#### **Management of Organizations**
---
Organizations are created in the Admin interface by Server Admins and Server Operators only - responsible for user management across the server. It is recommended to have **one internal organization **including further Server Operators and other available user roles like Organization Admins and Users. The internal organization can be dedicated to the management of the network connectivity and coverage across the server including tasks such as the setting up of networks, registration and management of gateways. Although the networks are created within the internal organization, their coverage can be exploited across the server when [community access](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031837) is enabled.
Along the internal organization, a myriad of **other organizations **can be created representing the customers who purchase the network connectivity from the network provider. Each customer is responsible for creating its own organizational environment including various [account profiles](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6033522/LORIOT%27s+Multitenancy+Concept#Account-Profiles). Due to the multitenancy, the internal organization and the various customers are independent of each other.
#### **Management of resources**
---
Below two possible options are outlined on how a LoRaWAN® network provider operates:
- LoRaWAN® network provider set up and operates the server networks and registered gateways for all its customers. Devices are managed by each customer independently.
> ℹ️ In this case, make sure to set the gateways [limit](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032673/Resource+limits#Resource-limits-for-organizations) to 0 when creating new organizations!
- LoRaWAN network providers set up and operate the server networks and registered gateways with the option to allow customers to manage their own networks and gateways. When community access is enabled on those additional gateways, the network coverage is increased across the whole server.
Organization Admins and Users are those who can manage resources at the organisational level. Additionally, Organization Admins can manage user accounts and access their resources from the admin interface. Below a best practice example is outlined on how to manage resources using dedicated user accounts.
#### **Using dedicated user accounts**
---
Dedicated user accounts allow the organization to have ownership of the resources shared among different individuals. That might be particularly helpful when a user leaves the organization, his/her resources do not be shifted to another account as the ownership is shared.
Accounts can be classified as followed:
- Accounts per network region (e.g., europe@company.com)
- Accounts per team (e.g., gateway@company.com)
- Accounts per user (e.g., user@company.com)
> ℹ️ Individual user accounts can still exist along those dedicated user accounts to add gateways when [networks are shared across the organization](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032731/Organization+User+Access#Networks). The [ownership of the resources](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032673/Resource+limits#Resource-ownership-and-limits) remains with the dedicated user account
For further info on how to ensure network coverage across the server, see the following [article](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031545).