Billing & plans
Your subscription, seat count, and renewal cadence are managed from Settings → Plan. Payments run through Razorpay; only the company owner can change plans or seats.
Plans control how many users (`maxUsers`), projects (`maxProjects`), and features (e.g., social publishing, dataspaces) your company can use.
Step-by-step
- 1View current plan
Settings → Plan. See active plan, billing cycle (monthly/yearly), next renewal date, and seat usage.
- 2Change plans
Click Change plan. Pick a new plan from the list. For Free → Paid transitions, Razorpay checkout opens for the first payment; the system mirrors the new seats and features immediately on success.
- 3Add seats mid-cycle
Increase the seat count from the plan card. Razorpay updates the subscription quantity now; the prorated charge appears as a discount on your next invoice (no immediate card hit).
- 4Cancel a subscription
Click Cancel subscription. You keep access until the current cycle ends (`expiryDate`); the nightly cron downgrades to Free after.
- 5Contact sales for Enterprise
Enterprise plans don't run through self-serve checkout. Click the plan → Contact sales to open a mailto draft to sales@.
Tips
Adding a teammate when seats are full is blocked at the API layer — bump seats first. Failed payments are treated as transient (Razorpay retries); subscription.halted is terminal and triggers an immediate downgrade. All billing events show up in the company's Action log so you can audit who changed what and when.
Admin configuration
Only the company owner can change plans or seats — even admins are 401'd from these endpoints. The shared system Free plan is canonical; it's assigned on register and used as fallback when a paid subscription expires. Plan flags (like `allowSocialPublishing`) are configured by the super-admin in `/admin/plans`, not here.