Teams, workspaces, recovery, and data control

Dashloom treats a workspace as the isolation boundary for products, credentials, metrics, Agent runs, reports, channels, and members. A user can belong to several workspaces and switch the active workspace from Settings.

Roles

• Owner: workspace settings, administrators, members, credentials, export, and deletion.
• Admin: workspace settings, non-admin invitations and members, credentials, reports, and export.
• Member: products, analysis, reports, and report delivery.
• Viewer: read-only product intelligence.

An invitation is valid for seven days, stored as a SHA-256 token hash, bound to one normalized email address, and usable once. Dashloom displays the invitation URL once so self-hosters can deliver it through their preferred communication system.

Password recovery email relay

Dashloom uses Better Auth's one-hour reset tokens and revokes existing sessions after a successful reset. Configure a transactional email relay that accepts this JSON body:

Hosted operators can set AUTH_REQUIRE_EMAIL_VERIFICATION=true after configuring this relay. Verification links expire after one hour; sign-up and sign-in dispatch them without awaiting the mail provider. Community local development defaults the flag to false so a missing relay does not block setup.

{
  "event": "dashloom.auth.email",
  "to": "user@example.com",
  "subject": "Reset your Dashloom password",
  "text": "Use this one-time link…"
}

Set RESEND_API_KEY and RESEND_FROM_EMAIL to send invitations and authentication messages directly through Resend. Keep email verification disabled until the sender domain is verified and a real delivery/link test passes.

Export and deletion

Owners and administrators can download a versioned JSON export from Settings. Version 6 includes workspace data, Agent actions and their post-completion outcome cycles, Growth Missions, versioned Agent comparison history, and audit events but excludes API keys, OAuth tokens, connector credentials, and delivery secrets.

The same Settings page provides a Community-to-Cloud migration flow for portable Dashloom JSON exports. A server-side preview validates schema compatibility, references, file limits, destination plan capacity, and the number of products that will be created or matched without writing data. After approval, import is a merge operation scoped to the active workspace: products match by slug, metric identities are upserted, and competitor evidence is remapped to new local identifiers. Only products, product goals, normalized metric points, competitors, and competitor metric points are accepted. Credentials, users, roles, invitations, subscriptions, tokens, reports, Agent runs, actions, outcome cycles and comparison history, delivery channels, and audit history are stripped during validation and never imported.

Only the owner can delete a workspace, and the request must include the exact workspace slug. Deletion cascades through workspace-owned tables. Export first if the data may be needed later.

Audit trail

Workspace creation and updates, invitations, membership changes, and exports append audit events. Audit metadata must never contain secrets. The API returns the newest 200 events to owners and administrators.