Pull content out of the CMS, store, or help centre it already lives in, translate it, and (for most of them) publish the translations back.
Who this is for
Owners and admins on the project.
Before you start
Every platform needs credentials created on its side, and the requirements differ. The connect screen for each one carries a Before you connect note listing exactly what to create and which permissions it needs. Read it, because the most common failure is a token that can read but not write.
Steps
Open the project's CMS screen.
Choose the platform.
Follow its Before you connect note to create the credentials it asks for.
Paste them in and save the connection.
Run Sync from CMS to bring content in.
What happens next
Content arrives as ordinary keys in your project, so it goes through translation memory, the glossary and quality checks exactly like anything else. Translate and review it as usual.
Getting it back depends on the platform, and the connect screen says which you have:
Two-way platforms accept the finished translations back, writing only the target-language content and never touching your source.
One-way import platforms are read-only from transglot's side, usually because the platform models each language as a separate site or has no per-language write path. The screen labels these read-only, and there is no publish-back.
If it doesn't work
If the sync brings nothing in, check the credential's scope covers the content type you expect.
If translations do not appear back in the platform, check whether that platform is two-way at all.
Related
The integrations hub