In MobileTrack Nexus solution, a Customer Company represents the B2B or B2C organisation/single person that subscribes to and utilizes the platform. (a paying customer). This entity is central to the management and organization of various resources within the platform. it contains accounts, environments, devices and/or roles.
Accounts: Individual user profiles or user groups within the company. Each account is associated with specific roles and permissions.
Environments: Logical groupings within the company. Environments help organize resources and apply different configurations or policies.
Devices: Physical or virtual hardware managed by the company. Devices may include mobile phones, IoT devices and other devices that connect to the platform.
Map Markers: customizable map markers to denote how devices are displayed on a map.
Roles and Permissions: Role-Based Access Control (RBAC) is used to define access levels and permissions for users based on their roles. This ensures that users can only access resources and perform actions appropriate to their responsibilities.
Settings: Configuration options that apply to the company’s use of the SaaS platform. Settings may include security configurations, notification preferences, and other customizable options. users can make their own overrides to these settings for personal preference.
Templates: Companies can utilize their own custom templates when sending emails, SMS, XML or JSON to third parties (devices, mail server, api server's, etc.) In this way, a company can customize the look and feel of the messages sent from the platform.
Data Protection: Ensuring that all data related to accounts, devices, and other resources is securely stored and transmitted and never mixed with the data of other customers. Encryption and secure access controls are essential for protecting sensitive information.
Access Control: Implementing RBAC to manage who can access various resources and perform specific actions within the platform. Proper role management helps prevent unauthorized access and maintains operational integrity.
Compliance: Adhering to relevant regulatory requirements and standards, such as GDPR or NIS2, to ensure that the company's data practices are lawful and ethical.
Audit Trails: Maintaining logs and records of user activities, changes to settings, and other important actions. This helps in tracking and responding to any security incidents or compliance issues.
Consider a customer company named "TechCorp". TechCorp is a factory with Research and Development facilities who use a ton of IoT devices for telemetry and tracking of assets within and outside the facilities. Within TechCorp, the structure may include:
Accounts: Employees of TechCorp, each with a specific role like "Admin" or "User" or "HR".
Environments: Separate environments for facilities or departments within the company, or mobile environments for field operations.
Devices: Mobile phones, trackers, and other IoT devices generating data used by TechCorp employees or deployed throughout their facilities.
Metadata: Information about each device's location, status, and maintenance history.
Roles and Permissions: Admins have more access based on their level of privilege, while regular users have restricted access based on their roles.
Templates: TechCorp uses custom email templates in order to have their own custom branding in their header/footer when sending emails to their customers or employees.