Use one account across authorized subsites

A single POM AI subscription can serve several sites at once. This page is about doing that deliberately: what it costs in domain capacity, how the shared balance behaves, and how to keep one site from spending what another needed.

It applies equally to several subsites of one multisite network and to several independent WordPress installations owned by the same person.

What sharing a key actually means

Saving the same key on several sites creates several authorized domains under one license. Each of those domains:

• consumes one slot from the plan's domain capacity;
• spends from the same account balance;
• appears separately in the account's authorized domain list and usage log.

There is no per-site allocation by default. The balance is a single pool, drawn down in whatever order the sites happen to work.

When this is the right model

Reuse one key when the same person or organisation owns the sites and the budget:

• an agency's own portfolio;
• a multisite network where every subsite belongs to the network owner;
• a brand running separate installations per market or per product line;
• a production site plus its staging copy.

Do not reuse a key across sites owned by different customers. Their usage would be billed to your account, your balance would be exposed to their workload, and your usage log would mix everyone together. In that situation each customer buys their own subscription and saves their own key.

Set it up

For each site that should share the subscription:

1. Open Settings → POM AI → License on that site.
2. Paste the same key.
3. Select Save and validate.
4. Confirm the Domain line shows that site's own host.

On a multisite network this must be done inside each subsite's administration; there is no network-wide way to grant AI to subsites. See Authorize one multisite subsite for AI services.

You can also authorize a domain from the account side before touching the site, which is useful when preparing several sites at once. See Authorize a domain to use POM AI.

Watch the capacity

Every host counts, including the ones people forget:

• www and non-www count as one, because the host is normalized for matching;
• a staging copy counts as a separate domain;
• a local or development copy counts too, when the plan allows it at all;
• a retired site keeps its slot until the domain is deactivated.

Check the current position in My Account → Licenses & Downloads, where the POM AI card shows a used-of-total domain count, or in My Account → POM AI Management, which lists the authorized domains for your POM AI subscription.

When the plan is full, the next activation is refused rather than silently replacing an existing one. Free a slot first — see Remove an authorized domain — or move to a plan with more capacity. Understand domain authorization limits explains how capacity is counted.

Control what each site can spend

The single most useful safeguard for a shared subscription is a per-domain limit.

In My Account → POM AI Management on account.pom.es, the Manage AI Domains card lists your authorized domains and lets you attach an optional spending limit to each one. Use it to stop a single site from consuming the entire balance — a site running a large bulk operation is the usual cause.

The same screen shows the usage log, with the domain, the tool, the endpoint and the credits used for each operation. Review it periodically; a domain you do not recognise in that list is worth investigating immediately.

Operational habits that make sharing work

• Give each site its own budget expectation even though the pool is shared, and set the limits to match.
• Run bulk operations on one site at a time. Bulk translation and bulk image metadata are the two operations most capable of draining a shared balance in one afternoon.
• Keep a list of which sites hold the key. When the time comes to rotate it, every one of them needs updating.
• Unlink retired sites promptly. A dead site holding a slot is invisible until you need the slot.
• Do not paste the key into shared documents or tickets. The more places it exists, the more likely a rotation becomes necessary.

Rotating a shared key

Rotation is where a shared key costs the most effort: the old key stops working immediately, on every site at once.

Before rotating, list every site holding it and plan to update them all in one session. The procedure is in Rotate a license key safely.

Verify the arrangement

• Each participating site shows a valid license and its own host on the Domain line.
• The account's authorized domain list contains exactly those hosts.
• The used-of-total domain count matches the number of sites you intended.
• Spending limits exist where you wanted them.
• One small AI operation succeeds on each site.