Administration
The Global Admin console
The platform operator's portal (/p/ga):
| Page | |
|---|---|
| Companies | Every tenant — profile, plan, status, and (with the Super Admin's approval) support access to its data |
| Plan Management | The plan catalog and the feature catalog |
| Subscriptions | Active subscriptions, periods, renewals |
| Users & Roles | Platform users and role assignment |
| Reports | Cross-tenant reporting |
| Salary Setup | The salary-component catalog new companies inherit |
| Support Tickets | The client ticket queue |
| Audit Logs | The platform audit trail |
| Settings | Platform configuration, including deployment mode |
Activity logs vs. audit logs
| Records | Scope | |
|---|---|---|
| Activity log | User-visible actions — who did what, when — for a company's own review | Tenant |
| Audit log | Security-relevant events — sign-ins, permission changes, data access grants, sensitive-field reveals | Platform, Global-Admin visible |
Both are append-only.
Maintenance mode
A Global Admin can put the platform (or a tenant) into maintenance mode — active sessions see a Maintenance page and writes are held — for a migration or an incident, then lift it. The state is served from the API so every client picks it up on the next request.
Deployment mode
One platform-wide setting: SAAS or ENTERPRISE.
| SaaS | Enterprise | |
|---|---|---|
| Demo requests | ✅ | hidden |
| Plan catalog & plan requests | ✅ | hidden |
| Subscription billing | ✅ | hidden |
| Multi-tenant self-serve registration | ✅ | typically one tenant |
| Auth | Native email / password | Keycloak SSO + per-tenant LDAP |
Enterprise is the shape used when HridaOne is bundled as a dedicated install alongside Hrida AI Studio.