Help Centre

Choose a category to find the help you need

Making logs visible - agileChilli

As you may know, audit trail information is available in various places within agileBase.

At the bottom of each record, is a ‘history’ link which shows the past 12 months of data changes for that record – who changed what, when.

Additionally in the admin dashboard, administrators can download spreadsheets of the most recent 200,000 data changes, logins, view accesses, schema changes etc.

However what we’re now offering takes it a step further. It’s possible to make all of that data visible *within* agileBase, in normal tables. That means you can search, chart & analyse audit trail data in exactly the same way as any other data in agileBase. You can even set up custom workflows: want to receive an email whenever anyone exports any data to Excel, or when a new user logs in for the first time? Just set up a view filtered to show that data, along with an email workflow.

Furthermore, rather than just storing the previous 12 months worth of data, you can keep as much as you like.

How much does it cost?

Much less that storing the same amount of data would typically cost, based on the standard pricing structure. In fact, at the time of writing, there’s an introductory flat rate of £15/month for each year’s worth of data.

How do we set this up?

Setup is simple. Just create tables with the following names and field names. All fields are text unless otherwise specified.

ab data changes – to record record creations, updates and deletions

  • table id
  • table
  • action
  • record id (whole number field)
  • saved data
  • field id
  • field

ab logins – shows the date, time and details of each login

  • ip address
  • browser
  • operating system
  • provider
  • country
  • details

ab authentication changes – records important changes such as user privilege changes, password updates etc.

  • table id
  • table
  • action
  • details

ab view access – shows every time that a user looks at a view, or filters is

  • view id
  • view
  • details

ab table changes – all schema changes made to tables, e.g. fields added or removed

  • table id
  • table
  • action
  • details

ab view changes – similarly, all changes to views, such as field, filter or calculation modifications

  • view id
  • view
  • action
  • details

The eagle eyed may notice that a couple of fields are missing from each of those tables, which are the user who made the change and the time it was made. That data is actually stored in the standard ‘system’ fields ‘created by [auto]’ and ‘creation time [auto]’. Those fields can be made visible in views created from the tables.


Not found what you’re looking for?

Please email us at [email protected]