System Logs & Audit Trail

Flowtly maintains a system log and audit trail that records key actions taken across your organisation's projects, clients, people, and resourcing data. This record helps administrators and managers understand who performed an action, what was changed, and when it occurred, supporting accountability and compliance across the workspace.

What Is Recorded

The audit trail captures activity such as changes to organisation settings, updates to client and project records, adjustments to people and resourcing data, and other significant actions performed by users within the workspace. Each entry typically includes the user responsible for the action, the type of action taken, and the time it occurred.

Viewing the Audit Trail

Authorised users can review the audit trail to trace the history of changes within a given area, such as an organisation, project, or client record. This allows teams to confirm that data was updated correctly, investigate unexpected changes, and maintain a clear record of activity over time.

Access and Permissions

Access to system logs and audit trail information is controlled by role permissions, and viewing the audit trail requires an audit or management role. Organisation administrators see records across the organisation. Managers see the records their role is responsible for, so a project manager and a people manager each see the activity that belongs to their own area rather than the whole organisation.

Team members who hold neither an audit nor a management role do not have access to the audit trail, and the audit log page is unavailable to them. Audit entries name the person who performed each action, so access is kept to the roles that need it for accountability and compliance. If you need to review activity for an area you are responsible for, ask an organisation administrator which role covers it.

Example use cases

• An organisation administrator reviews the audit trail to confirm which user updated a client's billing details.
• A project manager checks the log history for a project to understand when a status change was made and by whom.
• A resourcing lead investigates the audit trail after noticing an unexpected change to a team member's allocation.
• A compliance reviewer examines activity across people records to verify that data handling followed organisation policy.
• An invoices manager checks who moved an invoice line to a different project, and when, after a project's income changed unexpectedly.