How to activate your license

Documentation
, , ,
1

How to activate your license

This guide explains license activation end to end, including limits, plan feature validation, deactivation, and migration between sites.

Required access: Customer account with at least one license.

When to activate a license

Activate a license when you are preparing a new site or moving an existing install to another environment.

Pre-activation checks

Before activation:

  1. Verify target site is connected and online.
  2. Verify activation capacity remains on the license.
  3. Verify target product tier is available in your plan.
  4. Confirm this environment should consume an activation (staging vs production).

How to activate

  1. Open Licenses in your dashboard.
  2. Select the license to use.
  3. Choose a connected site and confirm activation.
  4. Wait for activation state to update.
  5. Verify activation counters and feature badges.
  6. Run one test install to validate effective access.

How to deactivate or move an activation

Use this process when replacing a site:

  1. Open Licenses and locate the active site entry.
  2. Deactivate the old site.
  3. Confirm activation capacity is released.
  4. Activate the replacement site.
  5. Re-verify product install access on the new site.

What happens after activation

  • The site is counted against your activation limit.
  • Plan features become available according to your license.
  • You can deactivate old sites to free capacity.

Troubleshooting

If activation fails, verify the site is connected and that your license has available activations.

Related guides

  • How to manage connected websites
  • How sublicenses work

Exact route paths

  • /dashboard/licenses
  • /dashboard/sites

Expected UI state after each step

  • Step 1: Selected license details panel opens.
  • Step 2: Activation action is enabled for a connected site.
  • Step 3: Activation counter updates after confirmation.
  • Step 4: Product access reflects license entitlements.

Screenshot map (step-level)

  1. License overview and counters

  2. Site linkage context

Operational objective

Complete the “How to activate your license” workflow with predictable outcomes, clear auditability, and repeatable execution quality across team members and projects.

Acceptance criteria (all must pass)

  • The workflow can be completed without missing permissions or blocked route access.
  • All required dashboard routes load successfully for the active account.
  • The expected UI states are visible in the same order as documented.
  • At least one end-to-end validation confirms the process works in practice.
  • Evidence artifacts are captured for support and audit handoff.

Routes that must be reachable during validation:

  • /dashboard/licenses
  • /dashboard/sites

Failure modes and exact remediation

  • Permission failure: Recheck plan/license entitlements and retry after session refresh.
  • Route loads but action is missing: Confirm feature flags/plan gates and selected context (site/license).
  • Action runs but state does not update: Refresh, re-open the relevant page, and verify from history/log view.
  • Partial success in multi-step operations: Retry only failed sub-steps and preserve successful state.
  • Cross-page mismatch: Reconcile with dashboard history and capture timestamps before escalation.
  • Persistent failure after one controlled retry: Open support ticket with full evidence package.

Evidence package for support escalation

Collect all items before escalating:

  • Account email and user role
  • Affected route path and exact action taken
  • Site URL, product/license identifier (if relevant)
  • Timestamps for first failure and latest retry
  • Expected result vs actual result
  • Screenshot set listed below

Screenshot evidence checklist

  • Step 1: License overview and counters
  • Step 2: Site linkage context
  • One screenshot with visible timestamp (system clock/browser tab)
  • One screenshot showing route context or breadcrumb
  • One screenshot showing final persisted result
  • Replace any generic placeholder/demo visuals with real environment captures

FAQ

Can I skip steps if I already know this workflow?

Skip only after all acceptance criteria still pass. If any criterion fails, run the full sequence exactly as documented.

Should I run this in production first?

Use staging first for medium/high-impact changes. Promote to production only after validation evidence is complete.

What if my screen does not match the guide exactly?

UI can vary by plan and feature access. Validate route access, plan gates, and expected state outcomes instead of pixel-perfect layout.

How many retries should I perform before escalation?

Run one controlled retry after checklist validation. If failure persists, escalate with full evidence to avoid hidden side effects.

Who owns this guide operationally?

Support Engineering owns this guide and its periodic review cycle.

Guide metadata

  • Difficulty: Beginner
  • Estimated completion time: 10-15 minutes
  • Owner: Support Engineering
  • Last reviewed: 2026-03-18