Platform operations
IT Admin for multi-tenant campus ERP
The control plane institutions need after go-live — tenants, entitlements, integrations, devices, JIT, session assurance, and audit — not just a login page and a support email. Full access-control model on Security & compliance.
What IT Admin covers
Built for college IT teams and platform operators who run Tuling for one campus or a group.
-
Tenant isolation
Each institution runs on its own isolated tenant and database boundary — not a shared spreadsheet of rows with a college_id column and hope.
-
Roles, entitlements & access
Role portals plus the full access stack — permission claims, ABAC policy packs, PDP decide API, JIT grants, session step-up, and SoD trails — with module entitlements matching what the campus licensed.
-
Integrations & API keys
Manage biometric devices, payment gateway keys, messaging providers, webhooks, and partner API access from one ops desk.
-
System health & logs
Technical support queues, health checks, and operational logs so IT is not chasing screenshots in WhatsApp groups.
-
Audit & security
Policy decision audit, JIT approve/revoke history, session assurance events, and trails for sensitive actions — the controls multi-campus groups expect from a modern ERP. See Security & compliance for the full model.
-
Subdomain & branding
Institution subdomain provisioning and tenant branding so each campus feels like their system — still operated under one platform.
See tenant ops on a live walkthrough
We’ll map entitlements and integrations to your institute’s role matrix.