Role model
Access is organized into five functions. The client reviews their service, usage and documents. The operator runs and supervises technical work. Support handles tickets. Billing manages charges and tax documents. Administration maintains the platform.
No role inherits permissions out of convenience: if a function does not need a capability, it does not have it.
Isolation between companies
Each client's data is separated from every other client and from the platform infrastructure. A query made from one company's account cannot reach another company's information, even when both use the same service.
Sessions and authentication
Sign-in uses opaque sessions with expiry, CSRF protection and lockout after failed attempts. Signing out invalidates the credential on the server, not only in the browser.
What the client sees in the panel
Service status, contracted periods, usage, issued and pending charges, notifications and expiry warnings. Cost and capacity information is visible by design: service continuity should never surprise anyone.