Activity history

On a busy team, “who changed this?” should never be a mystery. Geniviv answers it automatically: every file carries its own activity history.

What gets recorded

Whenever something meaningful happens to a file, Geniviv writes it down:

• Uploads and new versions
• Renames and moves
• Sharing and access changes
• Locking and unlocking

Each entry captures who did it and when, so the history reads like a clear timeline of the file’s life.

It's automatic

You never have to remember to log anything. The history is a by-product of doing the work — every action records itself.

Why it matters

A trustworthy record changes how a team works:

• Accountability — everyone can see who made a change, so there’s no finger-pointing.
• Context — a new collaborator can read a file’s history and understand how it got here.
• Confidence — because nothing is hidden or overwritten, you can trust what you’re looking at.

Reading a file’s history

Open any file to see its activity — its versions and the events around it, newest first. It’s the same trail whether you’re checking a quick “did the new mix land?” or reconstructing exactly how a master came together.

History and versions go hand in hand

Activity history and versions are two views of the same truth. Versions are the takes of a file; the activity history is the story around them — including the shares, moves, and locks that versions alone don’t show. Together they make a file fully self-explaining.