Audit log

Written By Jessica Moore (Super Administrator)

Updated at March 16th, 2026

The Audit Log in the admin area in SchemeServe provides a clear record of activity within your site. This guide explains the table layout and the meaning of each event type so you can understand and trace actions with confidence.
 

Audit Log Table Columns
Below is a simple explanation of each column shown in the audit log:

  • Date & Time
    The exact date and time the event took place.
  • Event Type
    The category of activity that occurred (e.g., Login, Client, Policy). A full list of event types is included later in this document.
  • Reference
    The item or record the event relates to. This may be a username, client ID, scheme ID, policy number, or another internal reference.
  • Action
    What happened during the event. Common actions include:
    - Success – The action completed successfully (e.g., successful login).
    - Updated – A record was changed.
    - Created – A new record was added.
    - GoLive – A scheme or item was published.
  • User Name
    The SchemeServe user or system account that performed the action.
  • IP Address
    The IP Address from which the action was performed. Useful for security checks and tracking access.
     

Event Types Explained

Here is a list of all event types available in the Audit Log and what they represent.

  • Account
    Changes to user accounts, such as updates to profiles or settings.
  • AgentStatementSentToAgent
    Records when an agent statement has been generated and sent.
  • Case
    Activity relating to cases (policies) within your site
  • Claim
    Events relating to claim creation or updates.
  • Client
    Creation or updates made to client records.
  • DocumentTemplate
    Changes to document templates used for generating PDFs or dynamic documents.
  • Endorsement
    Updates or creation of endorsements.
  • Insurer
    Changes made to insurer profiles or configurations.
  • Login
    Records user login attempts.
  • 2FA
    Two‑factor authentication events – typically approval or verification attempts.
  • MasterPin
    Events related to master PIN authentication (only used internally by SchemeServe).
  • PasswordReset
    Tracks when passwords are successfully reset.
  • PasswordResetRequest
    Captures when a user initiates a password reset process.
  • Policy
    Policy‑related activity, including updates to policy details.
  • QuotationTemplate
    Changes made to templates used for generating quotations.
  • RateFile
    Updates to rate files used for calculating premiums.
  • Rule
    Changes to rules (e.g., workflow rules).
  • RuleAction
    Activity relating to actions triggered by rules.
  • RuleCondition
    Changes to the conditions that define when rules activate.
  • Scheme
    Events relating to schemes, including creation, update, or publishing (GoLive).
  • User
    Changes to user accounts, permissions, or settings.
 
 


  How to Use the Audit Log:

1. Filter by date range to review specific periods.
2. Filter by event type to investigate specific categories of activity.
3. Review IP addresses to verify access locations.
4. Use Reference values to trace actions on policies, clients, or scheme items.
 


Policy Activity Logs

Each policy (case) also has its own Activity Log, which records actions taken on that specific policy.

This can include events such as:

  • Who cleared a referral
  • When a policy was put on cover
  • Changes or updates made during the lifecycle of the case
  • Other actions taken by users on that policy

The policy activity log provides a clear timeline of activity for that individual case.


Activity Logs in Other Modules

Many configuration modules within SchemeServe also display activity information, showing when items were last edited and by whom.

For example:

  • Question Sets show the last user who edited them and the date of the change
  • Similar activity tracking is available in other configuration areas such as documents.

This makes it easier to identify recent changes and track configuration updates across the platform.