The platform

People, offices, institutions, appointments

The data model keeps four things apart. The person is John Smith. The office is “director” or “minister”. The institution is the university, the bank, the ministry. The appointment is the last two combined: director of that institution, with a start date and, where it applies, an end date.

One person can hold several appointments at once, and invitations use the most senior of them. When somebody moves on you close the appointment and open another: the person’s record stays as it is, and the history of who held that office at last year’s ceremony is not lost.

An unlimited number of protocols

Civilian dignitaries are ordered by institutional office. Military ones by appointment, rank and length of service. Create as many protocols as you need, and the quickest way to build a new one is to copy an existing protocol and edit the copy.

Multiple sites, separate data

If your organisation has several operating sites, each one works independently: ceremonies, registry, appointments and protocols stay isolated per site, and each user sees only their own. The administrator is the only one with no site restriction and can see everything.

A new site inherits the administrator’s registry, so it starts working straight away instead of from an empty archive.

Snapshots, dumps and restore

Three tools for keeping history, all in the administrator’s hands:

• Snapshot: a picture of the data on a given date, to see exactly how things stood at that moment
• Dump: a complete backup of structure and data in a single file
• Restore: recovery in a few clicks, with the backup history always available

Two-factor authentication

An optional module. It adds a six-digit temporary code to sign-in following the TOTP standard, generated on the user’s own device and valid for a few seconds. It works with Google Authenticator, Microsoft Authenticator and any compliant app.

It uses the users and roles already configured: no external service, no SMS, no data leaving the platform.

Working offline

The standalone version lets you work with no connection, from any computer. You generate it from the administrator area, take it where it is needed, and realign it to the central system with backup and restore when you are done.

It matters when a ceremony is prepared at a site with no network, or when the hall is somewhere the connection does not reach.

Where the data lives

Three deployment options, and for many of our clients this is the question that decides everything: cloud hosted by us on a dedicated subdomain, on-premise on your own servers inside your own network, and standalone for offline work on a single computer. If your policies require that data never leaves your infrastructure, on-premise answers exactly that.