Understand the three parts of a plan
Each application plan combines common Suite capabilities, limits specific to that service and its billing conditions. Two services on plans with the same name may therefore include different operational capacity. Always review the plan from the instance you want to change.
Read current usage
Open My applications and enter the instance details. The Plan usage area shows each resource with its description, used amount, included limit and remaining capacity.
- Unlimited: usage is measured, but the plan does not impose a numerical ceiling for that resource.
- Not included: the plan has a limit of zero and that function cannot create or activate records.
- Monthly: the counter restarts on the date shown in the period summary.
- Total: the counter reflects active or accumulated capacity and does not reset each month.
When you approach or reach a limit
The usage card changes its visual status as capacity is consumed. Reaching a limit never deletes information automatically. Depending on the service, new creation may be blocked or resources above the contracted capacity may remain suspended until you free capacity or move to a suitable plan.
Change plan safely
- Review every usage card, especially additional users and the main operational entities.
- Compare the service-specific limits shown in the available plans.
- If you upgrade, choose the payment method and confirm the new charge.
- If you downgrade, check the effective date and reduce usage beforehand when necessary.
Only the instance owner can change the plan, replace the payment method, cancel or reactivate the subscription. A pending downgrade is shown in subscription management and can be cancelled when the payment provider allows it.
Before confirming
- The target plan covers current usage and expected growth.
- The billing profile and payment method are valid.
- You understand whether the change is immediate or scheduled for the next period.
- Any active coupon and its remaining duration have been taken into account.
Tip: Use the real counters in the instance, not an estimate, before reducing a plan. This avoids unexpected operational restrictions after the change takes effect.