Workspace invitations

Email invitations are available when your installation administrator enables them. Workspace Owners and Admins open Members and invitations, enter an exact email address and select a role. An invitation expires after 24 hours. A pending invitation reserves a possible seat; the page shows active members and reserved seats separately.

Open the invitation email, sign in with your intended Kanva account, then choose Send verification code. Every sign-in method needs this separate mailbox check. Enter the eight-digit code, review the workspace and role, and choose Join workspace or Decline. An Owner role also requires accepting ownership responsibilities. After a full sign-in redirect or page reload, reopen the original invitation email.

Joining does not require owning a workspace or starting a trial. Use Open workspace when you are ready to switch. Your personal paid features remain independent. Viewer can read workspace-visible resources but cannot run training or predictions. Private resources stay private until their owner shares them. An invitation for an existing active member preserves their current role.

Email queued means Kanva has recorded the mail request. Accepted by mail provider; delivery unconfirmed is not a promise of inbox delivery. Check spam filtering or ask the administrator to inspect the invitation's status. Retrying email keeps the original invitation and expiry. Expired or revoked invitations need a fresh approval.

If a request times out, use Retry original request or Check original operation. Do not create a replacement while the original result is unresolved. Reload recovery retains a safe operation reference, without storing your recipient address, link or code.

Use Revoke invitation to withdraw pending approval. Accepted access is managed in the Members tab, through role changes and Remove workspace access. Removing, leaving or suspending a membership prevents older invitations from restoring it; a new approval is required to rejoin. The final Owner cannot be removed through invitation controls.

Invitation APIs use authenticated browser sessions with Origin/CSRF protection. API keys and integration agents cannot create or accept invitations. Never place invitation credentials or verification codes in API URLs, logs or scripts intended for sharing.