HR analytics without AI judgment of your people

Companies that have outgrown the standard reports in the free core and want to compose their own: joining headcount to attrition to leave to hiring in one view, saving it, and having it arrive by email every month. The buyer is a people lead or a founder who is currently rebuilding the same spreadsheet each quarter. It is worth having once you have several modules running and questions that cross them. If your questions are answered by the core standard reports, which already export to CSV and can already be scheduled, you do not need this module yet.

No. The module composes, aggregates and visualises; it ships no AI evaluation of people and no automated narrative. There is no attrition-risk score, no performance prediction and no sentiment analysis, and there never will be under the commitment recorded in our claims register. What you get instead is a dataset catalogue, a report builder over a closed vocabulary of dimensions and measures, sanctioned cross-module joins, dashboards, trends and scheduled delivery. The judgment stays yours.

A paid plan first, because paid modules cannot be enabled on the free plan. Beyond that there is almost nothing to configure: the dataset catalogue and its permission projection are provided rather than modelled by you, so the setup is composing the reports and dashboards you want and choosing who receives which schedule. What determines how useful it is on day one is which other modules you already run, because each one contributes its own datasets to the catalogue. Enabling analytics on a workspace using only the core gives you the core datasets and nothing more, which is worth knowing before you buy.

It ships no AI narratives, no automated insights and no predictive scoring of individuals. It cannot widen anybody’s reach: a composite report inherits the gate of the module it reads from, so the engagement survey minimum group size and the compensation bucketing survive every join. It writes nothing, because analytics is a read product and adds no path into another module’s data. It is not an embedded third-party business-intelligence platform, and it blends in no external data. And it gives you no raw SQL access to your workspace.

It reads them, under the viewer’s own permissions, and never around them. Every widget runs as the person looking at it rather than as the person who built it, so a shared dashboard can narrow what someone sees and can never widen it: one schedule can honestly tell two recipients different things, and a compensation figure stays a band-placement bucket for anyone without compensation clearance. Each module you enable contributes its datasets to the catalogue and its gates travel with them. It is worth being clear about what is not exclusive to this module: the core standard reports, their CSV export and scheduled delivery of them are part of the core on every plan. What this module adds is the custom builder, the cross-module joins and the dashboards.

The dataset catalogue, custom reports, dashboards and their schedules stop being reachable, and billing stops at the end of the current period rather than on the day. The core standard reports are unaffected, because they were never part of this module. Your saved report and dashboard definitions are retained on a schedule and restored if you re-enable within that window. Nothing about your underlying data changes, since analytics only ever read it: turning the module off removes a lens, not a record. A full workspace export is unaffected either way.