Empuls publishes its Android client under the app ID com.xoxoday.teams and requests only optional device permissions — camera and storage — when a user actively chooses to upload images or attachments within the app.
Android App ID
The Empuls Android app is distributed under the package identifier com.xoxoday.teams. IT administrators and mobile device management (MDM) teams can use this ID to allowlist, deploy, or manage the app across corporate device fleets. The identifier remains consistent across Google Play Store updates, making it reliable for long-term MDM policy configuration.Permission Model
Empuls takes a minimal-permissions approach on Android. The app does not request permissions on install that are unrelated to its core functionality — recognizing colleagues, responding to surveys, redeeming rewards, and engaging with the social feed all work without any additional device access. Optional permissions are surfaced only when a user initiates an action that requires them. If an employee wants to upload a profile photo, attach an image to a recognition post, or include a file in a survey response, Android presents a prompt for camera or external storage access at that moment. Declining these prompts does not disable recognition, reward redemption, or any other primary workflow.How This Works in Practice
Consider a team running Empuls alongside MS Teams. When an employee opens Empuls on their Android device to send a peer recognition with an attached photo, Android presents a one-time permission prompt for camera or media access. If the employee declines, the text-based recognition still reaches the recipient and surfaces in the MS Teams channel where Empuls notifications are configured. No core feature is gated behind device permissions. The same pattern applies for organizations integrated with Slack or HRMS platforms such as Workday, SAP SuccessFactors, or Darwinbox — Empuls operates without elevated device access until the user explicitly triggers an upload flow.For IT and Security Teams
Empuls holds ISO 27001 and SOC 2 Type II certifications, and its Android permission model aligns with those standards. Permissions are declared in the app manifest only for functionalities users can voluntarily access — not for background data collection or device tracking. MDM profiles targeting com.xoxoday.teams can be configured to pre-approve or restrict optional permissions according to organizational policy. When deploying through an enterprise mobility management platform, IT teams can reference this app ID to enforce update policies, configure VPN exceptions, or apply data-loss prevention rules without disrupting the employee experience.Learn more: Empuls Help Centre — Client Integration
Empuls iOS App ID and Permissions
Learn the iOS bundle ID and how Empuls handles camera and notification permissions on Apple devices.
Deploying Empuls via MDM
Configure app allowlisting, VPN exceptions, and update policies for Empuls across managed Android and iOS fleets.