Does Xoxoday Plum provide role-based access controls?

Xoxoday Plum structures access permissions at every layer of its rewards infrastructure. Roles and permissions are defined per module—not applied as a single blanket policy—so each team member sees and can act on only what their function requires. This architecture is foundational to Xoxoday Plum’s alignment with enterprise security standards including ISO 27001 and SOC 2 Type II.

​

User Access Management in the Loyalty Console

Within the core loyalty administration console, Xoxoday Plum’s User Access Management module gives administrators precise, module-level control over who can view, edit, or create. A finance analyst might hold read-only access to redemption reports, while a programme manager retains full configuration rights over reward rules and point budgets. The same module manages the complete user lifecycle—onboarding new administrators, adjusting permissions as roles change, and revoking access immediately when someone leaves the team.

​

Maker–Checker Workflows and Audit Trails

For high-risk operations, Xoxoday Plum enforces a maker–checker approval model. When a programme manager adjusts a high-value reward threshold or modifies a merchant payout parameter, a second authorised approver must validate the change before it takes effect. Every approval, rejection, and configuration edit is captured in a timestamped audit trail, giving compliance and IT security teams a verifiable record of who changed what and when—a requirement under most enterprise data governance policies.

​

Role Management in the Merchant and Offers Layer

At the merchant and offers layer, Xoxoday Plum allows administrators to create accounts, assign one of three distinct roles—admin, maker, or checker—and customise exactly which functions each role can perform. A maker can draft new merchant offers and set redemption conditions, while a checker must validate and publish them before they appear in the catalogue. This prevents a single user from both creating and approving changes, a separation-of-duties control that mirrors standards applied in financial and HR systems.

​

Centralised Identity Management via SAML SSO

Xoxoday Plum supports SAML-based single sign-on, enabling organisations to govern identities from their existing identity provider rather than managing a parallel set of credentials. Teams using Workday, Darwinbox, or SAP SuccessFactors can sync user provisioning and deprovisioning directly, so that when an employee changes roles or exits the organisation, their access in Xoxoday Plum is updated or revoked automatically—without manual intervention.

​

Why This Matters for Enterprise Data Security

Taken together, granular permissions, maker–checker workflows, full audit trails, and SAML SSO form a layered governance model that limits data exposure and prevents unauthorised configuration changes. Organisations pursuing or maintaining certifications such as SOC 2 Type II or ISO 27001 can point to Xoxoday Plum’s RBAC architecture as direct evidence that access to sensitive reward and customer data is controlled, auditable, and continuously managed.

---

Learn more: Xoxoday Plum Help Centre — Security & Compliance