Skip to content

Access & Entitlements

Overview

Access & Entitlements encompasses user permissions (who can see/do what) and feature entitlements (what capabilities are available based on tier/license). For enterprise treasury teams, this includes role-based access control for multi-user deployments and feature gating for commercial tiers.

The primary driver is regional enablement: global treasury teams want to share visibility with regional finance contacts without requiring extensive training or exposing irrelevant data.

For detailed ICP context and terminology, see fundamentals.md

Top Jobs & Desired Outcomes

Full history: jobs.md

1. Enable regional finance teams to access treasury data with appropriate permissions ⚡

Desired Outcomes: - Minimize training burden when onboarding regional users - Enable entity-level access restrictions so users see only relevant data - Reduce dependency on central treasury team for basic cash visibility

Source: ON (Emerging - needs corroboration)

2. Collaborate across global treasury organization without over-centralization ⚡

Desired Outcomes: - Minimize the "nudging" required to get regional teams to act - Increase stakeholder buy-in by giving regional teams ownership

Source: ON (Emerging - needs corroboration)

Key Pain Points

Full history: pain-points.md

  • Kyriba requires extensive, ongoing training - "Every two weeks... a morning walk to teach them how to use Kyriba" (Source: ON)
  • Regional teams don't adopt complex tools - Contrast with Palm being "way more intuitive" (Source: ON)
  • Central treasury bottleneck - Team has to constantly nudge regional contacts (Source: ON)
  • No entity-level permissions - Users either see everything or nothing (Source: ON)

Key Opportunities

  • Palm's intuitive UI is a differentiator - ON explicitly contrasted Palm favorably vs Kyriba for regional user adoption
  • Scheduled PDF reports as stepping stone - Even without full access control, scheduled reports can enable regional visibility
  • 3-hub pilot opportunity - ON has just 3 regional contacts to start (APAC, Americas, EMEA)

Open Questions

  • [ ] What permission granularity do enterprise treasury teams actually need? (entity-level, account-level, report-level)
  • [ ] How do other treasury tools handle role-based access for multi-entity setups?
  • [ ] Is entitlement/feature gating a real concern for our ICP, or mainly a commercial/packaging question?

Last updated: 2026-02-04 | Sources: 1 transcript (view all)