Access & Entitlements - Fundamentals¶

What It Is (General)¶

Access & Entitlements covers two related concepts:

Access Control (User Permissions): Who can see and do what within the platform. Includes role-based access control (RBAC), entity-level visibility restrictions, and action permissions.
Feature Entitlements: What capabilities are available based on subscription tier or license. Enables commercial packaging (Basic vs Premium vs Enterprise tiers) and feature gating.

What It Means for Our ICP¶

How Treasury Teams Think About It¶

Regional enablement is the driver. Treasury teams with global operations want to empower regional finance contacts (APAC, Americas, EMEA) with cash visibility without overwhelming them or requiring extensive training. The goal is making regional teams "stakeholders in the process" rather than passive recipients of treasury instructions.

ON's Regional Structure (Source: 2026-02-04) - 3 regional treasury hubs: APAC (1 person), Americas (North America), EMEA - Regional contacts need visibility into their accounts/entities - Currently considering Palm access for ~3 regional users initially - Goal: Regional teams can "sit with lower buffers and request less" when they trust the data

Typical Requirements¶

Access Control: - Regional treasurers should only see their region's accounts - Read-only access for stakeholders vs edit access for operators - Audit trail of who did what

Feature Entitlements: - Different feature sets for different pricing tiers - Ability to upsell by unlocking features - Trial access to premium features

How They Talk About It¶

"Enable them" - Lucia (ON) after visiting APAC: "We need to enable them way more than we do"
"Stakeholders in the process" - Not just recipients of information, but active participants
"Treasury cash culture mindset" - Regional teams need to develop this; it's not natural
Contrast with Kyriba - "So many training sessions... every two weeks" vs Palm being "way more intuitive"

Sources: view all