Role-aware access
Separate requester, technician and administrative experiences according to authorised responsibilities.
SECURITY
Security belongs in the operating model.
SERVE is designed around clear access, controlled integrations and deployment choices that make responsibilities visible.
SERVE / SECURITYoperating model.
Separate requester, technician and administrative experiences according to authorised responsibilities.
Deployment choice
Controlled integrations
Platform administration
OVERVIEW
Know what is controlled, where it runs and who operates it.
The right security model depends on how SERVE is deployed and which integrations are enabled. Cloud and self-hosted customers have different operational boundaries, so implementation should document responsibilities, access and supported data flows rather than relying on vague claims.
Deployment choice
Choose hosted or self-hosted operating models according to organisational requirements.
Controlled integrations
Connect external services deliberately and document what each integration can access.
Platform administration
Keep configuration, workflow and knowledge-management responsibilities visible.
Operational monitoring
Managed platform options can include application-level monitoring and maintenance activities.
Implementation review
Scope security-relevant decisions during onboarding rather than after go-live.
OUTCOMES
What this part of SERVE is designed to improve.
01Make platform responsibility explicit
02Reduce uncontrolled integration sprawl
03Support different deployment requirements
04Keep access and administration role-aware
NEXT STEP