Social Terminal administrator guide

Start with the terminal page

Open Cointacted → Settings after activation. Confirm the Terminal page and route, choose the terminal appearance, and decide whether the terminal should fit the viewport or use its own resizable shell. Add the page to WordPress navigation when visitors should be able to discover it. Direct loading and in-site navigation should both show the welcome sequence and one focused command input.

Social Terminal is the command host. It owns command normalization, help, history, transcript behavior, visibility checks, dispatch guards, and the browser terminal. Add-ons contribute commands through its registry; they do not replace the host.

Configure access deliberately

Review every enabled command before exposing the terminal publicly. A command may be public, signed-in, role-restricted, capability-restricted, or administrator-only. The terminal checks access both when listing commands and when dispatching them. Hiding a command in help is not a security boundary; the server handler must still enforce access.

If abuse protection is required, configure the supported Turnstile constants documented in the Settings screen and keep the secret outside page markup. Test signed-out, signed-in, and administrator sessions separately.

Use the terminal

• Run help to open the command catalog.
• Run help search TERM to find commands by name or description.
• Select a command to view syntax, examples, access requirements, and its contributing add-on.
• Use transcript controls to clear the visible session when needed. Clearing the browser transcript does not delete data owned by another add-on.

Wallet, AI, search, gamification, community, shortcode, and blockchain commands appear only when their owning packages register successfully.

Manage add-ons and access

Open Cointacted → Add-ons to inspect installed versions, dependencies, Free/Pro status, and signed updates. Free local features need no account or license. Connecting a Cointacted account or entering a license is a deliberate administrator action used for protected access and delivery. Manual keys and connected-account access are independent sources and can coexist.

Before updating, verify the product name, target version, package slug, and active state. The updater verifies signed release metadata and package integrity, replaces only the expected plugin, and restores its previous activation state.

Troubleshooting

• Terminal page reloads: confirm the current SnapWeb adapter is active and the Terminal page uses the registered document route.
• Welcome message is missing: clear page/cache optimization, reload directly, then test in-site navigation. The mount must initialize after the destination document is committed.
• Wallet appears connected unexpectedly: disconnect the browser wallet and clear only the provider session. Social Terminal must not invent a PHP-side wallet session.
• Command is absent: check that its add-on is active, dependencies are available, and the current user meets its visibility policy.
• Add-on update is absent: use Refresh products, confirm authority access, then check the product card for a precise signature, entitlement, dependency, or package error.

Data and external requests

Free terminal use is local. Public pages do not contact the licensing authority. A deliberate connection, license action, protected installation, or update may send the site URL, random installation ID, WordPress environment, requested product, and submitted credential to Cointacted. Credentials are encrypted at rest. Never paste license keys into support logs.

Continue with the documentation for each installed add-on; its guide is authoritative for its own commands and stored data.