> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getruba.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Sell Access by Team Seat
> Let one billing owner buy and assign access to multiple people
export const RubaSocials = () => {
if (typeof document === "undefined") {
return null;
}
const inject = () => {
const footer = document.getElementById("footer");
if (!footer || document.getElementById("ruba-socials")) {
return false;
}
const isDark = document.querySelector("html.dark") || document.querySelector('html[class*="dark"]');
const lineColor = isDark ? "#383838" : "#e8e8ed";
const iconColor = isDark ? "#8e8e93" : "#86868b";
const markColor = isDark ? "#ffffff" : "#08080c";
const hoverColor = "#0071e3";
const div = document.createElement("div");
div.id = "ruba-socials";
div.style.cssText = `display:flex;align-items:center;gap:20px;padding-top:20px;margin-top:20px;border-top:1px solid ${lineColor};width:100%`;
const logo = `Ruba`;
const spacer = ``;
const ig = ``;
const li = ``;
const x = ``;
const github = ``;
div.innerHTML = logo + spacer + ig + li + x + github;
footer.appendChild(div);
return true;
};
if (!document.documentElement.dataset.rubaSocialsObserver) {
document.documentElement.dataset.rubaSocialsObserver = "true";
const observer = new MutationObserver(() => {
if (!document.getElementById("ruba-socials")) {
inject();
}
});
observer.observe(document.body, {
childList: true,
subtree: true
});
}
setTimeout(() => {
if (!inject()) {
const interval = setInterval(() => {
if (inject()) {
clearInterval(interval);
}
}, 500);
setTimeout(() => clearInterval(interval), 10000);
}
}, 300);
return null;
};
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
| Record | Role in the model |
| ---------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Customer** | Owns payment methods, orders, and subscriptions. Its first seat purchase permanently changes its type to `team`. |
| **Member** | Represents an individual user. Members have an email and one of `owner`, `billing_manager`, or `member` roles. |
| **CustomerSeat** | Connects one member to one product and records `pending`, `claimed`, or `revoked` status plus its invitation token. |
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
| Decision | Subscription seats | One-time seats |
| ---------------- | ------------------------------------- | ------------------------- |
| Payment | Monthly or yearly | Single charge |
| Access lifetime | While the subscription remains active | Does not expire |
| More capacity | Change subscription quantity | Buy another order |
| Benefit lifetime | Active subscription period | After the seat is claimed |
## Configure the offer
Start a [new product](https://getruba.com/to/dashboard/products/new), then add its name, description, and media.
Select subscription or one-time, choose the billing cycle for subscriptions, and set pricing to **Seat-based**.
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.
Add what each seat holder receives. Benefits are issued on claim, not merely when capacity is purchased.
For tiers of 1–10 seats at $10 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](/guides/seat-based-pricing).