System Logs Module
Reading the Audit Trail
A read-only record of real events that already happened elsewhere in the app — sign-ins, role changes, settings updates, imports, and more — written automatically, never typed in by hand.
Start here
Before you start
There’s nothing to configure. Entries appear here the moment a real action happens somewhere else — a sign-in, a role change, a settings save, an import commit, a Super Admin grant. There is deliberately no “create log entry” button anywhere in the app: a hand-authored audit trail isn’t trustworthy as one.
Most entries belong to whichever company was active when the action happened, and only show up while that company is active. A handful of genuinely global events — sign-ins, failed sign-in attempts, company deletion, Super Admin grants, viewing-as-another-user, and password resets — aren’t tied to any one company, so they show up regardless of which company you have active.
What’s in here
Reading the log
This screen is split into tabs. Activity is the default one, and the one described in this section — the day-to-day business audit trail. A separate Login Attempts tab holds every sign-in attempt on its own (see Reading the Login Attempts tab); Accounts lists every user with real access to the app, install-wide; and Visitor Chat is the permanent record of every conversation from the public website’s chat widget that needed a human reply — an escalation drops a notification in the bell for every WP Admin, plus anyone picked under Settings → Login Page → “Who can see and reply to escalated visitor conversations.” Clicking that bell notification opens a Website Visitor conversation right inside Team Chat, alongside your regular chats — that’s where you actually reply, so handling these doesn’t have to fall on an Administrator alone; this tab stays the full log of what was said.
On the Activity tab, each row shows a Level, a Source (which module logged it — auth, users, settings, import-export, and others), a plain-language message, who did it (actor), and when. Newest entries are always first.
Individual rows can be removed by an Administrator if genuinely needed — there’s a confirmation prompt first, and no undo after that.
Filtering & searching
Use the search box to match against the message text, or the Level and Source dropdowns to narrow the list. The Source list is built from whatever sources actually appear in your data — it isn’t a fixed menu, so a module that’s never logged anything for this company won’t show up as an option yet.
The KPI cards
| Card | What it’s measuring |
|---|---|
| Total Events | Count for this view, with a 30-day trend line and %-change against the prior 30 days. |
| Errors / Warnings | Raw counts at each level, all-time. |
| System Health | 100% minus the share of all events flagged Error or Warning — a real ratio computed from your own log rows, not a fabricated score. |
| Most Active Actor | Whoever’s name appears on the most logged events. |
| Total Accounts | Every user with real access to the app across the whole install — every company membership plus every Super Admin. Not scoped to one company. |
| Total Companies | How many companies exist on this install, period. |
Who’s Online
At the top of this screen, above the tabs, sits a live roster of everyone who’s had the app open recently — across every company, not just whichever one you have active. There’s nothing to turn on: it’s built entirely on presence pings the app already sends quietly in the background while a browser tab is open, the same signal Team Chat’s own presence already relies on.
A green dot and Online now means active in the last 5 minutes; anyone else seen in the last 30 minutes still shows up as idle with a “last seen” time, and drops off the list entirely once it’s been longer than that. Each row also shows the person’s IP address, a resolved Country, their sign-in time, and how long they’ve been online this session. The panel refreshes on its own — no need to reload the page.
Common tasks
Reading the Login Attempts tab
Every attempt to sign in to the site — successful, failed, or blocked — has its own tab, kept separate from the Activity log so sign-in and hacker-hunting activity doesn’t get buried among routine business actions. “Blocked” rows are a direct hit on the real WordPress login page while your hidden-login URL is turned on (see the Settings guide) — the visitor never even got as far as entering a password.
In place of the Activity tab’s Source column, this tab shows a Country column, resolved from the attempt’s IP address. That lookup happens the moment you open this tab — never at the instant someone actually tries to sign in — so a flood of scanner traffic hitting the login page can never slow down a real sign-in for anyone. Countries resolve a handful at a time as you view the page; on a first look after a burst of new activity, a few rows might briefly show no country until you refresh.
Common tasks
Investigating a failed sign-in
Someone says they couldn’t log in, or you want to check for repeated failed or blocked attempts.
Open the Login Attempts tab
Sign-in, failed-sign-in, and blocked attempts all live here, regardless of which company is active.
Search the username, IP, or country
The message includes the exact username or login that was attempted, and the Country column can help you spot attempts from somewhere your real team never signs in from.
Check the timestamps
A cluster of failed attempts close together is worth following up on directly with that person.
Auditing a role or access change
Filter Source to users to see every role change, user addition/removal, Super Admin grant, password reset, and view-as session in one place — each logged the moment it happened in Users & Roles, with the actor’s name in the message.
Reference
Log levels
| Level | Typical meaning |
|---|---|
| Info | A routine, expected event — a sign-in, a settings save. |
| Success | Something completed the way it should — a user added, an import committed. |
| Warning | Worth a second look — a role change, a failed sign-in, an account deletion. |
| Error | Something genuinely went wrong. |
What this module doesn’t do
Only the modules that explicitly call the logger produce entries — this is a curated audit trail of significant events (sign-ins, access changes, settings saves, imports), not a full field-by-field history of every record edit across the app.
Entries are kept indefinitely by default — there’s no automatic expiry, and no built-in CSV/PDF export for compliance archiving.
Deleting a company permanently deletes its log history along with it — there’s no separate retention for audit records once the company itself is gone.