Review a plan change request

What this achieves

When a customer asks to move to a different plan from inside their own workspace, the request arrives here rather than changing anything. Approving it applies the plan; rejecting it tells them why.

Required role: Humavera platform staff.

Steps

Go to Platform → Plan Requests.
Stay on Pending, or select Approved, Rejected, or Cancelled to see decided ones.
Read the request: which plan the workspace is on, which they want, who asked, and when.
Select Approve to apply the change.
To decline, select Reject, enter the reason, and confirm.

The four lists

Option	Description
Pending	Waiting for a decision. This is the worklist.
Approved	Decided and applied, showing who decided and when.
Rejected	Declined, showing the reason recorded.
Cancelled	Withdrawn by the customer before anyone decided.

Why a request exists at all

Not every plan change goes through this queue. Moving up a tier is an immediate change the customer makes themselves. Moving down is a reduction in what they are entitled to, so it is submitted for review instead of being applied.

That is the point of the queue: a change that takes something away from a live workspace is a decision somebody makes, not an outcome that happens.

Example: HC Corp upgrading to reach a module they need does not appear here. HC Corp asking to move to a smaller plan does.

Your rejection reason is read by the requester

A rejection requires a note, and that note is sent to the person who asked. Write it for them rather than for the queue.

Example: “Your term runs to 31 March 2027; we can move you at renewal” tells an administrator what to do next. “Denied” leaves them with nothing but the outcome.

Approving changes a live workspace

Approval applies the plan to the customer’s environment there and then. Everything a plan change carries applies with it — modules and features follow the new plan, and included AI credits reset to the new plan’s monthly allowance while any top-up balance is preserved.

What happens next

The requester is notified of the decision either way. In their own workspace the pending request disappears from their subscription page, replaced by the new plan if you approved it. Where the request was for something that needs hand-set terms rather than a published plan, set up a negotiated agreement instead of approving.