UX for operators and partners

1) Context and key differences

Operators work with risks, payments, compliance, content, promotions, support. Their UX goal is operational management and incident reduction.
Partners (affiliates) focus on traffic, offers, payments and LTV/ROI analytics. Their UX goal is transparency and growth.

General b2b-UX principles:

One role - one main script on the desktop.
Signals and statuses are more important than decorative graphics.
Any indicator is clickable to the original source (drill-down).
Audit trail by default; actions - reversible (undo/confirm).
A11y/i18n-by-default: keyboard, contrasts, local formats.

2) Roles and Rights (RBAC) - UX Framework

Basic operator roles: Admin, Compliance, Risk/Fraud, Payments, CRM/Bonuses, Content, Support, BI.
Partner roles: Partner Owner, Manager, Finance, Analyst.

UX patterns:

Partition visibility and CTA - by role.
Restricted actions are marked with a "key" and a reason hint ("Payments: Advanced role required").
Sensitive operations - double confirmation + journal.

3) Desks (operator)

3. 1 Platform Status Dashboard

SLA/SLO block: uptime, incidents, queues.
Financial unit: GGR/Net Gaming, deposits/withdrawals, TtW p95.
Risk/AML: alerts on fraud patterns, chargeback spikes.
Gaming activity: DAU/Concurrency, top providers, launch errors.

Actions: "Open incident," "Disable provider," "Enable technical work banner."

3. 2 Transactions and payments

Payment queue: status, ETA, limits, method source (same-method).
Mass actions: approve/hold/reject with cause.
Operation card: KYC level, geo, device fingerprint, anomalies.

3. 3 Risk/AML

Summary of rules, risk rate, related accounts/devices, 3rd factor (docking package).

Recipes for actions: "Put on hold for 24 hours," "Request extended KYC."

3. 4 Marketing and Bonuses

Stock Builder: Audience, Terms, Limits, Deadlines, Micro Copy Previews.
Budget and bite forecast simulator (abuse control).
AB slots, frequency constraints, change log.

4) Desktops (partner)

4. 1 Partner Overview

Traffic/quality: clicks, registrations, FTD, CR, D7/D30 retention.
Finance: RevShare/CPA, accruals/disbursements, inconsistencies.
Offers: active, in moderation, will expire soon.

4. 2 Tracking and links

Link generator: source/channel/creative, deeplink, auto-UTM, short link.
Geo/Language/Age Landing Match Check.

Validation: "Pixel installed," "Events received (signup/deposit)."

4. 3 Reports and uploads

Periods/groupings: by geo, by offer, by creative, by device.
Export to CSV/XLSX with filters/timezones saved.
Scheduled report subscriptions.

5) Information architecture

Main navigation: Operations, Games/Providers, Payments, Risk/AML, Bonuses, Partners, Reports, Settings.
Secondary level: lists → card → modal actions.
Search everywhere: by ID, email, transactions, ticket, device, partner.
Bread crumbs and a fixed filter panel.

6) Signals, statuses, alerts

Single scale: info → notice → warning → error → critical.

The color ≠ the only signal: icon/text/form.
Global alert bar for criticism, local inline prompts - next to the problem.
Timeouts and retrays: showing the reasons and solutions ("repeat in 2 minutes," "change provider").

Examples of microcopy:

"Output is held until KYC is complete. [Open checklist]"
"Offer expires in 24 hours. Renew?"

7) Reporting and Analytics

Drill-down from KPI to transaction/session/event.
Saved views for roles (Finance/CRM/Risk).
Partner attribution: last-click/first-deposit/linear - explicit choice.
Anomalies: automatic signals by deviations from baselines.

8) Partner Cabinet: Trust and Transparency

Fairness of calculations: formulas of commissions, deductions, corrections - "in two lines" with disclosure of details.
Payment terms: ETA and statuses, log by details.
Media Center: Tagged Creatives/Languages/Geo, Version and Date Updated.
Communication: built-in chat/tickets, response templates, SLAs by appeal.

9) Compliance and security (built into UX)

KYC/KYB checklists with progress and ETA; sensitive fields - masked.
Audit trail on all critical operations, export.
Consents and reasons for requests (cameras/geo/documents) - explicit.
Segregation of duties: One cannot create and approve a payment.

10) Availability and localization

Full keyboard, visible focus, AA contrast.
'aria-live'for alert/toast,' aria-describedby'in forms.
Numbers/currencies/dates in local formats, line length margin, RTL mode.
Tables: 'th '/' scope', sorting and read signatures.

11) Performance and reliability

Virtualize long tables (thousands of rows).
Skeletons instead of spinners; saving filters to a URL.
Autosave drafts (promotions, reports).
Fail-soft: partial degradation of functions with clear explanations.

12) Incidents and SLAs

Incident Screen: Status, Impact, Affected Providers/Methods, ETA, Responsible, Timeline, List of Associated Tickets.
Communication: banner/fluff/letter templates with segmentation (operators/partners).
After the incident: post-mortem, actions and key dates.

13) Key screen templates

13. 1 Payouts (operator)

Filters: method, amount, geo, status, risk.
Table (rows are clickable): ID, user, amount, method, status, ETA, risk tag.
Right details: history, KYC, logs, secondary actions.
Mass transactions: checkboxes + confirmation with reason.

Microcopy:

"Payment queued. ETA - up to 15 minutes. Commission is not withheld"

13. 2 Partner Profile

KPI-top: FTD, CR, retention, commission.
Tabs: Offers, Links, Creatives, Payouts, Reports, Documents.

Quick actions: "Create a link," "Request payment," "Open a ticket."

13. 3 Designer of the offer

Audience → Terms → Conditions Creatives → Budget/Limits → Preview → Publication.
Micro copy preview (short version + disclosure).
A/B slot and frequency constraints.

14) Quality metrics for b2b-UX

Time-to-Action (to the desired action from the dashboard).
Error rate in forms (payments/offers), Time-to-Fix.
SLA compliance (payments/incidents), alert response time.
Partner metrics: CR, FTD, retention, payment delay, share of disputed accruals.
NPS/CSAT of operator and partner teams.

15) Checklists

Pre-release screen

One key goal for the role.
Loading/empty/error/success states are covered.
Actions are reversible or confirmed.
Focus, contrasts, 'aria-' in order.
Localization: lengths, currencies, dates, timezones.

Report/Table

Filters are saved, export with current filters.
Totals/amounts match (drill-down) details.
50k + line stability (virtualization).

Partner Cabinet

Transparent pay formulas.
Link/pixel validation.
Report subscriptions and alerts.

16) Anti-patterns

"All for all" on one dashboard.
Hidden reasons for restrictions ("cannot" without "why").
Color as the only status carrier.
Export that does not match the interface (other filters/timezones).
Modals without focus trap and focus return.
Unexplained changes in payments/fees.

17) Fast microcopy templates

Restriction by role

"The action is available to the Payments: Advanced role. Contact your administrator"

Fees/disbursements

"The payment has been created. We expect enrollment up to 15 minutes. [View Status]"

Affiliate link

"The link is active. Tracking: OK. UTM added automatically"

Incident

"Provider X is unstable. Games are not available for some EU users. ETA - 30 minutes. [Learn more"

18) Implementation process (6 steps)

1. Audit roles/tasks → screen matrix and CTA.
2. Dashboard MVP for Operator/Partner with KPIs and actions.
3. A set of critical forms (payments, offers, risks) with inline validation.
4. Uniform status tokens and alert/toast components.
5. Reporting and export with saving filters/timezones.
6. Incidents and communications: templates, SLA, post-mortem.

Final cheat sheet

Make desktops by role, not "universal."

Statuses and actions are always there, with a clear "why" and "what's next."

Reports - End-to-End - KPI → Transaction, Export = Screen

Partners - transparency of settlements and stable payments.
A11y/i18n is the default. Incidents - with clear communication and SLA.

It is necessary - I will prepare screen frames (operations/payments/risk/partners), i18n keys and metric tables for your design system.