[Feature] Log-in and other Activity Logs

[sushantmnair]

Target Module

General (cross-module)

Description

Whatever actions users perform, like logging-in, scheduling an interview, updating their profile, etc. should be logged.

Use Case

Security: All actions are accounted for
Transparency: Admin can come to know who did what
Troubleshooting: The root cause of issues can be better identified

Proposed Solution

Whatever action is performed by ANY user, add it to a logs table. This table should be visible ONLY to the website admin.

Benefits

Security: All actions are accounted for
Transparency: Admin can come to know who did what
Troubleshooting: The root cause of issues can be better identified
Compliance: This would add to Horilla's credibility and is a non-negotiable requirement for production-grade systems.

Additional Information

Note: I request the development team to take this up at high priority, as logs and transparency are a non-negotiable requirement for any production-grade system. I look forward to the feature getting implemented.

Labels

enhancement

Priority

High

Submission Checklist

• I have searched for duplicate feature requests
• I have provided clear and concise information

[horilla-opensource]

Hi @sushantmnair,

Thank you for the detailed feature request and for highlighting the importance of activity logs for production-grade systems.

We’d like to clarify that Horilla already records activity logs internally for many user actions (such as create, update, delete, login-related activities, etc.). These logs are stored and are partially visible today—primarily through the Audit Log / LogEntry model in the admin area, as shown in the screenshot above.

That said, you’re absolutely right that:

• Logs are not consistently exposed across all functional areas in the UI
• Some actions are logged but not easily discoverable or centralized for admins

If you need to access or list all recorded activities right now, you can directly use the LogEntry / audit log model to query and display records (for example, via Django Admin or a custom admin-only view). This model already contains details like:

• User
• Action type (create/update/delete/access)
• Resource
• Timestamp
• Field-level changes (where applicable)

We agree that improving visibility, consistency, and admin-only access to these logs across modules would significantly enhance security, transparency, and compliance. We’ll treat this as an enhancement to surface and standardize existing logs, rather than starting from scratch.

Thanks again for the thoughtful proposal and for pushing Horilla toward stronger production readiness. 🙌

Best Regards,
Team Horilla