Xoxoday Plum restricts full partnership and offer catalogue access to authorized solution provider administrators through role-based access controls, while client organizations access only the approved subset of offers and reporting views defined by agreed governance.
Access to the full partnership and offer catalogue in Xoxoday Plum follows a strict, layered permission model. The complete catalogue — every partner, every offer, and every configuration detail — resides exclusively within the solution provider’s administration environment. Only users with authorized administrator credentials and the appropriate role assignments can view or manage it.
This design enforces the principle of least privilege across every layer of the platform. Xoxoday Plum uses role-based access controls (RBAC) to ensure that an administrator provisioned within the solution provider’s environment can browse the entire catalogue, configure active offers, set redemption rules, and manage partner relationships — while users outside that environment access only what has been explicitly approved for them.
Client-side administrators — for example, those managing a rewards program through an HR system like SAP SuccessFactors, Workday, or Darwinbox — interact with a governed view of the catalogue. They see the offers scoped and approved for their organization, alongside the reporting and analytics views aligned to their agreed governance model. They do not have visibility into the full commercial partner list, unpublished offers, or provider-level configuration settings.
For organizations where employees redeem rewards through an integrated channel such as Microsoft Teams or Slack, the same access boundaries apply. Employees browsing and redeeming through a Teams tab or Slack bot only ever interact with the curated, approved catalogue — never the underlying provider-level inventory.
This access separation also supports compliance readiness. Xoxoday Plum’s RBAC architecture aligns with audit requirements under frameworks such as ISO 27001 and SOC 2 Type II. Every access event is logged, role assignments are tracked, and any change to catalogue visibility requires authorized approval within the provider’s admin console.
The result is a clean, controlled experience for client organizations, while commercial partner relationships and the full catalogue breadth remain confidential to the solution provider.
Learn more: Xoxoday Plum Help Centre — General
Role-Based Access Controls in Xoxoday Plum
Understand how Xoxoday Plum uses RBAC to control who can view, configure, and manage catalogues, offers, and reporting across the platform.
Configuring Approved Offer Catalogues for Client Organizations
Learn how solution provider admins define and publish the approved subset of offers that client organization users can browse and redeem.