License Status and Expiry

Read the ContextQA Dashboard entitlement indicator and respond safely when a self-hosted or time-limited license approaches expiry.

Who is this for? IT administrators and engineering managers responsible for keeping a ContextQA deployment licensed and available.

The ContextQA Dashboard can display the current entitlement state alongside the workspace test inventory and activity metrics.

ContextQA workspace dashboard showing web, API, and mobile test inventory together with AI and human activity trends

Reading the indicator

The observed demo workspace displays an Active entitlement with the remaining time shown in minutes. Other deployments may show a date, a different time unit, a renewal warning, or subscription-specific wording.

Use the displayed state as an operational signal:

Visible state	Recommended response
Active with ample remaining time	Record the owner and renewal date in the organization's normal vendor-management process
Active with limited time remaining	Contact the ContextQA account owner, confirm the renewal plan, and schedule a verification after the updated entitlement is applied
Warning or expired state	Capture the non-sensitive status text, notify the service owner, and avoid configuration changes that could complicate recovery

Do not publish fixed warning thresholds unless they have been confirmed for the target deployment. Countdown units, banners, grace periods, and post-expiry behavior can depend on licensing and deployment configuration.

Renewal runbook

1. Identify the ContextQA organization and deployment owner.
2. Record the visible entitlement state and remaining time without including user data, API keys, or secrets.
3. Contact the ContextQA account team or ContextQA support with the organization details.
4. Agree on a maintenance and rollback window when applying a self-hosted license update.
5. After renewal, sign in and confirm the indicator returns to the expected active state.
6. Run a small, non-destructive test and confirm that scheduled automation still operates.
7. Retain the approval and verification evidence according to the organization's process.

Business value

• Avoid release disruption: Assigning an owner and renewal lead time keeps test gates available during critical delivery windows.
• Reduce incident ambiguity: A short verification run separates entitlement problems from unrelated execution failures.
• Support governance: Preserving the approval, visible state, and post-renewal check creates a clear operational record.

Related pages

• Administration Overview
• System Configuration
• Roles & Permissions
• Authentication and SSO