Workspace Guide
A workspace is your studio's private environment inside Lomio — it owns all projects, characters, assets, and billing.
What is a workspace?
Lomio uses a multi-tenant workspace model. Every piece of content — every project, episode, character, generation task, and video asset — lives inside a workspace. Workspaces are fully isolated: members of one workspace cannot see or access another workspace's data unless they are explicitly invited.
A workspace typically represents a single studio, production company, or creator brand. Large organizations sometimes create separate workspaces per content vertical or team.
Key properties of a workspace:
- Name & slug — the human-readable name and a URL-safe identifier (e.g.
my-studio). The slug is set at creation and cannot be changed. - Plan — the subscription plan that governs credit limits and feature access.
- Credit balance — a pool of credits shared across all members and all projects in the workspace.
- AI settings — default model preferences, safety configurations, and generation parameters inherited by all projects.
Creating a workspace
- From the workspace selector (top-left dropdown in the studio), click Create new workspace.
- Enter a workspace name and slug. The slug must be unique across Lomio and can only contain lowercase letters, numbers, and hyphens.
- Choose a billing plan. You can start on the free Starter plan and upgrade later. See the Billing FAQ for plan details.
- Click Create Workspace. You are now the Owner.
Members and roles
Every workspace has a team of members. Each member is assigned a role that controls what they can see and do.
| Role | Description | Key permissions |
|---|---|---|
| Owner | The workspace creator or a promoted admin. Only one Owner per workspace. | Full control: billing, member management, workspace deletion, all content. |
| Admin | Trusted team leaders who manage people and settings. | Invite/remove members, configure workspace settings, access all projects and generations. Cannot delete the workspace or change billing plan. |
| Editor | Core production team members. | Create and edit projects, episodes, characters, and generation tasks. Cannot manage members or billing. |
| Viewer | Stakeholders who need read access — clients, executives, reviewers. | Read-only access to projects and generated content. Cannot create, edit, or trigger generation. |
Inviting members
- Go to Workspace Settings → Members.
- Click Invite Member and enter the invitee's Google email address.
- Select the role (Admin, Editor, or Viewer) and click Send Invite.
- The invitee receives an email. When they sign in to Lomio with that Google account, they will see your workspace in their workspace selector.
Changing or removing a member
In Workspace Settings → Members, click the ⋮ menu next to any member to change their role or remove them. Removing a member immediately revokes their access; any in-progress generation tasks they triggered continue running (credits are charged to the workspace, not the individual member).
Transferring ownership
To transfer the Owner role, promote an existing Admin to Owner via the member menu. The previous Owner is automatically downgraded to Admin. Only one Owner exists at a time.
Switching workspaces
If you are a member of multiple workspaces, click the workspace name in the top-left of the studio. A dropdown lists all workspaces you belong to — click any to switch. The studio reloads with that workspace's context.
Workspace settings
Workspace Settings (accessible to Owners and Admins) includes the following sections:
- General — workspace name, description, and logo.
- Members — invite, remove, and manage roles.
- Billing — plan, credit balance, payment method, and invoices. See Billing FAQ.
- AI Settings — default generation model, safety level, and output language.
- API Keys — generate workspace-scoped API keys for integrations.
- Danger Zone — delete the workspace (irreversible; all data is permanently removed).
Workspace isolation and data security
Lomio enforces strict workspace isolation at the database level using row-level security (RLS) policies. Every API request is validated to ensure the authenticated user is a member of the workspace they are accessing. Cross-workspace data access is architecturally impossible — even workspace Owners cannot see other workspaces' data.