Guide · Getting more out of it
Working with a team
Share a glossary and a translation memory with colleagues — encrypted on your device, joined by a link, and nothing published until you press Share.
Updated · 3 min read
Traxlate keeps your work on your device. A team needs two things to leave it on purpose: the terms everyone must use, and the sentences someone has already got right. Both can be shared from Settings, and both are built so that we hold only what we cannot read.
A shared glossary
Under Team glossary in Settings, a signed-in person creates a share and gets a link. Send the link to your colleagues: whoever opens it gets the entries into their own glossary, needs no account to do so, and can accept later updates from you. From then on the team's terms are enforced in their translations the same way their own glossary is — a term that cannot be fitted into a sentence is flagged under it rather than silently dropped.
The key that unlocks the share is inside the link, after the `#`, and that part of a link is never sent to a server. So keep the link private: anyone who has it can read the glossary.
A shared translation memory
Under Team memory in Settings, Start or join: start a shared memory and get a link, or paste a link a colleague sent you. Nothing is published until you press Share and get updates. That press sends the corrections on this device to the share and brings back what your teammates have shared, so a sentence a colleague already corrected comes back corrected for you the next time it appears.
Your own memory stays on your device and keeps working on its own; the share is a copy you choose to send. Where two people corrected the same sentence differently, the more recent correction is the one that is kept.
A shared memory is meant for the sentences that recur across a team's work — the boilerplate paragraph, the safety line, the standard clause. It is not a place a client's document goes: only the corrections you push are shared, never the source files, the history or anything you did not press Share on.
What we hold, and what we cannot read
A share is encrypted on your device before it is sent. The server stores the encrypted blob and a version number so that two people pushing at once are merged rather than one overwriting the other. It never has the key, so it cannot read a term or a sentence. Leaving a share from Settings stops this device from sending to or receiving from it; what has already been shared stays with the people who have the link.
Seats on a licence
A subscription covers one person on one device. A licence that holds several people is built into the product but is not sold yet, so today each person who wants Pro subscribes on their own device. Sharing a glossary or a memory needs no subscription at all — only an account for the person who starts the share.
- Does a teammate need an account?
- Not to join. Opening the link is enough; the terms or sentences land in their own glossary or memory on their own device. Starting a share needs a signed-in account.
- Can a teammate see my history or my documents?
- No. Only what you push to a share is shared: glossary entries, or the corrected sentences in your memory. History, documents and everything you did not press Share on stay on your device.
- Can we work on the same document at the same time?
- Not yet. The Desk is local to your device. Export the file, send it, and the other person opens it in their own Desk; the shared memory means your corrections are already there for them.