Activity log
Review the append-only record of important practice changes, imports, exports and staff actions.
Open Settings → Activity log to see important changes across the practice. Each row keeps the action, affected record, acting staff member or system source, request identifier, field changes where available, and the time it happened. Display names are copied into the event so historical rows remain readable after the underlying record or user is removed.
The log is append-only: correcting an action creates another event rather than rewriting the old one. Imports, exports, organization and membership changes, and terminal background transfer outcomes use the same record.
Patient-linked audit detail follows the practice's audit-detail retention period: the action, time, actor and subject reference remain, while the patient-bearing label and field changes are removed. Staff-only and organization-only audit detail is outside that patient-retention clock.
Filtering
Narrow the feed by the person who acted, the kind of action, the type of record affected, and a date range. The member filter includes anyone who appears in the log, including staff who have since left the practice, so their history stays reachable after their account is removed.
Sign-in and security events
Signing in and out, a failed sign-in, a password or sign-in email change, a password reset request, turning two-factor authentication on or off, regenerating backup codes, signing other devices out, and creating or revoking an API key all appear in the log alongside record changes.
Repeated failed sign-ins for one account are grouped into a single row per hour, so a burst of attempts cannot flood the feed. A sign-in attempt for an address that does not belong to an account is not recorded at all.
Actions taken by SmileLine
When SmileLine support acts on your practice — suspending or restoring an account, changing a platform role, deleting an account, or running a billing reconciliation — the event appears in your own activity log.
If a support engineer works inside your practice on your behalf, the log records that access starting and ending, and every change made during it carries a SmileLine support marker next to the member's name. Changes made by an API key are marked API key, so automated traffic is never presented as a member working at the keyboard.
An hourly Stripe billing reconciliation that confirms stored billing state already matches Stripe does not create an activity row. It appears only when the audited billing state actually changes.
When an action creates, updates or deletes CRM data, SmileLine saves the change and its audit row in the same database transaction. If the audit row cannot be saved, the CRM change is rolled back and the request fails; the system never reports an audited change as successful without its evidence.
Access-only actions, such as downloading an export or playing a call recording, do not change a CRM record. SmileLine writes those audit rows directly and uses an idempotent recovery queue if the first insert cannot reach the database. Audit dead letters are re-queued instead of being discarded. Background jobs save important terminal state changes and their audit rows together as well.
The in-app activity log supports operational accountability. It is not a replacement for a separately retained regulatory archive if your practice is required to operate one.