Contextual threads
Attach comments to terms, concepts, examples, source passages, translation memory matches, or review tasks.
Feature
Keep translation discussions attached to the exact term, source, domain, document, or workflow step they concern.

External chat threads lose context quickly because they separate the discussion from the term, source, document, and review state that gave the question meaning.
Idanium keeps conversations inside the translation record so a future reviewer can see not only what was decided, but why it was decided and which evidence shaped the outcome.
Attach comments to terms, concepts, examples, source passages, translation memory matches, or review tasks.
Preserve the reasoning behind terminology choices, rejected alternatives, and expert approvals.
Mention translators, reviewers, domain experts, terminology owners, or project leads without moving the discussion elsewhere.
Turn a resolved discussion into a note, guardrail, glossary update, or source annotation.
What this adds
The goal is not chat for its own sake. The goal is to keep every explanation attached to the record it improves.
A translator can ask whether a literal equivalent is acceptable, attach the source sentence, and request a domain expert opinion.
A reviewer can accept a translation, reject a competing equivalent, and explain which register or jurisdiction applies.
A future team can inspect the discussion when the same term appears in a new project or when a source changes.
Connected records
This turns communication into structured institutional memory instead of a loose archive of comments.
Discuss preferred terms, forbidden terms, definitions, and examples in the same place where they are stored.
Attach debates to the concept itself when the issue is meaning, not only wording.
Keep assignment, review, blocker, and approval conversations visible to project owners.
Reference the source passage, citation, date, or document version behind a decision.