User Access Provisioning & Reporting 1. Please demonstrate and provide

1. User-role / group/privilege mapping

• Empuls uses role-based access control, where users are mapped to roles (e.g., Super Admin, HR Admin, Manager, Employee) and to org groups such as departments, locations, or custom segments.
• Each role is tied to a permission set (view, create, approve, configure), and those permissions are mapped to specific services/modules like rewards, budgets, surveys, analytics, billing, and admin settings.

​

2. Granularity of access control

• Access can be restricted at module, page, and action level – for example, “view surveys only”, “create rewards but not approve”, or “configure SSO but not billing”.
• Data access can also be scoped to “self”, “direct team”, “hierarchy”, or “entire organisation”, so a line manager only sees their team while HR/Compliance can see org-wide reports.

​

3. Defining different system administrators

• Empuls allows multiple admin roles with clearly separated responsibilities, for example, an HR Admin for user/org data and policies, an IT Admin for SSO/integrations, a Finance/Rewards Admin for budgets and catalog, and a Super Admin with full platform control.
• These roles can coexist in the same tenant, so your organisation can delegate administration to specialist teams without exposing full system-wide privileges.

​

4. Reporting on users and privileges

• Admins can generate reports that list all active users along with their roles, groups, managers, and status, and export this data for review or audit.
• Additional audit logs show key admin actions (role changes, access updates, configuration edits), giving your organisation a clear trail of who has which access and when it was granted or changed.

Learn more: Empuls Help Centre