Skip to main content

Hub Connection

Hub Connection​

Last verified: 2026-07-13

Awthy Hub is the HaakCo-operated account utility that connects paid WordPress installs to account-bound managed services such as Google Drive audit export and managed reporting. Hub can also broker geo database downloads without requiring the store owner to sign in.

Claim flow​

The normal flow is:

  1. Sign in to Hub with the site owner or license manager email.
  2. Choose the expected account, license, and site.
  3. Copy the short claim code.
  4. Paste it into Awthy Security -> Settings -> Hub connection in WordPress.
  5. Confirm WordPress shows the connected state.

Claim codes are short-lived and one-time use. Do not send claim codes, install secrets, cookies, Google tokens, Custd credentials, or raw Hub payloads to support.

Reclaim and reinstall​

A same-account reinstall should be able to reclaim the install relationship when ownership matches. A different-account claim conflict requires support review before transfer. Support should verify account and license ownership without asking for secrets.

Account and license ownership​

Hub account ownership, license ownership, install activation, and managed-service provisioning are Hub-side concerns. The plugin should show only the connected state and safe next steps.

If a license has reached its activation limit, decide which install should remain active before trying to claim another site.

Managed Google Drive​

Google Drive export uses Hub as the managed OAuth broker. Store owners should not create their own Google OAuth clients for Awthy's managed path. See Google Drive audit export.

Managed reporting​

Managed reporting can send approved Awthy telemetry and evidence summaries through provisioned credentials when the entitlement and feature setting are active. It must not silently stream secrets, raw file contents, raw customer data, raw order data, or browser journey data.

The Hub Reporting tab is account-scoped. It supports preset and custom ranges; Custd query filters for store, event, outcome, severity, stream, and flow; managed-report drill-down; and paginated, sortable stores. Display-safe text search filters connected-store host/status rows and their corresponding CSV/JSON rows only; it does not change summary totals or managed report details. The current view persists in the URL, but the URL is not an authorization token: another account receives no rows or provider detail. See Audit and consented funnel reporting for result-state meanings and privacy boundaries.

If a report is partial, stale, or truncated, keep using the visible rows with the displayed qualification. Narrow a truncated query, check the WordPress connection for stale data, and do not interpret missing rows as proof of no activity. If reporting is unavailable, retry once. Then confirm that WordPress still shows Hub connected and managed reporting ready; reconnect only when WordPress reports an expired, missing, or conflicted connection.

Reconnect behavior​

Reconnect when WordPress shows an expired, missing, or conflicted Hub connection. Generate a fresh claim code and repeat the claim flow. If WordPress reports a conflict, stop and follow support ownership review instead of retrying with borrowed accounts.

For support, provide the account email, site host, selected range and filters, visible result state, timestamp, and non-secret error text. Remove claim codes, cookies, tokens, credentials, raw exports, customer/order details, and provider payloads from screenshots. A signed-out response or another account seeing rows is an authorization incident; stop and report it through the security channel rather than reconnecting repeatedly.

Last updated on