Change a workspace's plan

What this achieves

A workspace’s plan decides which modules and features its people can open and how many AI credits arrive each cycle. Changing it here changes a live customer environment, and it takes effect at once rather than at their next renewal.

Required role: Humavera platform staff.

Before you start

Know which plan the agreement is for, and read what a change resets before you make one. The dialog states it, and it is repeated below.

Steps

Go to Platform → Tenants and open the workspace.
Open the Subscription tab.
Select Change plan.
Choose the Target plan. The panel shows its Seats, AI credits, and Modules.
Select Change to the plan you chose.
To vary one thing rather than the whole plan, use Feature overrides or Limit overrides further down, then select Save overrides.

What a plan change resets

Option	Description
Modules, features, and limits	Replaced with the new plan’s. A module the old plan included and the new one does not becomes unavailable to that customer.
Included AI credits	Reset to the new plan’s monthly allotment, not carried over.
Top-up credits	Preserved. Credits bought separately survive a plan change.

Example: moving HC Corp from one plan to another gives them the new plan’s monthly credit allowance from that moment, and any top-up balance they had bought is still there on top of it.

Overriding one thing instead of changing the plan

Where the agreement differs from the plan in a single respect, override that one thing and leave the plan alone.

Option	Description
Module access	Read-only here. Modules follow the plan, so use Change plan to alter them.
Feature overrides	Force one feature on or off for this workspace only. Each shows its Plan default and is marked overridden once it differs. Use default clears the override.
Limit overrides	Max employees (override) and Monthly AI credits (override). Leave a box blank to clear that override.
Capability overrides	Compose individual capabilities on top of the package. Dependency-validated, so a capability cannot be added without its prerequisites.

Effective entitlements at the bottom of the tab is the readout that matters. It shows what the workspace actually has once the plan and every override are resolved together.

Example: a workspace on a mid-tier plan that has negotiated one extra capability gets that capability added as an override. Their plan, and everything else it carries, is untouched.

When each change lands

Option	Description
A plan change	Immediately.
A feature override	Immediately on Save overrides.
An employee-limit override	Immediately on Save overrides.
A monthly AI credit override	At the workspace’s next monthly credit reset, not on save.

This is a live customer environment

Everything on this tab reaches a workspace that people are working in. Removing a feature or a capability takes it away from them while they are using it, with no warning from the platform side and no scheduling.

Where a change reduces what a customer has, make sure it is the agreed change and that they know it is coming. A plan change is reversible, but the working hour in between is not.

What happens next

The customer sees the result in their own subscription page, where their plan, their modules, and their credit position are shown. A module their new plan does not include reads as locked to them, with their plan named as the reason.