- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2 hours ago - edited 2 hours ago
FSO Disputes Roles and Personas
Objective
FSO Disputes is a multi-persona product. Each persona maps to one or more ServiceNow roles that control access to workspace views, queues, playbook activities, and reports. Aligning your RBAC configuration to these personas before building playbooks and record producers is a foundational implementation step, as persona requirements directly shape configuration choices. This article covers every persona involved in the dispute lifecycle, the roles that enable their access, and the key configuration notes every implementer should know.
FSO Disputes Personas and Role Assignments
The table below maps each FSO Disputes persona to its ServiceNow role, primary responsibilities, and main working surface.
| Persona | ServiceNow Role | Key Responsibilities | Primary Surface |
|---|---|---|---|
| Dispute Agent | sn_bom_credit_card.dispute_agent | Primary case worker. Initiates, investigates, and resolves disputes; submits network messages; issues provisional credit. | FSO Workspace, Transaction Playbook |
| Dispute Agent Connector | sn_bom_credit_card.dispute_agent_connector | Same responsibilities as Dispute Agent. Must be combined with a CSM industry data model role, as connector-only assignments will cause access errors. | FSO Workspace |
| Dispute Manager | sn_bom_credit_card.dispute_manager | Queue and SLA owner. Monitors breach risk, approves escalations. Approves mandatory 4-eyes policy tasks at Manual Investigation and Review Representment stages. | Dispute Manager Workspace, Dashboards |
| Admin | sn_bom_credit_card.admin | Full access. Configures content packs, plugins, assignment rules, email templates, Card Data Security, integration spokes. | All FSO and platform admin modules |
| Customer / Cardholder | sn_customerservice.customer or .consumer | Dispute initiator via Customer or Consumer Service Portal. Uploads evidence, signs WSUD for ACH disputes, tracks status via dispute tracker. | Customer / Consumer Portal |
| Contributor (CSR / Branch) | Contributor persona (CSM) | Assisted intake. Opens disputes on behalf of customers via FSO Workspace. Case routes to Review stage for agent validation before investigation. | FSO Workspace, Guided Decisions |
| Card Data Security Admin | sn_data_sec.admin | Manages Tokenizer Resource Configuration table and admin privileges for Card Data Security. | Card Operations, Card Data Security |
| Card Data Security Flow Executor | sn_data_sec.flow_executor | Allows execution of all Card Data Security subflows. Includes script_include_admin, web_service_admin, sn_data_sec.admin, and connection_admin roles. | Integration Hub, Workflow Studio |
Key Configuration Notes
- Dispute Agent Connector role must always be paired with a CSM industry data model role. Connector-role-only assignments result in missing data access and errors during intake, a common implementation oversight.
- Contributor vs. Agent intake: when a customer or contributor submits via portal or workspace, the case routes to a Review stage before investigation. When an agent creates the case directly, Review is skipped. This distinction affects playbook design and SLA start calculation.
- 4-Eyes Policy: the platform enforces a maker-checker approval at two points: Manual Investigation and Review Representment. Dispute managers must hold the sn_bom_credit_card.dispute_manager role to action these approval tasks.
What's Next
Continue learning about FSO Disputes with these related resources:
- Financial Services Card Operations, Installed Roles reference (ServiceNow Docs) — full list of roles, descriptions, and contained roles.
- For customer-facing dispute intake configuration, see FS Portals.
- For CSR-assisted intake via Record Producer, see Streamlining Case Intake with Record Producer.
- For the data objects these roles interact with, see FSO Disputes Data Model and Core Data Objects.
- For a full overview of the FSO Disputes module, see Getting Started with FSO Disputes.
Have questions or implementation notes to share? Post them in the FSO Community Forum and help the community grow.
