LingoSealLingoSeal Docs

Getting started

LingoSeal manages translations across multiple languages with your team. This guide walks you through creating a workspace, adding a project, importing existing strings, and shipping your first translations.

1. Create your workspace

A workspace is the top-level container for your projects, members, and billing. After signing up and verifying your email, the onboarding wizard prompts you to name your workspace and pick a URL slug.

  • The slug becomes part of your URL: /w/<slug>.
  • You can rename the workspace later from settings.
  • The slug is permanent once chosen.

2. Invite your team

Workspaces support four member roles. Owners and admins can manage everyone; members can use the workspace; billing-only members see invoices but nothing else.

  • Owner — full control including workspace deletion.
  • Admin — manage members, projects, settings.
  • Member — create projects, edit translations they have access to.
  • Billing — invoices and payment method only.

Send invitations in bulk from the onboarding wizard or from Workspace settings → Team. Recipients without an account sign up first; their workspace membership is auto-claimed on first sign-in.

3. Create your first project

Inside a workspace, projects hold the keys and translations for a single product or surface (e.g. Marketing site, iOS app). Each project has:

  • A base language — the source of truth your keys are written in.
  • One or more target languages — what you'll translate into.

4. Import existing strings

You can import from JSON (flat or nested), CSV, XLIFF, or QT TS files. Drag a file into the upload dialog; we'll show a diff preview before committing anything. Common workflows:

  • One-off import — drop a single file, confirm the diff.
  • CI-driven sync — use the CLI to push and pull from GitHub Actions.
  • Figma plugin — pull copy directly from designs.

5. Publish

Drafts stay editable until you publish. Publishing copies the current draft value into published_value — what the public API returns. Translations have a parallel review + approval workflow; a project owner can require both flags before a value gets published.

Where to go from here

  • CLI reference — push/pull from your codebase.
  • FAQ — common questions about limits, security, and billing.