# Account invitations from Hive Open [Hive operator console](https://hive.nodelift.app/operator), authenticate as its owner, then choose **Users → Invitations** in the upper action bar. This manages customer account invitations, separately from **Add a device** and its companion pairing QR. ## Invite a person 1. Enter the recipient's email address. 2. Choose member or developer access, the email language (English, Simplified Chinese or Italian), and a validity period. The interface offers 1, 9, 24, 48 and 72 hours, with **24 hours as the default**; the API accepts an integer from 1 to 72. 3. Select **Create and email invitation**. The committed invitation appears in history with an email queued state. The separate worker attempts delivery within approximately one minute while its timer is running. 4. The recipient opens the personal one-use link, creates an account, awaits operator approval, signs in and sets up their own Authenticator before enrolling devices in their personal cluster. An invitation never grants Hive owner or administrator access. Approval remains a separate operator decision. The invitation URL uses a private fragment on the fixed account origin. Neither email tracking pixels nor link rewriting is added. Opening the page alone does not consume the invitation: successful account creation does. Invalid, revoked, consumed or expired links fail closed. ## Validity and email delivery are different states | Invitation | Meaning | | --- | --- | | Active | Unconsumed, unrevoked and within its expiry | | Expired | The deadline has passed | | Revoked | The operator invalidated the link | | Accepted | The invitation has been consumed; historical CLI records may represent an older closed invitation | | Email state | Meaning | | --- | --- | | Manual | Legacy/offline command invitation; the application did not send an email | | Queued | Committed to the encrypted outbox; not yet submitted | | Sending | A bounded worker has claimed the message | | Accepted by email service | SMTP returned acceptance; inbox delivery is **not confirmed** | | Sending failed | Explicit SMTP rejection or an unusable payload; no automatic resend | | Outcome uncertain | The connection or worker ended without a conclusive receipt; no automatic retry | | Email cancelled | Unsent queued delivery was invalidated or expired | SMTP cannot establish inbox delivery, spam placement, message opening or reading. This implementation has no delivery-confirmation webhook and does not label SMTP acceptance as delivered. Mail accepted before a revocation cannot be recalled, but the link is invalid immediately. A send already in flight may still produce an acceptance receipt after revocation; history preserves both facts. **Revoke** invalidates an unused invitation immediately. It does not delete an existing account. **Send new invitation** is available for active or expired records: it revokes the old link and creates a new invitation with a fresh validity period. Accepted or revoked records cannot be resent through that action. Creating a new invitation for an email also invalidates its older unused invitations. Existing accounts cannot be invited again. History is paginated, 25 records per page. Loading earlier pages pauses automatic refresh to preserve the reading position; explicit Refresh returns to the newest page. Unknown creation dates on legacy records remain unrecorded. Existing cleanup removes invitation metadata seven days after expiry; this is not a permanent audit archive. ## Email configuration and current rollout boundary The selected production sender is **invites@nodelift.app**. The mailbox has been created and verified active in Hostinger. The live server still has no authenticated SMTP configuration, so external invitation delivery is **not enabled or qualified yet**. Hive shows this explicitly and disables creation while SMTP is unavailable; existing invitations can still be inspected and revoked. After creating the mailbox, use the private interactive setup on the NodeLift server: ```sh sudo python3 /opt/nodelift-platform-tools/configure-invitation-email.py \ --sender invites@nodelift.app --host smtp.hostinger.com ``` Enter the mailbox password only at the hidden terminal prompt, never in chat, command arguments, Git, browser diagnostics or email. The helper authenticates with verified TLS and sends SMTP NOOP, not a test invitation. It updates only the invitation variables in the existing root-owned private EnvironmentFile, restarts the account service and enables the outbox timer. A failed authentication leaves the configuration unchanged. Hostinger documents [authenticated SMTP over SSL on port 465](https://www.hostinger.com/support/1575756-how-to-get-email-account-configuration-details-for-hostinger-email/); its mailbox password is separate from the hosting login. The existing `NODELIFT_OTP_ENCRYPTION_KEY` must be present. The outbox derives a separate purpose-bound encryption key, stores only a token digest for redemption, and retains an encrypted sending payload until submission, cancellation or expiry. Delivery receipts never expose raw tokens or provider error text. | Environment variable | Purpose | | --- | --- | | `NODELIFT_INVITATION_EMAIL_ENABLED` | Explicit enable switch, `0` by default | | `NODELIFT_INVITATION_FROM` | Verified mailbox sender | | `NODELIFT_SMTP_HOST` | Authorized SMTP hostname | | `NODELIFT_SMTP_PORT` | 465 for SSL, or 587 for STARTTLS | | `NODELIFT_SMTP_SSL` | `1` for SSL; otherwise verified STARTTLS | | `NODELIFT_SMTP_USER` / `NODELIFT_SMTP_PASSWORD` | Private authenticated mailbox credentials | Install [the outbox service](https://github.com/sev7enITA/NodeLift/blob/main/docs/../web/platform-server/deploy/nodelift-invitation-mail.service) and [timer](https://github.com/sev7enITA/NodeLift/blob/main/docs/../web/platform-server/deploy/nodelift-invitation-mail.timer). The API remains loopback-only and never opens outbound SMTP. The separate worker runs as the existing restricted service user. Each row has an atomic claim; interrupted claims become uncertain rather than being resent. The API enforces per-operator and per-recipient limits. Request identities make lost-response retries idempotent. Password recovery remains the separate [operator-assisted recovery procedure](https://github.com/sev7enITA/NodeLift/blob/main/docs/PASSWORD_RECOVERY.md). Enabling invitation email does not automatically enable password-reset email or change MFA. ## API and authority The approved-admin account service exposes `GET /api/admin/invitations` and `POST /api/admin/invitations/{create,revoke,resend}`. It preserves Django session, role and CSRF checks. The Hive interface uses `GET /gate/api/users/invitations` and corresponding action paths behind owner-session, same-origin and CSRF checks. Its fixed private identity RPC does not accept a client-supplied principal, owner binding, SMTP host or sender. There is no public invitation-creation endpoint or email relay. An existing private bootstrap-code owner session remains an operator authority, like the rest of Hive. Authenticator-bound sessions additionally require their live principal. Workspace membership alone never grants access to these global administration routes. ## Verification Run the account service tests from `web/platform-server` using its configured test environment, then the shipped UI tests: ```sh python manage.py test portal python manage.py makemigrations --check --dry-run python manage.py check --deploy --fail-level WARNING node web/hive-gate/invitation-ui-tests.cjs PYTHONPATH=host python3 -m unittest discover -s host/tests -p test_invitation_routes.py python3 -m unittest discover -s scripts/tests -p test_invitation_email_setup.py ``` From the repository root, `scripts/check-invitation-smtp.py` is a separate isolated Linux qualification. It requires loopback port 465 and permission to bind it, creates a temporary database and private short-lived test CA, authenticates through real TLS/SMTP, captures three MIME messages locally and removes its temporary credentials. No message leaves loopback. Its [receipt](https://github.com/sev7enITA/NodeLift/blob/main/docs/evidence/account-invitations-2026-11-16/smtp-loopback.json) is not an external-delivery receipt. See [verification scope](https://github.com/sev7enITA/NodeLift/blob/main/docs/evidence/account-invitations-2026-11-16/README.md).