---
title: "Industrial Company with internal customers"
canonical: "https://docs.loriot.io/space/NMS/6032128/Industrial%20Company%20with%20internal%20customers"
format: markdown
---
**Business background**

Industrial companies are the end users in the LoRaWAN<span style="color: #000000">®</span> ecosystem and are usually responsible for setting up and managing their own network coverage, resources and output on the LNS without the intention to resell it to external stakeholders.

**Main goal:** Manage internal use cases compatible with organisation's choice of hardware and software

**Important features: **<span style="color: #3366ff">[Community access](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031837)</span><span style="color: #3366ff">, </span><span style="color: #3366ff">[Gateway Status Alerts](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6033239)</span><span style="color: #3366ff">, </span><span style="color: #3366ff">[Server Operator Alerts](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032955)</span><span style="color: #3366ff">, </span><span style="color: #3366ff">[Gateway Management - Best Practices](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031545)</span>


### How to manage internal customers/use cases on the server

---

In order to exploit features only available on private servers (e.g., community access, unlimited device number), it is highly recommended to have a private server deployed, either on-premise or hosted 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

---

Organizations are created at 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 [organization and user management](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6037557) across the whole server.

Along the internal organization, a myriad of **other organizations **can be created representing the internal customers/use cases. Either the Server Operators from the industrial company or their internal customers are responsible for creating their own organizational environment including various <span style="color: #3366ff">[account profiles](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6033522/LORIOT%27s+Multitenancy+Concept#Account-Profiles)</span>. Due to the multitenancy, the internal organization and the various customers are independent of each other.

![loriot-Industrial-company_organization-management.png](media://f0d73874-a356-4694-811f-c67cca8113d7)

#### Management of resources

---

Each internal customer is responsible for the network and application management.

![loriot-industrial-company-resource-management.v2.png](media://c2a7c045-15e4-4ed3-8c5e-f78f4d73706f)

Networks and corresponding applications can represent regional areas (e.g., North Europe, France).  It is up to the internal customer to decide on the geographical areas (countries, cities, etc.). 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.   


##### <u><span style="color: #000000">**Networks**</span></u>

![image](media://8bcd3617-5415-46bc-a9e4-578000868cee)

  


![image](media://0fe415da-4c6e-43e8-a8c7-02fbf4356709)

  


##### <u>**Applications**</u>

Applications including the end devices could be divided as well into geographical areas.

![image](media://2764dc95-42ca-4212-aa24-a2b86d83ffc1)


  


> ℹ️ Regardless of the chosen organization constellation, it is recommended to have dedicated teams (team gateways, team devices, team application) as account users to have shared ownership of the resources.

  


#### Using dedicated user accounts

---

Dedicated user accounts allow the organization to have the ownership of the resources shared among different individuals. That might be particularly helpful when an 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 regions (e.g., [europe@company.com](mailto:europe@company.com))
- Accounts per teams (e.g., [gateway@company.com](mailto:gateway@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) remain with the dedicated user account


For further info on how to ensure network coverage across the server, see the following <span style="color: #3366ff">[article](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031545)</span>.