Admin Console
The Admin Console is the single control plane for ServiceCore. From one panel your administrators define who can do what, how the organization is shaped, and how the platform behaves — roles, permissions, organizational structure, workflows, and platform-wide configuration are all managed centrally, with the granular controls a multi-company, multi-tenant setup demands. Because every one of ServiceCore's 29 modules runs on one shared data model, a change made here propagates consistently across incident, request, change, asset, and service-level management instead of being re-applied module by module.
Built for the way admin console should work
The Admin Console is the single control plane for ServiceCore. From one panel your administrators define who can do what, how the organization is shaped, and how the platform behaves — roles, permissions, organizational structure, workflows, and platform-wide configuration are all managed centrally, with the granular controls a multi-company, multi-tenant setup demands. Because every one of ServiceCore's 29 modules runs on one shared data model, a change made here propagates consistently across incident, request, change, asset, and service-level management instead of being re-applied module by module.
Access is governed by role-based access control. Administrators build roles, attach permissions through permission matrices, and assign them to teams or individuals, so an agent, an approver, a tenant administrator, and an end user each see exactly the surface they should. Permissions resolve down to the record, field, and action level, which means the same data model can safely serve a help-desk technician resolving incidents and an external customer raising requests through the self-service portal. Service catalog visibility, approval authority, and reporting scope all inherit from these definitions.
Configuration management lets you tune platform behavior without code: business hours and calendars that feed SLA targets in Service Level Management, escalation and notification rules, form fields and category trees, and the assignment logic that workflows in Workflow Management rely on. Multi-company administration extends this to tenant boundaries — each company or business unit can carry its own branding, data partition, catalog, and policy set while the platform stays a single instance, working hand in hand with the Federation Engine that orchestrates cross-tenant operations.
Every administrative action is captured in an immutable audit log: who changed which setting, role, or permission, with the previous and new value and a timestamp. That record gives security and compliance teams a defensible trail for access reviews and change governance, and it ties back to Change Management so configuration changes follow the same controlled, traceable path as any other change to the service environment.
- Role-based access control
- Organization & tenant setup
- Configuration management
- Permission matrices
- Audit logging
- Multi-company administration
What you can do with it
Role-based access control
Define roles, bind them to permissions, and assign to users or teams so each person sees only the records, fields, and actions their role allows.
Permission matrices
Manage create, read, update, and delete rights per module, record type, and field from a single grid that resolves conflicts predictably.
Organization & tenant setup
Model companies, departments, sites, and groups, and partition each tenant's data, catalog, branding, and policies within one platform instance.
Platform configuration
Set business calendars, notification and escalation rules, category trees, and assignment logic that feed SLA, workflow, and request behavior.
Workflow & form governance
Control which workflows, forms, and approval chains are active per tenant and route their behavior without touching code.
Immutable audit logging
Capture every configuration, role, and permission change with actor, timestamp, and before-and-after values for review and rollback.
Why teams adopt it
One source of control
Manage access, structure, and configuration for all 29 modules from one panel instead of reconciling settings across disconnected tools.
Least-privilege by default
Granular roles and permission matrices keep sensitive data and high-impact actions limited to the people who genuinely need them.
Audit-ready governance
A complete, immutable change trail makes access reviews, security audits, and compliance reporting fast and defensible.
Multi-company scale
Onboard new companies or business units as isolated tenants without spinning up or maintaining separate platform instances.
Where it fits
Onboard a new company
Stand up a new tenant with its own catalog, branding, roles, and SLA calendars in the console, ready to operate alongside existing companies.
Quarterly access review
Use permission matrices and the audit log to confirm who holds which rights, revoke stale access, and produce evidence for auditors.
Restructure after a reorg
Update the organization tree, reassign teams, and rebind roles so queues, approvals, and reporting scope realign automatically across modules.
Tighten a privileged role
Adjust a role's permission matrix to remove a risky action, with the change recorded in the audit log and applied platform-wide instantly.
Common questions
Permissions resolve down to the module, record type, field, and individual action (create, read, update, delete). You build roles, attach them through permission matrices, and assign them to users or teams, so the same shared data model can serve internal agents, approvers, tenant admins, and external self-service users with distinct surfaces.
Related modules
See Admin Console in action.
Book a demo and we'll show admin console working alongside the rest of the platform — on one shared data model.