Full System Audit Trail / User Activity Logs should be mandatory
CSuite would benefit greatly from having a comprehensive system-wide audit trail that logs all user activity across every module and function.
Recently we discovered grants had been entered using the “Create Spendable” function, but no user log was available to identify who performed the action. Without that information, the only way to determine what happened is to ask staff individually if they made the entry. When you have multiple staff entering grants, this is important. Not only from an operational standpoint, but from a chain of custody one. We have also had issues with profiles being marked inactive and no log showing who inactivated it. It seems like there are many areas where logs are not being generated.
For organizations that rely on CSuite for financial and grantmaking operations, this presents a significant gap in internal controls and auditability as well as inefficiencies in daily operations.
Ideally, every action in the system should generate a log entry, including:
User name
Date and timestamp
Module and record affected
Type of action (create, edit, generate spendable, delete, etc.)
A system-wide activity log would allow organizations to:
Maintain proper audit trails
Strengthen internal controls
Quickly troubleshoot data discrepancies
Identify the responsible user without staff-wide inquiries
Given the financial and compliance responsibilities of organizations using CSuite, comprehensive activity logging should be standard across all system functions.
Michele Jeican
shared this idea
-
Anna Wagner
commented
This is super important in EVERY area. We just ran into an issue where a staff member edited a grant type name, and no log was maintained for that action. Caused hours of headache to fix!
-
Kelli Glomski
commented
1000% agree this should be mandatory!
-
Alison Hawkinson
commented
We run into the same issues as well. Having an "audit trail" for every transaction is imperative.