Subscription Access, Scope, and Usage

Premium access is evaluated for the active scope and feature. A kingdom plan, alliance plan, allocation, grant, and personal assignment are not interchangeable.

Resolve the effective feature

1. Confirm the active kingdom and alliance.
2. Open the effective plan or current feature summary.
3. Check that the named feature is enabled, not merely included in a plan available elsewhere.
4. Review its usage period and remaining allowance when shown.
5. Reload the protected page after a recent request or grant becomes accepted.

Usage and quota

Usage warnings can appear before a limit is reached. Quota exceeded blocks the relevant new premium action until the visible reset or plan change. It does not make previously saved imports, analytics records, profiles, or articles vanish. Free or browser-key alternatives may remain available for processing when their cards are enabled.

Expiry and suspension

Expired, revoked, or suspended access can relabel tabs as premium, hide a protected action, or show a locked state. Existing data remains governed by ordinary access and retention. Restoring a plan re-enables only the features in the current effective plan; it does not guarantee that an old unfinished job restarts.

Grants and analytics sharing

A kingdom subscription grant can enable features for an alliance. Analytics-only sharing can expose granted aggregates without granting edit access or the complete subscription feature set. Check the specific feature summary rather than treating all grants as equivalent.

Subscription access and usage landmarks

Use the current feature summary, not a plan name alone.

• Active scope and direct, allocated, or granted plan source.
• Enabled and locked feature list with effective dates when shown.
• Used, remaining, limit, reset, warning, or quota-exceeded feedback.
• Accept grant, request change, or contact support route available to the current role.

Related: Feature Availability and Analytics Sharing.

Purpose, controls, roles, and worked decision

The page explains effective feature access and current usage for the selected alliance or kingdom. Visible controls can include request, grant acceptance, allocation, and permitted cleanup according to role. Resolution checks direct alliance plan, accepted grant, kingdom plan, Free, feature eligibility, quota, limited mode, and suspension. Example: An accepted grant provides processing, but the alliance allocation is exhausted. Reading and supported cleanup remain; another upload is blocked. Increasing allocation or cleanup can recover usage, while acceptance alone cannot add quota or management rights. Report scope, source label, grant status, resource, allocation, usage, operation, and message.