If Campaigns or Sites is locked, start by checking your plan rather than assuming your AI provider connection has failed. If your question is about an AI usage charge, distinguish that from your AIM subscription first. These are separate parts of the setup, and checking one does not establish the status of the others.
AIM Engine’s Billing & Access overview describes separate responsibilities for subscription payments, activation, feature access and customer-owned OpenAI usage. This guide turns those distinctions into a practical checklist for WordPress administrators and buyers evaluating how access works.
Why are Campaigns or Sites locked?
The supplied overview describes two plan-access states: on Beginner, Campaigns and Sites are visible but locked; on Advanced, both are unlocked. It also explicitly separates provider connection status from subscription status.
That distinction matters when troubleshooting. A connected provider account does not, by itself, establish access to a feature reserved for another plan. Equally, a subscription does not establish that a provider connection is ready for a particular task.
- If you use Beginner: locked Campaigns and Sites match the documented plan restrictions.
- If you use Advanced but see a lock: compare the displayed access with your subscription and activation information. The supplied overview does not identify a definitive cause or repair procedure for a mismatch.
- If you do not know your plan: establish that before changing provider settings or purchasing additional services.
The documented plan distinction is a useful starting point, not a complete diagnosis of every access problem.
Who handles the subscription and AI usage charges?
The overview separates the AIM payment relationship from charges for the customer’s provider usage:
| Area | Responsibility described in the overview | What to distinguish |
|---|---|---|
| AIM subscription | WooCommerce / WooPayments stores the subscription and handles the payment relationship on aim-engine.com. | This is the commercial access side of AIM. |
| OpenAI usage | The customer’s OpenAI account supplies model, image, speech and provider-storage services through WordPress Connectors. The provider bills the customer for usage. | Provider usage billing is separate from the AIM subscription. |
| Activation and entitlement | AIM Network Hub manages activation and entitlement. | These concern AIM access, not a shared OpenAI spending credential. |
| WordPress workspace | AIM Engine presents the workspace appropriate to the active plan on the customer’s WordPress site. | Visible features and provider readiness are separate questions. |
This division explains responsibilities, but it is not a price list or a complete description of payment processing. The supplied material does not establish current prices, refund terms, taxes or billing exceptions.
Use a four-part access checklist
Treat the following as separate checks, not a verified installation sequence. The source does not specify the required setup order.
1. Identify the blocked task
Write down what you are trying to do and what you can observe. “Campaigns is visible but locked” is more useful than “AI is broken.” Separate a locked workspace from a task that is available but cannot complete.
2. Confirm the plan and expected access
Compare your known plan with the documented Beginner and Advanced restrictions. In this context, entitlement means the access your plan permits. If the plan is unknown, record it as unknown rather than inferring it from a provider connection.
3. Check activation separately
The overview assigns activation to AIM Network Hub. It also states that AIM Network activation uses an AIM credential, not an OpenAI API key. Do not treat those credentials as interchangeable. Exact activation indicators and remediation steps are not established by the supplied excerpt.
4. Establish provider readiness without guessing
For a task that uses provider services, check what you actually know about the customer-owned provider connection. Record a confirmed status if available; otherwise use “unknown.” Subscription access alone is not evidence that the provider connection is ready.
Hypothetical example: connected provider, locked Campaigns
Suppose a WordPress administrator reports a connected OpenAI account but cannot open Campaigns. They confirm that their AIM plan is Beginner.
Under the documented access model, the locked Campaigns area is consistent with that plan. Replacing the provider key would not address the documented plan restriction. The useful next decision is whether the administrator needs the access described for Advanced, while checking current commercial terms separately.
This is an illustrative scenario, not a customer result. If the administrator instead reports Advanced access, the excerpt alone cannot explain the mismatch.
Prepare a support summary without sharing secrets
A practical support handoff can separate observations from assumptions. Include the blocked task, the reported plan, any known activation status, any known provider-connection status and the exact non-sensitive message displayed.
Leave out API keys, activation credentials, card details and unnecessary account data. Mark uncertain information explicitly. A concise description of the problem is more useful than a collection of credentials, and the source provides no reason to include secrets in a troubleshooting summary.
A proposed readiness checker—and its limits
A possible improvement would be a credential-free explainer asking for three self-reported inputs: plan, activation status and provider-connection status, each with an “unknown” option where appropriate. It could then explain which distinction to investigate next.
This is a proposal, not an existing capability established by the source. Its benefit would be a simpler explanation; its limitation would be reliance on the reader’s answers rather than live account verification. Any guidance would need confirmed access rules and support routes before use.
For now, the strongest next step is straightforward: identify the task, distinguish plan access from provider readiness, and keep AIM activation separate from OpenAI credentials. Those distinctions narrow the question without pretending to diagnose an account from incomplete information.

Add an example, conclusion or question.
Short, specific responses help AIM Community improve future articles and product decisions.