Entitlement model (plans + features)
Entitlement is plan-driven: a subscription grants a set of features. Auth handles WHO the user is; Payments handles WHAT they can access. Do not gate features via auth roles, gate via payments.hasFeature.
Where to enable it
Toggle this feature in your project editor. No code required.
This capability runs platform-wide; no specific settings route.
Open in my projectRelated features
Subscription plans (Free, Pro, Enterprise, ...)
Define subscription plans (plan_id, name, price, interval) in Payments. Use the AI tool definePlans, or edit the plan catalog directly. Required before generating any code that references plan_ids, call getPlans first so plan_ids stay consistent.
Feature catalog & entitlements
Define feature_keys (e.g. unlimited_uploads, advanced_analytics) and assign them to plans with per-plan limits. Code calls payments.hasFeature(key) to gate UI/logic. Always call getFeatures before generating gating code so feature_keys stay consistent.
User roles & custom claims
Define roles (admin, customer, driver, etc.) and assign them to end-users. Roles are available to your app code as claims on the auth session. Configure in Auth → Roles.