Data & Insight

Data & Insight is what turns a long list of punches into something a manager can act on. Dashboards show the live state of the workforce, filters let you cut it by department or site or period, and exports hand the same numbers to whatever else your business runs on.

It is also where the system talks to you rather than the other way around. Notifications carry the things worth knowing without anybody logging in to look, and the AI layer flags anomalies in the data that a person scanning a report would plausibly miss.

The Dashboard answers the questions asked most often: who is in, who is late, what overtime is running, how much leave is booked for the weeks ahead. It is built to be read in a few seconds rather than studied, which is the right design for a screen people open ten times a day.

My Notifications is the per-user inbox: approvals waiting, anomalies flagged, changes that affect this person's team. It is worth clearing rather than letting it accumulate, because a full queue stops being a signal.

Settings decide what gets sent and how it arrives: email, WhatsApp or the mobile app. Route by role rather than by individual where you can, so a change of supervisor does not mean rebuilding the rules.

Be conservative at the start. It is much easier to add a notification people ask for than to win back attention after everyone has muted the channel.

Import brings existing data in, which in practice means the first week of any implementation. Employees, positions, departments and historic attendance can all be loaded rather than typed.

Import a sample of ten rows before importing two thousand. Every mapping problem that will bite you shows up in the first ten.

Export produces files for the systems Maltese businesses commonly run alongside Communicator-Cloud: PayDay, Pyramid and Indigo 1 to 4. Each has its own expected format, and the export is built to match rather than to be adjusted by hand afterwards.

System Logs record the platform's own activity: calculations that ran, syncs that completed or failed, jobs that queued. It is the first place to look when something did not happen rather than happened wrongly.

Event Logs record human activity: who changed what, when, and from where. During an audit this is the evidence that attendance and payroll data was not quietly adjusted, which is usually the question being asked.

Global Settings holds the rules the rest of the system reads: company defaults, employee defaults, attendance behaviour and costings behaviour. Changes here reach everywhere, so treat it as a considered change rather than an experiment, and note what you changed and why.