Leave Activity log

Use the Activity log to understand who changed a leave record, when it happened, and which values were recorded. It covers requests, types, balance policies, and balance-history entries. Reading an event does not change or undo it.

Access needed

Access depends on your assigned permissions and workflow scope.

Read/filter events, compare changes, or export the current page: audit.read
Activity log access is independent of leave management and review permissions. It does not grant changes to the underlying record.
Role and permission labels
Typical responsibility: Authorized investigator. Role names alone do not grant access.
Read the service Activity log
Open request history from a request: audit.read
Opening your own request requires your employee link; reading another person’s request additionally needs leave.requests.read. Review eligibility remains separate.
Role and permission labels
Typical responsibility: Request owner or authorized reader. Role names alone do not grant access.
Read the service Activity log
Open history from a leave type: All:audit.readleave.types.read
Type read access lets you reach the catalogue; audit.read permits reading its history.
Role and permission labels
Typical responsibility: Authorized catalogue reader. Role names alone do not grant access.
Read the service Activity log
Read leave types and policies
Open history from a balance entry: audit.read
Your own balance requires an employee link. Reading other employees’ balances additionally needs leave.balances.read.
Role and permission labels
Typical responsibility: Employee or authorized balance reader. Role names alone do not grant access.
Read the service Activity log

Demo screenshots may show broader access than your account.

Open the log

Open Leave → Activity log. Events appear newest first. Check the action, record type, actor, subject, time, and number of changes before opening an event. The actor is the account performing the action; the subject identifies the affected person where recorded.

Populated Leave Activity log with request, approval, type and balance-history events — Start with the record type and action.

You can also inspect a particular record's history: open a request's Activity log tab, choose View activity for a leave type, or use View activity on a balance-history entry. These views keep the record context so that you can investigate without searching the entire log.

Access to the Activity log is separate from permission to read or manage the underlying records. A reviewer who can approve requests does not automatically have Activity log access.

Find the event you need

Start with the record type
Open Filter and choose Entity type. Select a leave request, leave type, policy, or Balance history entry, depending on what you are investigating.
Narrow the context
Add Action, Actor, Subject, or Entity filters as needed. Actor identifies who made the change; Subject can identify the employee affected by a request. Use the record reference offered by the picker rather than substituting an employee number for a record ID.
Check the date range
Set the available start and end dates, then review the results. Read the event's displayed timestamp when comparing it with another record.
Clear filters when necessary
Remove individual filter chips or Reset to widen the search. Check other pages of results before deciding that an event is missing.

Leave Activity log filter menu — Combine filters deliberately and clear them to widen the search.

A record-scoped view may retain its fixed record context. To search across records, return to Leave → Activity log.

Read the event details

Select an event to open its side panel. Details identifies the action, occurrence time, actor, entity, subject where available, and event ID. Keep the event ID when asking an authorized administrator to investigate the same entry.

Approved leave event details showing actor, subject and record references — Use the event reference to identify the same historical action.

A record ID is a reference, not a leave balance or an employee number. If a friendly name is unavailable, use the remaining references and context rather than assuming the person or record was deleted.

Compare recorded values

Open Changes. Search the changed fields when the list is long, then expand a field with Compare to read Before and After. Not set means that the event has no value recorded on that side; it is common on a creation event.

Leave approval comparison showing Pending before and Approved after — The comparison describes this event; check the request for its current state.

This demo approval records Status changing from Pending to Approved. It describes that event in history. Open the request to check its current status and approval stage. In a two-step flow, an initial approval is not necessarily final approval.

Recognize balance-history events

Filter Entity type to Balance history entry when investigating an adjustment or another recorded balance movement. A Created event here means that a history entry was added, not that an employee or leave request was created.

Leave Activity log filtered to Balance history entry — Created refers to the new history entry.

Open the event and inspect Changes. In this fictional example, Days is 5 and Kind is Adjustment. The entry was deliberately added for the demo; it is not an accrual grant or payroll payment.

Balance history event showing Days five and Kind Adjustment — This fictional five-day adjustment is separate from accrual.

Use Leave balances and policies to inspect the employee's ledger and current recorded allowance. The Activity log explains the action; the balance history provides the balance movement and its surrounding entries. Editing a policy does not rewrite earlier history.

Export the current results page

Select Export page CSV to export the loaded page of filtered events. Check your filters and pagination first: this action does not export every matching page or the full field-by-field comparison. Follow your workspace's rules when storing or sharing the file.

Troubleshooting

Problem	What to check
The Activity log is unavailable	Ask for Activity log read access; request approval or type-management access alone is insufficient.
No events appear	Clear restrictive filters, check the date range and record context, and review other pages.
A request is visible but its history is unavailable	Reading the request and reading its Activity log are separate permissions.
A note or value says Hidden	The value is withheld; do not treat it as blank or attempt to recover it from the screenshot.
Created appears for an adjustment	Check Entity type. A new balance-history entry is a creation event.
An old event differs from today's record	History describes the event at that time. Open the current request, type, or balance separately.
Loading fails	Use Retry when offered. A failed request is not evidence that there are no events.