AppsAutessaDB

Row-level security and access · AutessaDB

Data access log

The AutessaDB access log records every read, change and decrypt of protected data in your tables: who did it, when and from where. It filters by table, row, date range and action, and shows a chain integrity check so you can tell the trail is complete.

Goes beyond a typical managed database
Access log · customersChain verified ✓SAMPLE
whenwhoactionrow
09:41:07dana@ (person)DECRYPT1042
09:40:55SupportAgent (as dana@)READ1042
09:38:12dispatch-sync (key)UPDATE1051
09:31:40Portal visitor #88READ1043
Every read, change and decrypt of protected data: who, when and from where.

-- the problem

"Who looked at this record?" should have an answer

Auditors, privacy requests and incident reviews all ask the same question. Application logs rarely capture reads, and never across scripts, agents and API keys. AutessaDB writes the trail at the data layer, for every caller.

What you get

  • Every read, change and decrypt of protected data, newest first.
  • Who (person, agent, app or key), when, and from where.
  • Filter by table, row, date range and action.
  • A chain check shows "Chain verified", or flags a chain integrity issue.
  • Reveals of masked values are recorded.
  • Readable from the terminal with autessa autessadb access-log list.

-- how it works

How does data access log work in AutessaDB?

  1. Pick a table

    Open AutessaDB, then Access log, and choose a table you administer.

  2. Filter

    Narrow by date range, action or a single row.

  3. Drill in

    Open an entry for its full detail.

-- every option

Access log filters

optionwhat it does
Table / rowOne table, or one row within it.
Date rangeFrom and to dates.
ActionReads, changes, decrypts and other actions.
Chain statusChain verified, or a chain integrity issue.

-- example

Read the access logbash
autessa autessadb access-log list --tableId ayXduiaLeFKh

Full reference in the AutessaDB CLI docs and the API reference.

-- permissions

Who can do what?

accesscan
Table ADMINRead the table's access log.
Everyone elseNo access to the log for tables they do not administer.

-- relations

How it connects

-- faq

Questions about data access log

Does the access log include reads?

Yes. It records reads, changes and decrypts of protected data, not just writes.

Who can see the access log?

Admins of the table. Others see a message that they need a table they administer.

Can I export it?

You can read it from the terminal with autessa autessadb access-log list and save the output.

$ autessa autessadb tables create

Try data access log in AutessaDB

Every read, change and reveal of protected data is logged by table and row, with a chain integrity check and filters by date and action.

Read the AutessaDB guide or install the CLI.

100% customizable, code and all

Make AutessaDB fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours