Editions and activation

Start in Community

Community includes one local Owner, agent enrollment, monitored logs/metrics, and alerts. No license key is needed.

Open Settings > Licensing & Edition to check the effective edition and capabilities. Community is a valid operating state.

Before you activate Business

• Where: LogForge in your browser; no host shell needed.
• Access: the local Owner and an authorized license administrator.
• Ready: a privately supplied key or matching offline package.

Business adds people, teams, delegated access, and paid-seat capacity. Website accounts manage purchases/license delivery; the local Owner activates the local installation. Keep the existing deployment and data.

Connected activation

1. Obtain the key privately through your authorized license administrator or LogForge account workflow.
2. Sign in to LogForge as Owner.
3. Open Settings > Licensing & Edition and its activation action.
4. If Online activation is available, enter License key and choose Activate license.
5. Return to Licensing & Edition and check verified Business access and the expected seat allowance.

Check the installation: a purchase receipt or submitted form does not prove activation.

Offline activation

Use Offline activation if no online form is offered. Otherwise expand Use offline activation.

1. Choose Download activation request. Save the short-lived JSON request privately; it belongs to this deployment and license revision.
2. Hand the request to your authorized license administrator through an approved private channel. Obtain their signed JSON package for that request/deployment.
3. Under License package, choose the returned file and select Activate offline license. Do not choose the request file or edit either file.
4. Wait for Offline license activated. Check Business and seat allowance on Settings > Licensing & Edition.
5. If needed, use Download activation report there and return it privately. A failed report handoff does not undo a successful import.

Check: Business is active without a hosted licensing connection from the LogForge server. Image access and other network needs remain separate.

Offline renewal/replacement needs a fresh matching package when requested; it does not refresh through the connected service. Owner uses no paid seat. Expansion depends on verified Business license and capacity. Continue with People & Access.

Keep license material private

Private material: exclude keys, activation files, passwords, and revealed screenshots from tickets and shared logs.

Bundled installation images do not choose the activation mode. Use the action offered by your supplied release and follow its verification/renewal advice.

When Business needs attention

Problem: activation is rejected or Business needs attention.

Why it matters: a submitted key/import does not establish Business access.

Next step:

• Read the explanation and next action on Licensing & Edition.
• For expired or mismatched requests, obtain a fresh request/package pair. Do not edit JSON.
• Have the Owner check license state, connectivity, and seat use.
• If unclear, keep the reason and audit/request ID for the license administrator; exclude the key.

Preserve local data and accounts. Do not reinstall or delete users to retry. See your first workload or Data and recovery.