Seeing and comparing versions works in the Free edition. Putting one back is a change, so it needs Pro.
Open the known versions
- Open a document (click its row).
- In the document editor, choose 🕘. The list of known versions opens, newest first.
Where the versions come from
- Now: the document as it is.
- Copies from the audit log: before each change made in Firetool on this computer, the audit log kept a copy. Each one says who made the change, when, and which change it was.
- Earlier times, when you choose Look back (below).
Versions with the same content are shown as one row. Each row says which fields changed from the one below it. A change that kept no copy shows as a gap, so you can see that something happened in between.
Look back
Look back reads the document as it was at a few earlier times, using Firestore's point-in-time reads. Each time is one read. Without point-in-time recovery, Firestore keeps the last hour; with point-in-time recovery turned on for the database, up to 7 days. This is the only way to see changes made outside Firetool, such as by your app or the Firebase console.
View, compare and put back
- View shows that version in full.
- Compare with now shows the fields that differ from the document as it is.
- Put back saves that version over the document. It's an ordinary save: it follows your role and project rules, it's recorded in the audit log, and the version it replaces becomes a known version too.
Questions
Is this the document's full history?
No. Firestore doesn't record a document's versions. Firetool shows the copies its audit log kept before changes made in Firetool on this computer, and the times you look back at. Changes in between that Firetool didn't make or read aren't there.
Does looking back cost anything?
Each earlier time is one document read, billed by Firestore like any other read.
Related
- Firestore data editor: editing documents with exact types.
- Edit documents: the document editor, step by step.
- Roles and production safety: the audit log and restoring changes.