Skip to main content
Every translation value keeps a full history of its changes. Nothing is ever silently overwritten — you can always see what a value used to be, who changed it, and roll back to any earlier version.

​
What history records

For each value, TextSetu stores an entry every time it changes, including:
  • The previous text and the new text.
  • Who made the change (name and email).
  • When it happened.
  • Who approved it (when the approval workflow is in use) and when.
This gives you a complete audit trail per value, which is invaluable for debugging “who changed this and why” questions and for compliance.

​
Viewing history

Open a key’s detail panel (or the cell’s History view) on the Translations grid. You’ll see the chronological list of edits for that value in the selected language, most recent first. Glossary terms and translation-memory entries keep their own history too, so you can track terminology and segment changes the same way.

​
Rolling back

From the history list, you can restore a previous version. The restored text becomes the current value (subject to the approval workflow if it’s enabled — a rollback by a non-approver is itself a proposal). The rollback is recorded as a new history entry, so the timeline stays complete; rolling back never erases the record.

​
Activity logs

Beyond per-value history, TextSetu keeps activity logs at the organization, project, glossary, and translation-memory level. These show the broader stream of actions — keys added, members invited, approvals, imports, merges, and so on. See Analytics & Activity.

​
When you’ll use this

  • Reverting a bad edit — restore the prior value in one click.
  • Auditing — prove who changed a string and when.
  • Understanding outdated flags — see what the source/translation used to be when a value was flagged outdated.
Related: Translating · Approval Workflow · Analytics & Activity