Planning a workspace upgrade

Account & Billing

3 min read

Updated Apr 12, 2026

An upgrade is easiest when you know why the workspace needs it. Higher token volume, enterprise identity requirements, and compliance expectations often move together, so planning should happen before the request is sent.

Before you begin

A reason the current plan is no longer enough

A rough volume forecast

Clarity on whether SSO, governance, or custom integration planning is also needed

Define the real need

Some upgrades are mainly about token volume, while others are really about governance, identity, or integration planning.

Knowing the driver helps the Signelio team recommend the right path.

Use billing and settings together

Review billing for capacity and pricing context, but also review security and compliance settings if the upgrade is tied to trust requirements.

That gives you a more complete request package.

Coordinate internal approval

If finance, operations, security, or IT all care about the change, align them before you contact the vendor team.

That prevents the request from stalling on missing internal decisions.

Pro Tips

Bundle volume, identity, and compliance needs into one discussion when possible.

Document the business reason for the upgrade before contacting support.

Review custom integration needs at the same time if downstream systems are involved.

Was this article helpful?

Use this as a quick signal while the public knowledge base is static.