---
title: Seat, usage, and feature access on managed Lago Cloud
description: A buyer example connecting seat charges, usage allowances, plan entitlements, enterprise overrides, and Stripe collection.
canonical: https://getlago.com/platform/entitlements
---

# Seats, usage, and feature access in one billing plan

Consider B2B software with a monthly seat subscription, an included number of API calls, and plan-based access to SSO and higher service limits. An enterprise customer negotiates more seats and a custom feature limit. This is an illustrative configuration, not a customer case study or a Lago price quote. Managed Lago Cloud operates billing; Stripe remains the payment processor. The application sends usage and checks access.

1. **Bill seats and usage together.** Configure the subscription fee or a fixed seat charge and an API-call billable metric on the same plan. Define the included quantity and the rate for excess calls. Record seat changes and API usage according to the chosen charge model, then preview a sample invoice. See [fixed charges](https://getlago.com/docs/guide/plans/charges/fixed-charges), [usage charges](https://getlago.com/docs/guide/plans/charges/usage-based-charges), and [invoice previews](https://getlago.com/docs/guide/invoicing/previews), which require a Premium license.
2. **Attach feature access to the plan.** Define a `seats` feature with an integer `max` privilege, plus features such as `sso`. Attach them to the plan with the values included in that tier. Lago's [entitlements guide](https://getlago.com/docs/guide/entitlements) documents the feature, plan, and subscription APIs with seat examples.
3. **Apply the negotiated enterprise terms.** Override the customer's subscription charges for its contracted seat price or included usage, and override that subscription's entitlement privileges for its custom seat or feature limits. The base plan and other subscribers do not change. Pricing overrides are [Premium](https://getlago.com/docs/guide/subscriptions/assign-plan); confirm the exact Lago Cloud quote and entitlement availability for the chosen edition.
4. **Let the product enforce access.** Fetch the subscription's entitlements, and update the application's local access state when Lago sends `subscription.updated`. The application checks the current feature and seat limit before accepting a user action. Lago supplies commercial state, not a synchronous request gate. See [retrieving entitlements and the webhook](https://getlago.com/docs/guide/entitlements).
5. **Invoice and collect.** Compare the invoice's seat and usage lines with known events and contract terms. Lago issues the invoice; Stripe processes payment through the [payment integration](https://getlago.com/docs/integrations/payments/stripe/payments). Confirm payment-method collection and failure recovery for the exact onboarding flow.

## Evaluate the joined-up workflow

- Start with two customers on the same plan. Override one customer's rate and entitlement limit; confirm the other customer's invoice and access remain unchanged.
- Change the number of seats mid-cycle and compare the resulting charge with the contract's proration rule.
- Send usage below and above the allowance. Check both the rated invoice and the product's access behavior.
- Simulate a subscription change and a failed payment. Define how the application updates access when a webhook is delayed or retried.
- Confirm which Premium features, payment integration, support terms, and Cloud price apply to the contract. [Public pricing](https://getlago.com/pricing) does not quote this scenario.