Skip to main content
Seat-based products separate the person paying from the people using the product. A billing manager purchases capacity, assigns it to members, and each claimed seat receives its own benefit grants.

​
The three records involved

The purchaser becomes an owner. Owners and billing managers can administer seats and subscriptions. Product access belongs to the member grant, so your application should identify the person by member rather than by the customer that paid.

​
Subscription or perpetual access

​
Configure the offer

1

Create the product

Start a new product, then add its name, description, and media.
2

Choose the commercial model

Select subscription or one-time, choose the billing cycle for subscriptions, and set pricing to Seat-based.
3

Define the seat curve

Use a fixed price for one rate per seat. Use graduated tiers when each quantity range keeps its own rate. Use volume tiers when the total quantity selects one rate for every seat.
4

Attach member benefits

Add what each seat holder receives. Benefits are issued on claim, not merely when capacity is purchased.
For tiers of 1–10 seats at 10and11+at10 and 11+ at 8, fourteen graduated seats cost 10 × $10 + 4 × $8 = $132. Fourteen volume seats cost 14 × $8 = $112.
With Ruba’s default confirmation page, the purchaser’s seat is claimed automatically. A custom success_url skips that automatic claim; assign the purchaser through the portal or API if they also need product access.

​
Seat lifecycle

  • Pending means an invitation was sent but not claimed.
  • Claimed means the member has the benefits.
  • Revoked removes those benefits and makes the capacity assignable again.
Managers can assign by email, external customer ID, or Ruba customer ID; resend a pending invitation; revoke an assignment; and change subscription quantity. Invitation links remain valid for 24 hours.
Revoking an assignment does not lower the paid subscription quantity. To stop paying for unused capacity, reduce the seat count as a separate action.

​
Quantity changes and proration

Adding subscription seats creates an immediate prorated charge for the remainder of the current period, then bills the full quantity on the next cycle. Reducing quantity creates a prorated credit for the unused part of the period.

​
Current limits

  • Dashboard assignment is one seat at a time; use the API for bulk workflows.
  • A subscription supports at most 1,000 seats.
  • The billing manager does not receive product benefits solely because of that role.
  • Seat metadata supports 10 keys and 1 KB in total.
Continue with the API and webhook implementation in Build Seat-Based Pricing.