Empuls restricts app configuration to client administrators across four defined role levels—Super Admin, General Admin, Manager, and User—while end users have no ability to modify platform settings or the interface.
How Empuls app configuration works
Empuls follows a centralized, admin-controlled configuration model. All settings are managed through a dedicated platform configurations section in the Empuls back-end, accessible only to client administrators. End users cannot change settings, adjust permissions, or modify the interface in any way. This design gives organizations consistent, predictable control over how Empuls behaves across their entire workforce, regardless of headcount or geographic distribution.Four role levels, clear boundaries
Empuls organizes access through four structured user access levels. Super Admins hold the highest level of control and can manage all platform-wide settings, including integrations, organizational structure, and billing. General Admins configure day-to-day features such as recognition programs, reward catalogs, and communication preferences. Managers have scoped access to oversee their direct teams—approving recognitions, tracking engagement, and viewing team-level reports. Users (employees) interact with Empuls to send recognitions, redeem rewards, and participate in surveys, but cannot access any configuration options. This tiered model ensures sensitive settings remain under IT and HR control while giving employees the streamlined experience Empuls is built to deliver.Central configuration, not end-user driven
Because Empuls does not support end-user configuration, organizations deploying at scale can rely on a single administrative setup. A Super Admin can define recognition rules, point values, and approval workflows once, and those settings apply uniformly across all teams and locations. When integrating Empuls with Slack or Microsoft Teams, for example, a Super Admin configures the connection from the Empuls back-end. Employees then receive recognition notifications and interact with Empuls directly inside their existing Slack workspace or Teams channel—no setup required on their end.EMM and MDM deployments
Empuls does not natively integrate with Enterprise Mobility Management tools such as Jamf or Microsoft Intune for application configuration delivery. Configuration is managed through the Empuls administrative back-end rather than via configuration files or the AppConfig standard. For organizations using EMM or MDM tooling, device-level policies are handled through those tools as usual, while application-level configuration is managed separately by Empuls administrators through the Empuls interface.Who should own Empuls configuration?
Client organizations typically assign Super Admin rights to IT administrators or senior HR operations personnel. General Admin access is appropriate for HR Business Partners managing specific programs. This keeps configuration intentional, auditable, and aligned with how enterprise platforms like Workday and SAP SuccessFactors handle role-based access control. Empuls maintains audit logs of all configuration changes, supporting compliance with standards including ISO 27001 and SOC 2 Type II. Learn more: Empuls Help Centre — Client IntegrationRole-based access control in Empuls
Understand how Super Admin, General Admin, Manager, and User roles map to platform permissions and what each level can configure.
Connecting Empuls to Slack and MS Teams
Step-by-step guide for administrators setting up the Slack and Microsoft Teams integrations from the Empuls back-end.