Core concepts

Localisync separates your account from the teams and projects you can access.

The same Localisync L symbol identifies the panel, documentation, account screens and account/team emails. Email actions and readable sender text remain available when images are blocked.

Concept	Meaning
Account	Your verified sign-in identity. It can belong to several workspaces.
Workspace	A team boundary containing members and projects.
Membership	Your role in one workspace: Owner, Admin, Editor or Viewer.
Project	A shared name/source-language boundary containing translation branches.
Source language	The project’s permanent, always-active language at the end of every fallback chain.
Target language	Another language that can be active or inactive and has one fallback link.
Fallback chain	An explicitly configured order from a target language to the source.

Each project starts with main. A branch owns its language configuration, keys, values, tags and file mappings. A key is a case-sensitive branch-wide name. A value is independent text for one configured language. No language value is required or treated as the original. The source language remains a fallback setting.

One account, different roles

You may be an Admin in one workspace and a Viewer in another. Permissions are checked against the workspace you are using. Customer roles do not grant platform administration.

All workspace members can see all projects in that workspace. There are no separate project memberships in this release. See the role matrix.

Names and identity

Workspace and project names can change and do not have to be unique. URLs identify records using UUIDs. Renaming a record does not create a new one or move it to a different workspace.

Workspace selection is part of the URL. Two browser tabs can use different workspaces independently.

Archive and inactivity

Archiving a workspace makes all its projects read-only and revokes pending invitations. Archiving one project only affects that project. Existing members retain read access.

An inactive target language keeps its fallback setting. Restoring a workspace does not restore archived projects or reactivate inactive languages automatically.

Configuration and translation delivery

The current release manages projects, languages and independent key/value content, project tags and reviewed file transfers. A fallback such as fr-CA → fr → en describes an order; it is not an automatic regional rule. Release validation resolves this explicit chain while the editor retains direct values.

See translation management for content editing. Releases and delivery capture immutable packages and activate compatible publications. Continue with the Flutter SDK quick start for application integration.

Independent content branches

Use Branches to fork content and compare and merge reviewed changes. Workspace roles remain shared. The three header selectors remember context without changing other browser tabs. Branch operations never publish translations.

Releases and distributions

A release captures immutable branch content and compatibility bounds. A distribution is an application delivery identity with fixed Preview and Production channels. A publication is an ordered activation of one release on one channel. Application versions, release numbers and protocol versions are independent. See publication rules.

Translation assistance

Translation assistance uses workspace-owned provider connections but branch-bound jobs. A proposal is separate from a translation value until an authorized user explicitly applies it. Connections are not forked or merged.