1. Scenario overview
The platform serves operations staff, channel agents, customer service, finance, and audit. Loose permissions lead to an unauthorized suspend or resume, a bulk export of customer data, or a change to settlement settings. Roles and audit on the SimtoLink IoT Cloud Platform use RBAC (role-based access control): permissions attach to roles, and people attach to roles. A data domain sits on top, so a person sees only the SIMs and customers in their account, project, or channel. Sensitive actions — bulk suspend, a detail export, a change to the revenue-share rate — require a second authentication or a two-person review, and every action is written to an audit log that cannot be altered.
It works with multi-tenant management. Isolation between tenants is the first boundary. Roles inside a tenant are the second. The design follows the access-control and audit expectations in MLPS 2.0 and ISO 27001, which is what large buyers and a listing audit ask for.
2. Core capabilities
Role and permission matrix
Operations, customer service, finance, and read-only audit are preset, and you can add your own. Permissions go down to menu, button, and API. You can separate “masked fields only” from “full fields”.
Data domains and row-level access
Filter by org tree, project, or agent line. Customer service sees only the customers tied to a ticket. A channel manager sees only the orders and revenue share of that channel.
Sessions and security
IP allowlists, alerts on an unusual login location, and automatic sign-out after idle time. When OAuth/SSO single sign-on is connected, sign-out and token revocation stay in sync.
Audit and trace
Each record keeps who acted, when, on what, a summary of the before and after values, and client details. Search by time, person, or resource type. Retention is configurable, and logs can be archived to storage the customer owns.
3. How this differs from consumer accounts
Consumer user management is the account system for end customers. This page is permissions inside the company and the channel console. Both follow least privilege. The sign-in method and the compliance terms are different.
4. Where teams use it
- Connected-vehicle B2B2C channels: Each channel level maps to an RBAC role. Customer service sees only SIMs tied to a ticket. Finance sees only settlement data. A bulk suspend needs a second authentication. That is the access control and the action record regulators ask for.
- Internal audit at a large shared-device operator: Operations, finance, and internal audit get read-write, read-only, and audit-only roles. A change to the revenue-share rate needs two people. Audit logs are exported and filed on a schedule, which is what an MLPS 2.0 level 3 review and ISO 27001 expect.
- White-label SaaS tenants: Each company is its own tenant. Data domains stop one tenant reading another. An agent sees only SIMs and orders in its channel, and project teams do not see each other’s data.
5. How to put it in place
Write the permission matrix before go-live and have legal and internal control sign it. Run a permission review on a cadence, and reclaim accounts when someone leaves or changes role. Put a watermark and an approval flow on export permissions.
6. What changes in daily operations
Roles and audit lower the chance of unauthorized access and a data leak, and they meet MLPS 2.0 and ISO 27001 on access control and audit. A second authentication and a two-person review on critical actions catch mistakes and deliberate misuse. The full audit log supports an incident trace and compliance evidence, which a procurement review or a listing audit can follow.