Skip to content

The project hub

Open a project from the dashboard to reach its hub — the control center for that one project. The header shows the project’s name (and a Continuous pill for continuous projects); below it, a row of tabs covers everything the project owns.

Which tabs you see depends on your role and the project type:

  • Delivery and Analysis appear for project managers and admins.
  • Editor appears on standard (document) projects; Integration takes its place on continuous projects.
  • Overview, Snapshots, Team, Translation Memories, Glossaries, and Settings are always there.

The landing tab: the project at a glance.

  • A progress chart and a Languages card summarizing the source and target languages and the file count.
  • A Status card with the deadline, days left, the assigned team, and the creation date.
  • A Quality card counting unresolved QA issues by severity — see QA and entities.
  • An Estimated cost card (managers only) with machine-translation token usage and translator costs.
  • A Files card listing every file with its word, character, and segment counts, and one row per target language: workflow stage, a progress bar, the people assigned, and an Open Editor link.

On continuous projects, Overview adds a getting-started checklist, a connection status banner, and a Visual Editor card for editing translations directly on your live site — see Continuous localization.

Where finished work leaves the platform (project managers and admins).

  1. Select Create translated files — the platform rebuilds every document in its original format with the translations applied. Re-run it any time the translations change.
  2. Download each file from the Available downloads list.

The tab also offers:

  • Export as XLIFF — download the project as XLIFF 1.2 files for external CAT tools.
  • Sync translation memories — write approved completed rows to the writable TMs attached to the project, with a report of written, deduped, conflicting, and skipped entries.
  • Re-open for editing — on a completed project, when it needs more work. Downloads and rebuilds do not require re-opening.

Delivery actions can be gated: unpaid assignments must be paid before files can be created or downloaded, and unresolved QA issues at error severity or above are flagged before delivery. See also Delivery & payments.

A flat list of every file and target language pair, each with an Open Editor button. This is the quickest route into the CAT editor when you know what you want to work on.

Continuous projects only: connects the project to where your content lives. The setup guide follows the integration mode chosen in Settings — developer uploads (JSON), a JavaScript snippet with a configurable language switcher, an edge proxy, or the WordPress plugin. The full setup for each mode is in Continuous localization.

A snapshot is a page captured from the visual editor — including authenticated pages — so translators can work on it without login access to your site. Each snapshot lists its page title, version, URL, capture date, expiry, and how many translatable blocks it holds.

  • Open — opens the snapshot in the visual-editor viewer.
  • Re-capture — captures the live page again as a new version.
  • Delete — removes the snapshot permanently.

Who works on the project.

  • Add Translator opens the assignment panel — the same one as in the creation wizard — to pick people per file, target, and workflow stage. See Offers & assignment.
  • Pending offers lists offers awaiting an answer, with a Cancel offer action per row.
  • Each file and target shows its workflow stages and the seat state per stage: unassigned, offer sent, negotiating, accepted, confirmed, or assigned. Assignees appear with a role badge and their stage deadline.
  • On organization projects, managers can also Add PM and choose which files each project manager handles — see Organizations.

The TMs attached to each language pair of the project — attached memories feed matches to the editor and can pre-fill segments before machine translation.

  • Add TM attaches an existing memory; Create New makes an empty one and attaches it.
  • Per attached TM: mark it Authoritative, toggle whether it is applied at the MT stage (and counted in analysis and quotes), open it in the TM editor, or detach it.
  • Managers control whether assignees may attach their own personal resources: allowed, org members only, or disabled.

See Translation memories for how TMs work.

The glossaries attached to each language pair, keeping terminology consistent in the editor.

  • Add Glossary attaches an existing glossary; Create New makes one (optionally case-sensitive). Managers can also attach system reference termbases.
  • Per attached glossary: mark it Authoritative, set who may add terms from the editor (read-only, only you, or project members on that language pair), open it in the glossary editor, or detach it.

See Glossaries for details.

TM-leverage analysis for managers: how much of the project’s wordcount is repetitions, exact TM matches, fuzzy matches, or new words, measured against the TMs applied at the MT stage.

  • Run analysis produces the band breakdown — words, characters, and rows per band, with a per-target expansion.
  • The Quote card turns a completed analysis into a price: enter a manual rate per word (and currency), or use your organization’s default rate card, to get a weighted-word quote per band.
  • General — rename the project, and change the deadline on standard projects. Shortening the deadline may be refused once a seat is confirmed.
  • Quality assurance — turn individual automatic QA checks on or off (they run on every machine translation and editor save), and — where enabled — tune MT quality routing: flagging low-quality rows, the threshold, enforcement severity, and auto-approval of top-band rows. See Machine translation & quality.
  • Continuous projects add a Translation section (MT engine override, glossary management, a monthly token budget) and an Integration section (integration mode and API keys) — see Continuous localization.
  • Danger ZoneMove to Trash hides and pauses the project; restore it from the dashboard’s Deleted group before the retention period expires.