Audit/access logs overview

Understand what Fluent logs, who can view logs, and how to use them for compliance and troubleshooting.

Roles: OwnersAdminsCompliance
Surfaces: Web app
2 min read Updated February 12, 2026

Context screenshot

At a glance

  • Audit logs answer: who did what, when, and where.
  • Access logs answer: who signed in, from what device/IP (if captured), and when. [Confirm in product]
  • Use logs after role changes, billing updates, or suspected account issues.

Overview

Fluent’s logs help you maintain accountability, support compliance needs, and troubleshoot operational issues. Depending on your plan and configuration, you may have audit logs, access logs, or both. [Confirm in product]

What’s typically logged

Exact fields depend on your implementation. [Confirm in product]

Audit logs (actions inside the workspace)

Common events:

  • Appointment created/edited/canceled
  • Interpreter assigned/unassigned
  • Rate/billing rule changes
  • Template changes
  • User invited/role changed/removed
  • Compliance document uploaded/changed (metadata only, ideally) [Confirm]

Access logs (authentication / sign-in activity)

Common events:

  • Successful sign-ins
  • Failed sign-ins (optional)
  • Password resets (optional)
  • SSO events (optional)
  • Device/browser details (optional)
  • IP address (optional)

Who can view logs

  • Typically: Owner/Admin, and sometimes Compliance roles.
  • Confirm your workspace’s setup in the Permission matrix.

How to use logs (common workflows)

Investigate “who changed this?”

  1. Open Audit logs.
  2. Filter by entity (appointment, interpreter, invoice, user). [Confirm in product]
  3. Filter by date/time.
  4. Review event details and acting user.

Investigate sign-in issues

  1. Open Access logs.
  2. Search by user/email.
  3. Compare timestamps with the user’s report.
  4. Look for repeated failures or unusual locations. [Confirm in product]

After offboarding or role changes

  1. Confirm the change is reflected in the audit log.
  2. Monitor for unexpected changes in the same window of time.

Best practices

  • Restrict log access to people who need it.
  • If exporting logs is supported, handle exports like sensitive data. [Confirm in product]
  • Establish a retention policy that matches your compliance requirements. [Confirm in product]

Troubleshooting

I don’t see audit logs

They may be disabled, not included in your plan, or hidden by role permissions. [Confirm in product]

Logs don’t show the detail we need

Some systems intentionally avoid logging sensitive content (e.g., PHI). Use logs to track actions and references, not raw data. [Confirm in product]

  • Permission matrix
  • Removing users
  • HIPAA readiness