Start, Change, or Cancel a Subscription

Manage the organization subscription and verify entitlement, seat, interval, renewal, and cancellation outcomes.

Written By 4ALL.LIVE

Last updated 12 days ago

Manage the organization subscription and verify entitlement, seat, interval, renewal, and cancellation outcomes.

Best for: Organization owners, billing administrators, finance approvers, event producers, and authorized support staff.

Before you start

Commercial actions and protected billing data require the correct organization role. Current plan, enterprise assignment, add-ons, seats, wallet, usage, payment state, and desktop license inventory determine effective availability.

  • Confirm exact organization and authority.
  • Record current subscription, entitlement, wallet, usage, or device state.
  • Obtain required commercial approval before purchase, cancellation, payment, or license transfer.

Step by step

  1. Confirm authority. Owner/billing admin in exact organization.
  2. Review current state. Plan, interval, seats, add-ons, status, renewal/cancel date, payment.
  3. Choose action. Start, upgrade/downgrade, interval/seat change, or cancel.
  4. Review checkout/portal. Organization, line items, tax, currency, proration, effective date.
  5. Complete authorized action. Approved Stripe or enterprise path.
  6. Return to 4All. Allow webhook/sync reconciliation.
  7. Verify entitlements. Test a non-production workflow.
  8. Communicate impact. Operators, finance, renewal owner.
  9. Retain approval/invoice. Policy.

What success looks like: The approved commercial or license state is reflected in 4All and verified against the intended workflow.

Check your setup

  • Subscription state matches approval.
  • Entitlements/seats refresh.
  • Effective/cancel dates recorded.

Troubleshooting

Change not reflected

Refresh/sync and use safe organization/session IDs with support.

Payment failed

Resolve through portal/issuer/3DS.

Cancellation removes needed feature

Migrate/export/disable before effective date.

Security and operational notes

  • Requires explicit approval.
  • Verify organization before checkout.
  • Never share card or portal session data.

Documentation status: Draft for billing, legal, security, and operational review. Validate current prices, entitlements, and UI before publishing.