> For the complete documentation index, see [llms.txt](https://codifi-fdm.gitbook.io/codifi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codifi-fdm.gitbook.io/codifi-docs/mobile-app/edit-history-recall-and-project-history.md). # Edit History, Recall, and Project History Every change to a Record in Codifi is logged. Open the **clock icon** on a Record and you see who edited which field, when, and what the value was. The same activity log powers the Project-level **Project History** view — broader visibility into who did what across the whole Project. For accidents, **Recall** lets you restore a previous value as a new edit (without rewriting the history). *** ## Per-Record edit history ### How to open it From any Record's screen, tap the **clock icon** (usually in the header). The history panel opens, showing every edit to the Record in reverse chronological order. ### What you see For each change: * **Who** made the change (assignee avatar + name). * **When** the change happened (timestamp). * **What** changed — the field name, the previous value, and the new value. * **From where** — web, mobile (iPad / iPhone), or system. The full history includes: * Field value edits. * Status changes. * Assignee changes. * Geometry edits (vertex added, moved, deleted). * Media added or removed. * Relationship changes (parent added, changed, or removed). *** ## Drilling into a single field's history Within the Record's history view, tap a field's row to scope the panel to just that field. You see only that field's edit chain — every value it's ever held, who set each, and when. This is the workhorse view for "what was the original value?" and "when did this field's value change?" *** ## Recall — restoring a previous value Sometimes a field has the wrong value because someone (you, a teammate, an automatic process) edited it incorrectly. Recall fixes the field while preserving the audit trail. ### How Recall works 1. Open the Record's history. 2. Find the previous value of the field you want to restore. 3. Tap **Recall** next to that historical value. 4. The previous value is restored as **a new edit event** — not as a rewrite of the original change. After Recall, the history shows: ``` 2026-05-15 09:42 Alex Voigt Length: 8 → 12 (recall of 2026-05-15 09:30 value) 2026-05-15 09:35 Hugo Hernandez Length: 12 → 8 2026-05-15 09:30 Alex Voigt Length: (new) → 12 ``` Both changes are visible. The Recall didn't delete Hugo's edit — it added a new event that restored the previous value. This matters for compliance, audit, and "who did what" reconstruction — the past is never rewritten, only added to. *** ## Project History — the Project-level view Project History shows the same kinds of events as Record history, but **across every Record in the Project**: * Records created, edited, deleted. * Photos added or removed. * Assignee changes across all Records. * Status moves at the Project level. * Project members added or removed. * Relationship changes that span Records. ### When to use Project History * **Audit / compliance** questions across the Project ("when was this Project finalized?", "who reassigned Records that week?"). * **Troubleshooting** when a Record's history alone doesn't explain something ("when did this STP get reassigned away from me?"). * **Project review** before a deliverable handoff — see the shape of activity over the Project's lifetime. Project History is currently a web-side view; mobile shows per-Record history via the clock icon. Both surfaces read from the same activity log. *** ## When Recall won't help A few cases where Recall isn't the right tool: * **Recalling a value that's downstream of a Ripple formula.** Recalling the input restores the input; the calculated field that depends on it re-evaluates per its formula. Recall doesn't override formula logic. * **Recalling something that was deleted, not edited.** A deleted Record's geometry can be restored by recovering the Record itself (talk to your PM or support); Recall only affects field-level edits. * **Recalling across a status change.** If you want to revert a status change, do it the normal way — change the status to the previous value. History captures both moves. *** ## Common questions ### Does my history fill up forever? Yes — Codifi retains history for the Project's lifetime. Old Projects keep their history; nothing is auto-pruned. The storage cost is small because events are tiny compared to Records or media. ### Can I see history from before someone left the team? Yes. History captures the user account at the time of the change. Even if the user is later deactivated or removed, their history events remain visible (showing their name as it was at the time). ### Can I "delete" sensitive edits from history? No. History is append-only — Recall adds a new entry but doesn't remove the original. If sensitive PII was accidentally entered into a field, the canonical fix is to update the field (so the latest value is clean), then document the issue with your tenant admin who can request server-side action if needed. ### Do mobile and web see the same history? Yes. Both surfaces read from the same activity log. A change made on mobile shows up in the web's Project History as soon as the Project syncs; a change made on web shows up in mobile's Record history on the next iPad sync. ### Why is Project History only on web? Per-Record history is more useful in the field (you're working with one Record at a time); Project-level audit is more useful at a desk. Mobile + clock icon + per-Record history covers field needs. *** ## Related * [**Hydra**](/codifi-docs/cross-platform-features/hydra.md) — the underlying sync technology that makes the activity log work consistently across web and mobile. * [**Syncing & the Cloud Icon**](/codifi-docs/mobile-app/getting-in-the-field/syncing-and-the-cloud-icon.md) — what controls when local edits become visible in history server-side. * [**Web: Project History**](/codifi-docs/web-app/project-history.md) — the Project-level view of the same activity log. * [**Fixing Wrong Parents**](/codifi-docs/mobile-app/records-in-context/fixing-wrong-parents.md) — for relationship issues, which are also tracked in history.