Skip to main content

Audit Trails & System Logs

The EducaSphere Backoffice Portal maintains a comprehensive audit trail of all significant actions performed within the platform. This ensures transparency, accountability, and security for all administrative operations.

Audit Logs Dashboard

The Audit Logs page provides a real-time feed of system activity across all organizations (tenants).

Audit Logs Placeholder Hint: The logs table displays the User, Action performed, Resource affected, Severity, and Timestamp.

Log Severity Levels

To help prioritize reviews, logs are categorized by severity:

  • Critical/Error: Security-sensitive actions, such as failed logins or unauthorized access attempts. (Color: Red)
  • Warning: Significant changes, such as tenant suspension or module disabling. (Color: Yellow)
  • Info: Routine administrative actions, such as user creation or profile updates. (Color: Blue)

Searching and Filtering

Administrators can use the advanced filtering toolbar to isolate specific events:

  • Action Filter: Filter by specific operation (e.g., LOGIN, CREATE_TENANT, UPDATE_PLAN).
  • Severity Filter: View only Critical or Warning level logs.
  • Date Range: Select a specific "Start Date" and "End Date" to view historical activity.
  • Search: Search for specific users (name/email) or resource identifiers.

Log Entry Details

Each log entry captures several key data points:

User Information

  • Administrator: The name and email of the admin who performed the action.
  • IP Address: The network identifier from which the action was initiated.
  • User Agent: The browser or device used to access the portal.

Action Details

  • Resource: The system component affected (e.g., Tenant, School, User).
  • Action: The specific operation performed (e.g., DELETE, UPDATE, SUSPEND).
  • Metadata: Detailed technical information about the change, including "before" and "after" values where applicable.

Activity Statistics

The top of the Audit page provides an overview of system health and activity:

  • Total Logs: The historical count of captured events.
  • Critical Events: A count of security-related warnings from the current period.
  • Active Admins: The number of unique administrators who have performed actions today.

Best Practices

  • Regular Reviews: Monitor "Critical" and "Warning" logs daily to identify suspicious activity.
  • Troubleshooting: Use the audit trail to trace the origin of configuration changes that may have affected system behavior.
  • Compliance: Utilize the export feature (CSV/PDF) to provide audit trails for regulatory compliance or institutional reporting.

This concludes the documentation for the Backoffice Portal. For tenant-level documentation, please refer to the Frontend Guides.