An anonymized example of a multi-tenant application for people, time, pay documents, and finance records. No client or measured result is named.

Anonymized

An example, not a named engagement

This page describes a kind of system. It does not name a client, an organisation, or a measured result.

The problem

A workforce leaves its records in more than one place: who someone is, when they worked, what was paid, and the money moving around the business. Administrators need the whole picture. Each person needs a narrower view of their own records. Those two audiences should not share a sign-in.

Approach

How the work is shaped

  • Start from the organisation, then the person
  • Separate administrator and employee sign-in
  • Keep time, leave, pay documents, and finance records in one application
  • A person approves leave and other changes that should not apply on their own
  • Pay documents are generated as files and kept with the record
  • Administrator sign-in can require a second factor

Architecture

How the pieces sit

  • Multi-tenant: each organisation’s records stay with that organisation
  • A relational database holds the records
  • Background jobs produce documents and other work that should not block a page
  • The interface is server-rendered, with a little client behaviour where a screen needs it
  • The same screens can be opened from a mobile shell

Stack

The kind of tools

  • Ruby on Rails
  • PostgreSQL
  • Redis
  • Background jobs
  • Hotwire

A similar workflow

Describe the job. These pages are examples of a build. They do not report a result.