AskHR360

AskHR360 is a multi-tenant HR and Health & Safety compliance platform built by AUXA. This page describes what it does and how it is put together. It does not report outcomes, because we are not publishing figures we cannot evidence.

The problem it addresses

An HR consultancy advising many employers has the same shape of problem every time: each employer needs its own policy set, its own incident register and its own audit trail, and none of them may see another’s. Handling that in documents and shared drives works until it does not, and the point at which it stops working is usually an audit.

The alternative is one system where every employer is a tenant. That is a different piece of software, not a tidier filing arrangement.

What the platform does

Policy library per tenant. Each employer holds its own set of policies with its own version history. A change to one tenant’s document is invisible to every other.

Incident register. Health and Safety events recorded against the employer, with the trail of who recorded what and when.

Audit trail as a feature. Not an application log. A record designed to be read by someone asking what happened, months later, who was not there.

Role-based access inside a tenant. An employer’s own staff see different things depending on their role, which is a second permission layer beneath tenancy.

Architecture and the decisions behind it

Row-level tenancy rather than a database per tenant. Every record carries a tenant identifier and every query is scoped to it. The alternative — a separate database per employer — gives stronger isolation and makes onboarding a provisioning task, backups an N-times problem and a schema change a migration campaign. Row-level keeps onboarding a configuration step. The cost is that isolation becomes a property of the code rather than of the infrastructure, so it has to be enforced in one place and tested rather than assumed.

Isolation enforced at the data layer, not in each query. Tenant scoping sits below the application code so a developer cannot forget it. Anywhere a query can be written by hand is somewhere a tenant boundary can be crossed by accident.

Append-only audit records. Audit entries are never updated or deleted. A record that can be edited is not evidence, and the whole point of the register is that it can be relied on later.

Versioned policy documents. A policy is not a file that gets overwritten. Superseded versions remain retrievable, because the question an audit asks is what the policy said at the time, not what it says now.

What we would do differently

Row-level tenancy is the right default and it puts a permanent obligation on the team: every new query path is a place the boundary could leak. If the platform were starting again with the same requirements, the tenancy scoping would be enforced by the database itself rather than by the application layer above it, which moves the guarantee from discipline to mechanism.

Related

AskHR360 is one of three platforms AUXA has built. The others are VisaFlow and ZenithMed AI. The service line is described on our software development page.

Frequently asked questions