New — the Tender Checklist Workbench is live: review tenders with page-cited answers. See it →
← All products

Tenant settings

Your team, your apps, your control

Tenant settings is a self-service console for your company's administrator. Add or remove the people on your team, then decide which RapidCloud apps and features they can use. Manage your subscriptions and tiers in one place, and see exactly what each user can access. No support ticket, no RapidCloud staff in the loop.

Stop filing tickets to manage your own team.

Tenant settings is the admin home for your company on RapidCloud. From one clean console you add and remove users, grant the apps and features each person needs, and manage your subscriptions and tiers — all yourself, all instantly.

Need to onboard a new hire before lunch? Done. Tightening access for a departing teammate? One click. Upgrading a plan to unlock another app for the team? It’s right there next to everything else.

Every action stays inside your tenant, takes effect the moment you save, and gives you a live picture of who can reach what. Less waiting, more running your business.

Open Tenant settings and take control of your team today →

Under the hood▾

Tenant settings is the customer-facing surface over RapidCloud’s entitlements model. The platform defines applications, each exposing fine-grained features. Access is resolved through layered grants: a tenant grant sets the baseline an organization is entitled to, and user grants (including per-feature override grants) refine it per person. Effective access is computed server-side via resolve_user_entitlements, so the console always reflects what each user can actually reach — and which grant won.

Apps carry subscription tiers: tier-locked features stay dimmed until the matching plan is active, with Stripe-backed checkout and management handled by rc-billing. Tenant settings reads and writes only within the admin’s own tenant — there is no cross-tenant visibility.

The whole surface is JWT-gated: a portal-issued system JWT authorizes every /api/* call, with company_admin role required for write operations. Entitlement changes propagate to the user’s next token resolution, so grants take effect without a re-provisioning step.