---
title: "End-to-end Solution Providers"
canonical: "https://docs.loriot.io/space/NMS/6033047/End-to-end%20Solution%20Providers"
format: markdown
---
**Business background**
End-to-end solution companies provide their customers with a LoRaWAN® solution including the hardware (devices and gateways) and the software side (application) where LORIOT's LNS is usually integrated. The end-to-end solution providers take care of setting up the network of gateways and registration of devices and will enable their customers access to their IoT platform dashboards where the collected data is already processed and visualized. Therefore, their direct customers usually do not have access to the LORIOT network server and resources will be managed directly by the provider. The LORIOT network server provides all the necessary features to achieve this from a technical and commercial perspective. Best practices are outlined in this article.
**Main goal**: Ensure smooth integration of the LNS into the end-to-end solution
**Recommended articles**: [API Documentation](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031752), [Organization User Access](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032731), [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 network server but might be implemented differently according to each use case requirement.
#### **Management of Organizations and User Accounts**
---
End-to-end solution providers usually do not grant their customers access to the LNS and manage the resources of each customer. As a result of that, one internal organization that manages all resources might be adequate including different user accounts. Optionally, parallel to this organization another can be created for test purposes.
#### **Management of resources**
The creation and management of networks/applications are handled by the end-to-end solution providers. A few constellations are explained in more detail below. It is recommended to enable the [organization user access](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032731) on all resources in order to allow all user accounts within the same organization to access and modify resources.
As the networks and applications are managed by the end-to-end solution providers for all customers, they can be categorized as followed:
##### **Networks**
Networks can represent regional areas (e.g., North Europe, France). It is up to the the end-to-end solution provider to decide on the geographical areas. When several areas within the same country are created, the ascending/descending sort option can be helpful to view the networks per country. The same applies to cities.
##### **Applications**
Applications including the end devices could be divided into the customers/use cases.
> ℹ️ Regardless of the chosen organization constellation, it is recommended to have dedicated teams (team gateways, team devices, team application) as account user to have shared ownership of the resources.
#### **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](mailto:europe@company.com))
- Accounts per team (e.g., [gateway@company.com](mailto:gateway@company.com))
- Accounts per user (e.g., [user@company.com](mailto: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). The [ownership of the resources](https://docs.loriot.io/display/NMS/Resource+limits#Resourcelimits-Resourceownershipandlimits) remains with the dedicated user account
#### How to manage resources on the LNS and the provider's IoT plattform in the most efficient way?
---
Resources (applications, devices, networks, gateways, etc.) that are created from the provider's IoT platform, need to be registered as well on the LNS resulting in duplicate work. The same procedure applies to any updates of the configurations. In order to save time and be more efficient, it is recommended to establish automated API calls. In our [API documentation](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031752), you will find the necessary information about available API calls.
> ℹ️ For authorization, it is recommended to use an [API key](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/462520321) due to its permanent availability.
> ℹ️ Take advantage of the [community access](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031837) to share network connectivity across the server.
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).