Xoxoday builds new loyalty management features directly into its backend engine, making them accessible through existing interfaces or as standalone modules—configurable via API or admin panel without interrupting current workflows.
How Xoxoday handles new feature rollouts
Xoxoday architects new capabilities at the engine level, meaning the underlying logic is embedded into the platform before it surfaces in any interface. This approach ensures that new features inherit existing data models, permission structures, and reporting pipelines from day one rather than operating as isolated additions. When a new capability becomes available, Xoxoday exposes it in one of two ways depending on the use case. Features that extend existing workflows—such as adding a new reward category to an active points program—appear within the current admin interface without requiring navigation changes. Features that introduce genuinely distinct functionality, such as a new gamification module or a referral-based loyalty engine, can be surfaced as a separate section in the system menu, keeping the admin experience organized and role-appropriate.Flexible configuration through the admin panel
Xoxoday administrators control how new modules appear and which user roles can access them directly through the admin panel. There is no dependency on vendor-side deployment cycles for configuration changes. An IT administrator can enable a newly provisioned module, assign it to specific business units, and restrict visibility to relevant personas—all without filing a support ticket or waiting for a release window. This matters in environments where HR and IT operate distinct workflows. For example, when Xoxoday is connected to Darwinbox or SAP SuccessFactors, the admin panel allows teams to activate a new milestone-based recognition module for the HR team while keeping the existing performance rewards interface unchanged for managers. Both coexist in the same tenant with no conflict.API-driven integration for enterprise environments
For organizations that manage system menus and feature access through their own infrastructure, Xoxoday exposes new capabilities via its REST APIs. Teams running Workday, SAP SuccessFactors, or custom enterprise portals can pull Xoxoday feature data into their own navigation structures rather than relying on the native Xoxoday menu. Notifications for new module activity can simultaneously surface in Slack or Microsoft Teams through the existing integration layer. This means a company can adopt a new Xoxoday feature within its existing intranet experience rather than asking employees to learn a new navigation path. The API contracts for new modules follow the same authentication and authorization standards as existing endpoints, so no changes to token management or security policy are required.Workflow continuity by design
Xoxoday treats backward compatibility as a prerequisite, not an afterthought. Existing configurations, reward rules, and approval workflows remain active when new features are introduced. Administrators receive in-panel notifications about new capabilities but are never forced to adopt them on a vendor-defined schedule. This gives organizations the flexibility to expand their loyalty programs at a pace that fits their internal change management processes. Learn more: Xoxoday Help Centre — Technical requirementHow Xoxoday APIs connect to HR and HRMS platforms
Understand how Xoxoday’s REST APIs integrate with Workday, SAP SuccessFactors, and Darwinbox to sync loyalty data across enterprise systems.
Admin panel access controls and role permissions
Learn how Xoxoday administrators manage module visibility, user roles, and feature access through the admin panel.