Upgrade
Evaluate plan fit, handle feature gating, and execute upgrades safely.
Use this guide when a feature is gated by your current plan and you need to increase capability without disrupting active operations.
Upgrade objectives
These objectives define a successful upgrade process.
- Required capability is unlocked for the intended teams.
- Upgrade decisions are documented with owner and business reason.
- Post-upgrade workflows validate without regressions.
Upgrade workflow
Follow this sequence whenever you change plans.
Review which capability is blocked and why it is required.
Compare available plans against near-term operational needs.
Confirm plan change with billing owner approval.
Validate that gated workflows now execute successfully.
Decision criteria
Use these questions to avoid unnecessary plan churn.
- Is the blocked capability required now or later?
- Which team owns the capability after upgrade?
- What governance controls must be updated after change?
- Is there a rollback or alternative if outcomes are not acceptable?
Post-upgrade validation
You should verify both functionality and governance after each plan change.
Verify previously blocked screens, actions, and flows are now available and stable.
Verify roles, notifications, and runbooks still align with your new capability set.
Next steps
- Review access impact in Settings.
- Review subscription state in Admin subscriptions.
- Document outcomes in your team operating runbook.
Last updated on