Change Audit Log / Revision History

Feature Requests
21

I don’t see a survey thus my first thought here:

The history itself seems very comprehensive. Nice job!

Since you @darragh taught me to manage (build) my data admin in the app itself, I spend very litte to no time in the data backend. Thus it would be great to have a dedicated history element that I can place in my layout. I personally would prefer not to have it as part of the comments element as I do not use that element in many records.

The way I organise my record pages there is always an admin tab that is only accessible to admins. This would be the perfect place for the brand new Noloco History Element.

22

Thanks for your feedback @Tobias !

Good to know!

23

Great news @Tobias and @Brandi_Bullock

Your record-level history is now available to admins and data admins in your app.

Once enabled it will show up next to your comments (for applicable users)

image
image1072×1460 96.9 KB

24

Hi. That is great! According to your screenshot the history symbol should be aligned right on the page. On my record page it aligns left, right over the record title. Not such an ideal place in my opinion.

25

Can you share the page? This sounds like an alignment issue on our side

26

It happens because I don’t have breadcrumbs or backlinks activated. Just like the comments icon. This, too, aligns left when comments or backlink are inactive. It’s just never been a problem, because I always you comments elements on the page, never the top bar icon.

27

We’ll take a look at this today @Tobias

28

Thank you for fixing this

29

@darragh Any timeline on making this available to users who are not data admins?

We flipped some users to a data admin role so they could see the revision history (they LOVED it!), but that conflicted with permissions on the users table where we only allowed internal users to see user records for other internal users. By making them data admins, they could see them all.

The reason we limited permissions in the users table is to prevent someone from making an @mention in the record comments and accidentally triggering a notification to an external user. We have a lot, so typing in a name would commonly result in the wrong person being selected, and then we have an external user suddenly getting comment notifications for every comment in the record that they should not be seeing.

As it stands, we’ve had to take the revision history away from most users to prevent that from happening.

30

I’m glad the feedback was great @jesse

Unfortunately, this is the main reason we can’t (and won’t) make record history readily available to non-data admins.

It’s very hard to put permissions on historical data. We’re still thinking about it, but it’s not something we can easily do unfortunately.

31

Hey @darragh - thought of another middle-ground on this. Could we have an ‘export’ option on the revision history? That way at least I as a data-admin could share the revision history in plaintext/.csv with users who need to do some investigation on a particular record.

Or let me know if there is already a way to extract some of this information.

32

That’s a great suggestion actually!

What format would you expect that to be in?

Similar visual PDF? Or something more like JSON?

33

Probably .csv just to easily scroll through timestamps. I did a bit of extraction myself and used a .csv format like this:

timestamp_pt_source record_type record_label event_type actor_resolved field_name old_value new_value
2026-07-20 06:20:19 PDT [table name] [record name] create [user name] AR Payment Due Terms Net 30
This also makes it easy to reconcile against the data source’s changelog. In my case, Airtable.
34

Very interesting - thanks for sharing @jesse