Data access log
Check who read customers' details, tickets and messages, through the app or the REST API, from which network address, for the past year.
On this page
Settings > Data access lists every time someone read customers' personal data in your helpdesk: a customer profile, a ticket, its messages, a satisfaction survey, a drafted reply, an attachment or a customer's Shopify orders. Use it to answer "who looked at this customer?" or to check what a departed employee or an API key read. Only admins can open it.
Each entry records who read what, when, how and from which network address. It never copies the data that was read. Entries are kept for a year.
The audit log is the other half: it records changes. Reads are only here.
Read an entry#
| Column | What it shows |
|---|---|
| When | Date and time, in the helpdesk's time zone. |
| Who | The agent, API key, Growth Dept admin when Growth Dept staff read it, or A removed agent. |
| What | The record and its number, such as a ticket, or a list and how many it held, such as "View: 29 tickets" or "Shopify orders of customer" followed by the customer's number. |
| Through | App or REST API, with the request that read it. |
| From | The network (IP) address the request came from. |
A list counts as one read. Opening a view that shows 29 tickets makes one entry for the list; opening one of those tickets makes another entry for that ticket.
Find entries#
| Filter | Choices |
|---|---|
| Agent | Anyone, or one person. |
| What | Everything, Customers, Tickets, Messages, Satisfaction surveys, Drafted replies or Attachments. |
| Through | App and API, only The app, or only The REST API. |
| From and To | A date range. |
Show older entries at the bottom loads the next batch.
Export entries#
Export shown entries downloads what is on screen, with your filters, as data-access.csv. The file holds the same columns as the table, IP addresses included, so store it as carefully as the customer data itself.
What is not recorded#
Attachment links opened straight from an email. These links work without signing in, so nobody can be named as the reader.
Pages that show no customer data, such as settings, macros and rules.
Using it for a privacy request#
When a customer asks who has seen their information, set the dates you need, export the entries, and search the file for their customer number and their ticket numbers. Customer data and privacy covers erasing a customer's data on request.
Related articles
- Audit logSee who changed what in your helpdesk and when, from sign-in settings and API keys to rules, macros, tags and tickets, and export the entries.
- Customer data and privacyErase a customer's data when they ask, what happens to card numbers and other sensitive details in messages, and how long the helpdesk keeps what.
- The REST API and API keysFind your API address, create and revoke keys, and connect your own scripts and tools to the helpdesk, including tools written for Gorgias.
- AI Agent security and privacyWhich model writes drafts, what customer data is sent where, what is stored, and the safeguards that keep drafts from inventing facts.
Still stuck?
Write to the Growth Dept team and a person answers. Say which helpdesk you work in and what you were trying to do.