Empuls implements RBAC through a combination of predefined roles, custom roles, and centralised logging so that only authorised users can perform sensitive actions and every change is auditable.
RBAC model
- Follows need-to-know and least-privilege principles; access is granted based on role, not individual users.
- Uses role-based access control for critical systems; roles and the permissions attached to each are defined and documented (e.g., Super Admin, HR/Admin, Manager, Employee plus customer-specific custom roles).
- Access outside the default role matrix is requested via a formal process, justified, and approved before being granted; privileged rights are tightly controlled and reviewed periodically.
- Role changes and terminations trigger automatic adjustment or revocation of access so users never retain rights beyond their current job function.
Logging and change history
- All production and administrative access is logged to central logging systems to maintain user accountability and support incident investigation.
- Logs capture security-relevant events such as logins, failed attempts, role/permission changes, configuration changes, and data-access operations; irregularities are reviewed and acted on as part of Xoxoday’s access monitoring process.
- Access rights are reconciled at least annually, with findings from log reviews feeding into removal or adjustment of excess privileges.
Does Xoxoday Empuls support role-based access control?
Xoxoday Empuls enforces RBAC, restricting login to pre-identified users with permissions scoped strictly to their assigned role.
Does Empuls review user access when employees change roles?
Empuls runs a formal, documented access review process that removes unnecessary permissions whenever an employee changes roles, enforcing least…