Audit Logs

Review workspace activity, filter important events, and export activity history for admin review.

Audit Logs help admins review important activity in Edmissa. Use them when you need to understand who made a change, when it happened, what type of action it was, or whether a sensitive admin action needs review.

Audit Logs are most useful when admins review them regularly, not only after a problem is reported.

What this guide helps you review

Area	What Audit Logs help with
User activity	Review sign-in activity and user actions when available.
Data changes	Check changes related to student profiles, applications, Leads, documents, or tasks when logged.
Admin actions	Review changes to users, roles, settings, security, and integrations.
Investigation	Filter by date, user, action, or type to narrow a question.
Export	Export activity history when a manager or owner needs a copy.

Before you start

Prepare the question you are trying to answer.

Item	Why it matters
Date range	A narrow date range makes the log easier to review.
User	Knowing the user helps you filter quickly.
Action type	Knowing whether you are looking for login, update, export, or settings activity helps narrow results.
Related work	Student profile, application, Lead, or document context can help confirm whether the event is relevant.
Review purpose	Decide whether the review is routine, support-related, or part of a security check.

Open Audit Logs

Use this path when you want to review activity:

Open Settings.
Open Audit Logs.
Confirm the page title is Audit Logs.

The direct route is /t/settings/audit-logs.

The page includes:

Control	Use it for
Date range	Limit the review to the period that matters.
All users	Filter to one user when investigating a specific account.
All actions	Filter by action when you know the kind of activity you need.
All types	Filter by event type when available.
Export	Download activity history for review or sharing with an owner or manager.

Review routine activity

Use Audit Logs regularly for admin review:

Open Audit Logs.
Select the date range you want to review.
Start with all users, actions, and types.
Look for unusual patterns, sensitive admin changes, or unexpected activity.
Narrow the filters when something needs more review.
Export only when a copy is needed.

Routine reviews can help catch access issues, unusual account activity, and configuration changes before they become confusing for users.

Investigate a specific question

When a user reports an issue, use a focused review:

Question	Useful filters
Who changed a setting?	Date range, action, type, admin user when known.
Why did a user lose access?	Date range, user, role or user-management actions when available.
Was a document or application updated?	Date range, action, type, and related user when known.
Was a token or integration changed?	Date range, action, API or integration type when available.
Did a user sign in recently?	Date range and user.

Audit Logs show recorded activity. They do not replace user access review, role review, or workflow troubleshooting. Use the log as evidence, then review the related settings page if a change needs correction.

Export Audit Logs

Use Export when an owner, manager, or compliance review needs a copy of the activity history.

Before exporting:

Set the date range.
Apply user, action, and type filters if the export should be focused.
Confirm the export does not include more information than needed.
Store the export in an approved secure location.
Share it only with people who need it for the review.

Exports may contain sensitive activity details. Treat them carefully.

Recommended first version

For a study abroad agency, start with these review habits:

Review	Suggested use
Weekly admin review	Check recent admin actions, user changes, and unusual activity.
Access issue review	Check user, role, and location changes when someone loses access.
Security review	Check sign-in, password, session, token, or settings activity when something looks unusual.
Integration review	Check connected-tool activity after adding or changing an integration.

Choose one admin owner for regular review. A log that nobody checks will not help the team improve.

Guide	Use it for
Security and audit	Understand how audit review fits with security settings, session policy, and API access.
Session Policy	Configure timeout and step-up checks.
API Access	Manage tokens used by trusted external tools.
Users	Review accounts, passwords, active status, and sessions.
Roles	Review role changes and permission setup.
Access and permissions troubleshooting	Diagnose missing pages, disabled actions, or unexpected visibility.

On this page