Activate Pro and manage updates

Install and activate Free first, then the matching Pro add-on. WordPress plugin activation loads the add-on. On a new installation, the first successful licence activation unlocks new Pro work for this site; uploading a Pro ZIP alone does not unlock it.

1. Open Logged.ai → Licence & updates. Check that the displayed site address is the site you intend to register.
2. Copy the licence key from your account. Read the disclosure, enter the key, tick the consent box and choose Activate Pro.
3. Check the result. Continue into reports, alerts or cases. Opening a workflow never enables an alert, schedule or response automatically.

If an earlier installation shows Preserved for this existing installation, choose Connect licence for updates to add an eligible licence. Its retained local access does not need a new activation merely to continue on the same site.

The supplied publisher configuration is ready to use; a normal installation does not need an edit to wp-config.php. Keep licence keys out of screenshots and support messages.

Activation uses WordPress HTTPS with outbound access to plugins.shop. It does not require Linux, a separate PHP command-line installation, curl.so or process/POSIX functions. The native Sodium extension is not required for activation: WordPress’s bundled compatibility library can protect the saved credential.

In-plugin ZIP installation also needs the PHP ZIP extension, writable private temporary storage outside public web roots, and normal direct WordPress permission to update plugin files. The update screen reports an unavailable requirement. Account ZIP downloads remain the alternative installation route; they do not bypass first licence activation.

Only the licence key, product identifier, operation and this site’s canonical home URL are sent for licence actions. Audit events, request evidence, visitor data and case contents are not sent. Viewing the licence page does not contact the service.

Separate features such as saved private exports or arbitrary webhook destinations have their own storage and delivery requirements. Check the relevant guide before enabling them.

After a successful first activation, the saved local grant keeps Pro available through expiry, temporary service outages and later remote invalid or revoked status. New activations, private downloads, updates and product support still require the appropriate commercial entitlement. Existing evidence remains subject to your normal permissions and retention choices.

Upgrading an existing installation: a Pro installation initialized before 0.1.8 retains local access on its current canonical site and environment. This continuity record is not proof of purchase, does not reserve a licence slot and never grants paid updates. You can connect a valid licence for paid updates and support. A verified existing same-site commercial connection also preserves its recorded activation.

Moving an installation to another address or service environment requires activation. Copies made before their first migration, or exact copies sharing the same address and identifiers, cannot be identified automatically. A failed update lookup does not remove an existing local grant.

For the current 1.2.1 release, use the matching packages and the replacement steps below.

1. Keep a current backup and the previous compatible pair. Follow the update and schema-recovery reference.
2. Open Pro updates, confirm use of this site’s saved connection and select Check Pro updates. A service offer lasts 15 minutes; a fresh lookup can require a five-minute cooldown.
3. Install the matching Free update first, then use WordPress’s Update now action for Pro. Complete both before resuming Pro work. Background automatic Pro installation is disabled.
4. Check the installed versions, System status, any saved schema-upgrade phase and one representative workflow. Do not uninstall as an update method.

Manual route: obtain the matching Free and Pro ZIPs from your account, then replace Free first and Pro second through WordPress. An already activated site retains its activation during an ordinary matching-file update.

The private updater checks the exact installed Free version, compatibility profile, supported schema, entitlement and offered package. Install matching Free 1.2.1 before attempting the Pro 1.2.1 update. An offer alone is not installation approval. If an update fails after WordPress has deactivated Pro, inspect the installed files and plugin state before retrying; keep Free active.

The uncommon actions are under Manage this site’s licence. Read their effects before confirming.

Release licence slot

Ask the service to release this site’s slot so it can be used elsewhere. New Pro work locks here only after the service confirms the release. If the request fails, the saved local activation remains.

Remove saved connection

Remove this site’s saved key and local activation immediately. New Pro work locks here, even if the service is offline. This makes no service request and does not free the account’s site slot.

When an earlier installation has no saved licence, the same local action is labelled Turn off preserved local access. It withdraws that retained access immediately; a later successful activation is needed to unlock new Pro work.

Neither action deletes existing evidence or stops Free collection. Both withdraw local activation or retained installation access: new imports, Pro processing, scheduled report generation and advanced-alert generation or delivery stop. Authorized existing records/downloads and available privacy, cancellation and disable controls remain accessible. Existing request rules and already installed response policies keep their scope and expiry; disconnection does not recall completed actions or delivered messages. Review saved and pending work before reactivation.

Uninstalling Pro also removes its saved credential, local activation and installation identity without releasing the remote slot. Reinstalling requires successful activation. Default uninstall retains investigation data and a nonpersonal withdrawal marker; explicit delete-all removes both. Use Release licence slot before uninstalling when you need to move the allowance. Updating by replacing plugin files preserves ordinary existing access.

Updating to 1.2.1: back up and check the matching pair on staging. Use WordPress Plugins → Add New Plugin → Upload Plugin → Replace current with uploaded. Replace Free first, then Pro in a separate upload; keep Free active and do not uninstall either plugin. Free-only sites replace only Free. Get Pro privately from your account. The corrected Pro update manifest identifies the exact matching Free 1.2.1 release; an update offer still needs the normal compatibility, entitlement and archive checks.