CFM User Seats and Governance
Updated
The Pricing & Packaging (P&P) initiative transforms how Sprinklr sells, provisions, and governs platform access. Instead of purchasing features module-by-module, customers now receive bundled, seat-based packages.
Seat-based packaging replaces modular feature sales (Core, Care, Lite, Add-ons).
Governance tied to seats – entitlements drive feature access and permissions.
Explicit mapping of permissions, DPs, and UI to seat types.
Entitlement-driven provisioning ensures users only see purchased functionality
Note: All new PNP changes are controlled through DPs.
Users are managed under a three‑tier framework consisting of:
L1 (Package)
L2 (Seat)
L3 (Add‑Ons, optional)
For CFM, the following seat configurations are valid. Users can select their Product Seat using these L1, L2, and L3 combinations:
Core → Enterprise → CFM Admin
Lite → Lite → CFM Admin
Lite → Lite → CFM Limited Access
Note: In order to provision a Lite Seat, it is mandatory for the customer to have an Enterprise Seat.
Business Use Case
Clarity in Feature Access: By adopting a seat‑based packaging model, each user is assigned the correct access level. As a result, employees only view the functionality their organization has licensed.
Control through Governance: By using a seat‑based packaging and permissions model, access rights are automatically aligned with purchased seats and add‑ons.
Confidence in Provisioning: By adopting a structured seat assignment flow, administrators can provision large numbers of users quickly and accurately.
With Clarity, entitlement‑driven visibility ensures admins and end users only see the features their organization has purchased, reducing confusion, lowering support tickets, and simplifying navigation. With Control, permissions are automatically aligned to purchased seats, allowing admins to manage governance confidently without manual checks, minimizing compliance risks and preventing unauthorized access. And with Confidence, a guided seat assignment flow enables quick provisioning of large teams with fewer errors, accelerating onboarding and ensuring users are productive from day one.
Prerequisites
It is generally available for new onboarding customers.
Setting Up
Assigning a seat to a user
Navigate to Platform packages and select Package, Seat and Add-On-Modules( Add-On Modules is optional).
Examples
Package(L1) can be Core, Seat(L2) can be Enterprise and Add-On Modules(L3) can be selected as CFM Admin.
Lite → Lite → CFM Admin
Lite → Lite → CFM Limited Access
Note: Seat will be autofilled if Package is selected as Lite.
Assign or create a role with the available permission based on seat selected for the user.
Seat entitlements are saved and synced automatically through the backend.
Note: When Lite is selected as L1, the L2 field is hidden from the UI. The system directly shows the L3 (Add-On) field with values like “CFM Admin” and “CFM Limited Access”. Admins can only select one L3 for Lite.
How to use it?
Seat Selection Rules
Admins will only see seat types enabled for the partner & will not be able to see all combinations
A user can only select a Core seat once. The Core option will not appear again when the admin selects "+ Package".
Core and Care seats can coexist for the same user.
If an L2 value supports Add-Ons (i.e., Enterprise), multiple L3 values can be selected.
Lite contains 4 L3s, but only one L3 can be selected, i.e., for CFM—CFM Admin & CFM Limited Access.
Admin can at most select two unique L1s: one Core and one Care.
Core/Care seat can’t be selected with Lite seat.
Admins can select multiple L3s for Enterprise, but only one L3 for Lite.
Role Creation
Visibility: Admins will only see permissions relating to the seat types enabled for the partner.
Role Creation: Roles can only be created with permissions aligned to the partner’s purchased L1/L2/L3 values.
Add-On Filtering: Admins can select multiple add-ons, but only those enabled for the partner will appear.
If no add-on filter is chosen, all permissions associated with both Enterprise and enabled add-ons are displayed.
If you've chosen just one add-on, like "CFM Limited Access," you'll only see permissions that apply to that specific add-on. The standard Enterprise permissions will be hidden from view.
To see the combined permissions for Enterprise and CFM Limited Access, ensure that both “Enterprise” and “CFM Limited Access” are chosen in the filter options.
Add-On Handling
Add-Ons are assignable only if the seat supports it (Enterprise or Lite).
Admins can select multiple Add-Ons for Enterprise, but only one for Lite.
Add-Ons expand permissions within the boundary of the seat type.
The testing process for this feature mirrors the logical flow of setup and usage. The workflow remains simple and intuitive, with inline validation seamlessly integrated into the “How It Works” steps.
Best Practices
Always start testing with a dedicated test user account to avoid conflicts with production users.
Use add-on filters proactively during validation to confirm visibility rules, especially when partners have multiple entitlements.
When assigning Lite seats, plan add-on usage carefully since only one add-on can be selected at a time.
Validate both positive and negative flows (e.g., allowed vs. restricted seat combinations) to ensure compliance with seat rules.
Keep documentation of partner seat entitlements handy to cross-check against what appears in the UI.