Use Lami with confidence

Sign up with an email you control. Organizations group billing, members, and projects; invite collaborators once your workspace is stable.

If your organization requires admin approval for new members, wait for the approval email before expecting shared project access.

Every project row persists across onboarding and post-wizard work—there is no duplicate “workspace project.” The wizard captures references, palette intent, and structural cues.

You can leave and return: incomplete onboarding appears under continue-setup surfaces until the Theme reaches the complete state required for workspace entry.

Dashboard “active” lists and OpenDrive import targets only include projects that are active, finished onboarding, and have a completed Theme. Draft rows remain addressable for continue-setup flows.

This distinction prevents half-baked configurations from appearing where teams expect production-ready assets.

The workspace hosts canvas tools, background workflows, and Object Lab boards tied to the same project id. Media libraries deduplicate references so prompts stay short while intent stays rich.

Offline or flaky networks: some surfaces queue saves; watch the UI for retry states and avoid closing tabs mid-upload.

Generation calls route through Lami’s provider integrations. Streaming and model availability may differ per capability; admins see aggregate usage while members see project-scoped indicators.

Do not send regulated health, financial, or personally identifying client data through prompts unless your agreement explicitly permits it. When unsure, ask via Contact before processing.

For product questions, billing, or privacy requests, use the Contact form. Include reproduction steps and timestamps when reporting generation failures—our logs attach request identifiers that speed triage.

For security vulnerabilities, disclose responsibly through the same channel with “SECURITY” in the subject line.

Lami ships continuously behind feature flags. User-visible changes land when they are stable for production orgs; experimental toggles may preview earlier in controlled environments.

This document updates when customer-facing behavior changes; engineering epics in the repository are not contractual commitments.