Documentation

History

Requires. History on the customer's location.

The History tab is the customer's complete audit log — every field edit, every status change, every note added, every payment posted, every attachment uploaded, every user who touched the record. If you need to answer "who changed this?" or "when did this get set?" for any piece of data on the customer, this is where you look. Nothing is ever removed from history; it's append-only.

Getting here

  • Click History in the customer's header tab bar (history icon). There's no count badge.
  • Or navigate directly to https://portal.securitytrax.com/{your-company}/customers/{id}/history.

The log

Each row is one change. Columns:

  • Timestamp — when the change happened, shown in your profile's timezone.
  • User — the logged-in user who made the change (or "System" for automated actions).
  • Action — Create, Update, Delete, or a named event (e.g. "Invoice Generated", "Payment Applied", "Workflow Advanced").
  • Entity — what was changed (the customer field, or a related record like a note, an invoice, an appointment).
  • Field / Attribute — the specific field changed, when applicable.
  • Old value — what it was before.
  • New value — what it became.
  • Source — the part of SecurityTrax that triggered the change (web UI, API, workflow automation, integration sync, etc.).
  • IP address — the IP the change was initiated from, if recorded.

On very active customers, the log can be long. Filter controls let you narrow by:

  • Date range — only show changes in a window.
  • User — only show changes by a specific user.
  • Action type — only show specific action types (e.g. just field edits, just deletes).
  • Entity — only show changes to a specific kind of record.

What gets logged

Pretty much everything user-initiated:

  • Customer field edits — every field on the edit form, including address, phone, email, sale details, contract term, monitoring company, etc.
  • Note and ticket activity — creating, editing, closing, reassigning.
  • Appointment scheduling — creating, rescheduling, cancelling, completing.
  • Work order activity — creating, editing, completing, invoicing.
  • Equipment — adding, editing, replacing, removing.
  • Accounting — invoices created, payments recorded, billing methods added, funding events.
  • File uploads — each file upload, edit, delete.
  • Tag changes — tags added or removed.
  • E-Doc activity — envelopes sent, signed, voided.
  • Workflow progression — each step advancement on enrollments.

Fewer things are logged that happen without human action — routine system tasks, background sync checks, etc. — but the vast majority of anything a user would want to trace is captured.

Sensitive data in history

  • SSN, bank account numbers, credit card numbers — SecurityTrax masks these in history the same way it does elsewhere. You'll see ***-**-1234 or similar unless you have the confidential-field permission for that specific field.
  • Passwords — never stored in the clear, so never shown in history. You'll see "password changed" as the action, not the actual password.
  • Confidential flags on UDFs — admins can mark custom fields as confidential; those follow the same masking rules.

Immutability

History entries can't be deleted or edited — that's the whole point. If a change was made in error:

  • Make a new change to correct it. The corrected value becomes the new "current"; the wrong value and the correction both appear in history.
  • Don't try to work around history. If you need a value to appear to "never have been there," that's not supported. Your auditor will notice.

Archiving the customer doesn't remove history either. A soft-deleted customer's history is still readable by anyone with the permission.

Typical uses

  • Dispute resolution. The customer says "no one told me the rate was going up" — check history for when the rate change was saved and who saved it.
  • Compliance audits. An auditor asks "show every change to this customer's permissions over the last year." Filter history by the relevant field and date range.
  • Debugging. A value is wrong; was it wrong when entered, or did something change it later? History has the answer.
  • Personnel reviews. A manager wants to see what a specific rep has been doing — filter by user across multiple customers' histories.

Related

  • Notes & Tickets — for deliberate commentary and task tracking (as opposed to passive logging).
  • Home — the live data whose past states are reflected here.