Skip to main content

Team plan · for small agencies and translation teams

Manage the work, share the memory.

Upload a Word document on contextra.pro and assign it to a translator. Their progress shows on your project page and, once every segment is translated and reviewed, they hand back the translated .docx with Complete. Share a Translation Memory or Term Base, and teammates who subscribe get a read-only copy for their documents in the same language pair.

Free 14-day trial, no credit card needed. Create a team on contextra.pro during your trial to try it with up to 3 seats, yours included. AI isn't included: each member uses their own API key or their own AI Credits.

Projects
Tarnwick — EU dealer pack

Warranty, safety and dealer terms for the 2027 season.

English (US) → Spanish (Spain)

Project settings
Add a document

Pick the DOCX, say who translates it and by when. They open it in the Contextra app already set up.

Upload DOCX
DocumentAssigned toDueStatusSize
Retailer agreement.docx

64/64 translated · 64 reviewed

updated Oct 8, 2026

Elvira Zubelzu10/09/2026Completed3.1k wordsTranslationWorking fileDelete
Warranty terms.docx

31/48 translated · 12 reviewed

updated Oct 14, 2026

Elvira Zubelzu10/20/2026In progress1.9k wordsWorking fileDelete
Safety leaflet.docx

22/30 translated · 5 reviewed

updated Oct 13, 2026

Bastien Lorival10/12/2026

Overdue

In progress690 wordsWorking fileDelete
An invented agency's project on contextra.pro, as its owner sees it.

TranslatedReviewedOne bar, because reviewed is a share of what's translated.

Nobody should have to ask how it's going

A project holds one client's or case's documents, with a default language pair. Its page shows each document's translator, due date, status and progress, as last reported by the translator's app.

  • Assign in one step

    Upload a Word (.docx) file, pick the translator and, if you like, a due date. It shows up in their Team list and opens in the language pair you set, with their memory matches already filled in. Overdue work is flagged in red.

  • Progress that reports itself

    The translator's app reports translated and reviewed counts as they work, while they're online. It sends counts, never document text; reload the page to see the latest.

  • Complete waits for every segment

    Complete unlocks only when every segment is translated and reviewed. It hands the job back with the translated .docx, ready to download from your project page. It checks completeness, not quality.

The handed-back file is watermarked whenever the translator's own export would be.

What happened, and who's free

  • Every document keeps a timeline, from assignment to hand-back. It isn't an audit log.
  • Each export the translator makes while online saves a checkpoint for the team.
  • The Workload card shows each translator's open documents, their total size in words and anything overdue.
  • Reassign a job midway, and the next translator picks up the last version exported or handed back.
Document
Retailer agreement.docx

64/64 translated · 64 reviewed

updated Oct 8, 2026

  1. Oct 2, 2026Added to the projectby Oona Quenby
  2. Oct 2, 2026Assignedby Oona Quenby
  3. Oct 5, 2026Work startedby Elvira Zubelzu
  4. Oct 6, 2026Progress savedby Elvira Zubelzu— 40/64 translated, 18 reviewed
  5. Oct 8, 2026Translation deliveredby Elvira Zubelzu
  6. Oct 8, 2026Handed backby Elvira Zubelzu
One document's timeline, from upload to hand-back.
Workload

Open work across your active projects, by translator.

Oona Quenbyowner
0 open0 done

Free — nothing open.

Elvira Zubelzu
1 open · 1.9k words1 done
  • Tarnwick — EU dealer pack/Warranty terms.docx
    Oct 20
Bastien Lorival
1 open · 690 words1 overdue0 done
  • Tarnwick — EU dealer pack/Safety leaflet.docx
    Oct 12
Workload, on the team's page: open work per translator.
See everything in the Team plan

Check a segment without writing it into your memory

Opening a segment and moving on marks it reviewed; accepting it with Enter also saves it to the translator's own Translation Memory. So translators choose what their memory learns, and your project page still shows how much of each document has been reviewed.

Reviewed also counts 101–102% memory matches and repeats of an accepted segment, even if nobody opened them. Each translator should keep a Translation Memory and a Term Base of their own: a memory they subscribe to is read-only.

Your translators work in Contextra, on their own computers

Everyone translates in the Contextra desktop app, on macOS 13 or later or Windows 10 and 11 (x64). Its Team section lists each translator's assignments, soonest due first: Start working opens a job already set up, and Complete hands it back.

Elvira's Contextra app · Team
Contextra·Team
EditorLibraryTeamMemoryUsageShortcutsSettingsEZelvira@example.orgTeam seat
Quenby Language Studio — assigned to you RefreshManage on the web
Tarnwick — EU dealer pack
Retailer agreement.docxCompletedEnglish (US) Spanish (Spain) due Oct 9· 64/64 translated · 64 reviewed· work in progress· delivered Oct 8, 2026, 5:12 PM Download what you sent Reopen
Warranty terms.docxCompletedEnglish (US) Spanish (Spain) due Oct 20· 48/48 translated · 48 reviewed· work in progress· delivered Oct 16, 2026, 11:05 AM Download what you sent Go to
Oona's project page on contextra.pro
DocumentAssigned toDueStatusSize
Warranty terms.docx

48/48 translated · 48 reviewed

updated Oct 16, 2026

Elvira Zubelzu10/20/2026Completed1.9k wordsTranslationWorking fileDelete
Elvira's app
Warranty terms.docxCompletedEnglish (US) Spanish (Spain) due Oct 20· 48/48 translated · 48 reviewed· work in progress· delivered Oct 16, 2026, 11:05 AM Download what you sent Go to
Oona's project page
Document
Warranty terms.docx

48/48 translated · 48 reviewed

updated Oct 16, 2026

CompletedTranslationWorking fileDelete
  1. Wednesday: Warranty terms is 31 of 48 translated, so Complete stays locked, and its tooltip says what's left.
  2. Friday: all 48 segments translated and reviewed. Complete unlocks.
  3. Complete saves the document on Elvira's computer first, then uploads it with the translated .docx.
  4. Handed back. Elvira can download the exact file Oona received.
  5. On Oona's project page, after a reload: Completed, with the translation ready to download.
Invented agency, people and documents. Two days pass between the first and second steps.
  • Export saves a checkpoint. When translators export while online, the team also gets a checkpoint, without the job being marked done. Saving alone never uploads.
  • Saved on the computer first. Work is saved on the translator's computer before anything uploads, so a failed upload loses nothing. Start working or Reopen loads the team's last uploaded version, so edits that weren't exported are lost.
  • Download what you sent. After a hand-back, the translator can download the exact file you received.
  • Reopen to correct. Reopen a delivered job, export it and hand it back again with Complete.
  • Team work in the Library. Team documents a translator has opened sit in their Library, under the team project.
  • Consistent across their jobs. The Quality check compares a translator's team documents in the same target language and flags a sentence translated two ways or a term that drifts.
  • Offline, clearly marked. If the connection drops, the Team list keeps showing the last list it loaded, marked as such, and documents already opened keep working.
  • Instructions per document. Translators give the AI instructions for each team document, in the editor.
Learn it in the Guide: Working on a team

Your colleague's work, in your matches

Share a Translation Memory or Term Base with your team in one click. Teammates who subscribe get a read-only copy on their own computer, kept in sync, for documents in the same language pair.

Sharing uploads every entry to Contextra's servers, and anyone on your team can subscribe. Contextra can read the entries unless your team turned on encryption before they were shared.

Translation MemoryTerm BaseTeam library
Team libraryMemories your team shares. Subscribe to consult a colleague’s; share one of your own from its card in Translation Memory or Term Base. Sync now
Following “Tarnwick — approved EN→FR”.
  • Tarnwick — approved EN→ESTMEnglish (US) → Spanish (Spain) · 2,316 entries · oona@example.orgSubscribe
  • Tarnwick — approved EN→FRTMEnglish (US) → French (France) · 1,127 entries · oona@example.orgPriority1Unsubscribe
  • Outdoor gear EN→ESTBEnglish (US) → Spanish (Spain) · 246 entries · elvira@example.orgSubscribe
Bastien's Team library, just after he subscribed to the memory for his language pair. Invented team and memories.
  • Matched on your computer

    A memory you subscribe to is matched on your computer, as fast as your own, and is there offline, as of its last sync.

  • Context matches can fill your rows

    A colleague's entries show up in your matches, and an in-context 101–102% match can fill a row before any AI runs.

TM Matches3Concordance

Now: From memory · 101% · Oct 13

  • 1101%Tarnwick — approved EN→ES (oona@example.org)In useDown sleeping bag, comfort −5 °CSaco de dormir de plumón, temperatura de confort −5 °C
  • 2100%Tarnwick price lists EN→ESDown sleeping bag, comfort −25 °CSaco de dormir de plumón, confort −25 °C
  • 384%Tarnwick — approved EN→ES (oona@example.org)Down sleeping bag, comfort −5 °C, longSaco de dormir de plumón, confort −5 °C, talla larga
In a price list Elvira translates in her own Library (Excel files can't be assigned), the 101% match in use comes from Oona's memory, which Elvira subscribes to.
  • You set the order

    Priority sets the order your subscribed memories are consulted in on this computer. A better match from another memory still comes first.

  • Syncs never overwrite your memories

    A memory you subscribe to is a separate, read-only copy, so a sync never overwrites your own memories.

  • In the app or on the web

    Subscribe in Memory ▸ Team library or on your team's page on contextra.pro.

  • See what hasn't uploaded

    A memory you share shows how many of its entries haven't reached the server yet.

Only the member who shared a memory adds to it. Unsharing stops updates; it doesn't remove copies already on subscribers' computers.

What goes through Contextra, and who can see it

Each translator's Library, unshared memories and API keys are stored on their own computer. Document text and matching memory entries leave it only to reach the AI during an AI step, or when work is shared with your team. The first export of a document on a computer also sends their Contextra account a one-line record (file name, languages, pages, AI tokens), never the text. What your team shares goes through Contextra's servers:

Assigned documents
The Word file you upload, the working file (original, segments and glossary) that Export and Complete upload, and the translated .docx are stored on Contextra's servers. They aren't end-to-end encrypted, so Contextra can read them.
Who can open them
Only the assigned translator and the team's owner and managers can download a document. Every member can see each document's name, assignee, status, due date and progress.
Progress
Progress reports carry counts, never document text. A document's timeline is visible to its translator and to managers; in Workload, members see only their own row.
Shared memories
Sharing a memory uploads every entry, with its neighboring sentences and the author's email. Any teammate can subscribe; you can't share with only some. Contextra can read those entries unless your team turned on encryption before they were shared.
AI requests
On their own key, a member's AI requests go straight to their provider. On AI Credits, the text passes through Contextra to reach the provider and isn't stored; Contextra keeps each reply, encrypted, for ten minutes, and a billing record without the text.
Where your data goes, in full

Optional end-to-end encryption for shared memories

An owner or manager can turn it on for the whole team in the Contextra app, under Memory ▸ Team library, and it can't be turned off. From then on, each shared-memory entry is encrypted on the computer that sends it, and Contextra stores it as ciphertext it can't read.

What it doesn't cover

  1. Entries shared before it was turned on stay readable to Contextra until they change.
  2. Memory names, language pairs, who shared them and entry counts stay readable to Contextra.
  3. Assigned documents, checkpoints and hand-backs aren't covered.
  4. Key distribution relies on Contextra's member and device list, which the app doesn't yet let you verify. In practice, anyone able to change that list could add a computer, and teammates' apps would pass it the key without asking anyone. There's no way yet to revoke a computer's copy of the key or to rotate the key, so a computer keeps the key after the person using it leaves the team.
  5. Each subscriber's app decrypts the entries to use them, so they reach the AI provider during AI steps, like any memory's. Term Base terms found in a document go with Analyze and with translation requests, and near matches go as references. On AI Credits, that goes through Contextra's gateway.
  6. Contextra 1.7.1 has no way to use the recovery code. If every computer that holds the key is lost, access to the encrypted entries can't be restored, and encryption can't be turned off or restarted with a new key.
Illustration
Your computer
  • Encrypts each new or changed entry before upload
  • Holds the team key
ciphertextfrom the moment encryption is on
Contextra's servers
  • Store the entry as ciphertext they can't read
  • Can still read memory names, language pairs, who shared them and entry counts
  • Entries shared before it was on: still readable
ciphertextat the teammate's next sync
A subscribed teammate's computer
  • Gets the key from a teammate's app
  • Decrypts the entry and matches it locally
  • During AI steps, sends decrypted entries to the AI provider as references (through Contextra's gateway on AI Credits)
decrypted textto the AI provider, during AI steps

Illustration. Key distribution relies on Contextra's member and device list, which the app doesn't yet let you verify. During an AI step, a teammate's app can send a decrypted entry to the AI provider as a reference, through Contextra's gateway on AI Credits. Assigned documents, checkpoints and hand-backs aren't end-to-end encrypted.

Where a shared-memory entry goes once encryption is on.
  1. 1 · Before
    Team libraryMemories your team shares. Subscribe to consult a colleague’s; share one of your own from its card in Translation Memory or Term Base. Sync now
    Encrypt shared memories.Turn on

    Before: only an owner or manager can turn it on, for the whole team, and it can't be turned off.

  2. 2 · Turn on

    Write this recovery code down now — it is shown only once.

    K7QFM-2RD8V-XZ91T-HB4NW-QE6CP-3CopyI’ve saved it
    End-to-end encrypted.

    Turn on: a recovery code is generated on this computer and shown once. Contextra never stores it, and this version of the app can't use it to restore access.

  3. 3 · After
    End-to-end encrypted.
    • Tarnwick — approved EN→ESTMEnglish (US) → Spanish (Spain) · 2,316 entries · shared by youUnshare

    After: new and changed entries are encrypted before they leave each computer. Everything shared earlier, like the 2,316 entries in Tarnwick — approved EN→ES, stays readable to Contextra until it changes.

  • Encrypted before it leaves

    Each new or changed entry is encrypted on the computer that shares it, before upload.

  • Teammates' apps pass the key on

    A new teammate's computer gets the key automatically the next time a teammate who has it syncs; nobody is asked to approve it. Until then, their Team library says it's waiting for access.

  • A recovery code, shown once

    Turning encryption on shows a recovery code once. It's generated on your computer and never stored by Contextra. Contextra 1.7.1 has no way to use it yet, so it doesn't restore access today.

What the Team plan doesn't do

Last checked: Contextra 1.7.1.

It's built for assigning, following and handing back work, and for sharing memories. It isn't a translation management system.

  • No reviewer role or approval step, and no request-changes or rejection flow: Reviewed is set in the translator's app.
  • No co-editing: each document has one assignee at a time.
  • Assignments are Word (.docx) files, one per upload, up to 200 MB. Excel and PowerPoint files can't be assigned; translators handle them in their own Library.
  • No notifications or reminders beyond the invitation email; reload your project page for the latest.
  • Projects are managed on contextra.pro; the app shows each translator their own assignments.
  • No project-level AI instructions for team projects: translators set them per document.
  • No shared AI budget: each member uses their own API key or their own AI Credits.
  • No team usage report on the website: each translator sees their own AI use in the app.
  • An account belongs to one team at a time: a translator already on another team has to leave it before they can join yours.
  • While a Team plan is lapsed, team downloads, uploads and shared-memory sync pause. Members whose license comes from the team can't use AI on their own key until it's renewed, and their exports carry a watermark unless their AI Credits balance is positive. The work on each computer is never locked away.
  • Encryption has no device verification, revocation or key rotation yet.
What Contextra doesn't do

Try it with your translators

How to start

  1. Start a free trial. No credit card needed.
  2. In your dashboard, create a team and invite translators by email as a Member or Manager.
  3. Create a project with a default language pair, then upload a Word document and assign it.
  4. Each translator accepts the emailed invitation on contextra.pro with the invited address; someone new to Contextra creates an account there, with its own 14-day trial. Then they install Contextra on macOS 13 or later (Apple Silicon or Intel) or Windows 10 and 11 (x64). They sign in with that email and password (not Google or Microsoft) and find the job under Team.

Team plan pricing

Team

For small translation agencies

$45/seat/mo

billed annually, minimum 3 seats

That's $540 per seat per year; a 3-seat team, the owner's seat included, is $1,620 a year. USD, taxes excluded.

  • Every seat gets the full desktop app
  • During your trial, a team can use 3 seats, yours included, and everyone on it needs an active trial or plan of their own. The owner chooses the number of seats when buying, and a pending invitation holds a seat.
  • Owners and managers create projects, assign work and can download any document; only the owner changes roles.
  • Each member uses their own API key or their own AI Credits.
  • Without a connection, a Team seat's license stays valid for up to 7 days after its last check; after that, AI pauses and exports carry a watermark until it can check again. AI steps always need a connection.
Already have an account? Create your team in your dashboard