Control and security
BMMS is built to keep an orderly record: who did what, in what order, and what can no longer be changed.
Roles and approvals
Each user has a role: user, manager, controller or administrator. Approvals follow the routing described under How it works. The administrator controls who can use the system and with which role.
Locks
A finalised agenda, a recorded attendance and confirmed minutes cannot be changed by mistake. The software refuses and says why.
Audit trail
Changes to meetings, agenda, minutes, users and settings are recorded with the user and the old and new values, and can be reviewed on the Audit Trail page.
Protected accounts
One system administrator account cannot be edited, deactivated or deleted, and takes no part in approvals. The last active administrator and the last active controller cannot be removed.
Inactive users
A deactivated user cannot sign in, is left out of lists and receives no new alerts or mail. Their earlier records are kept.
Errors without details
When something goes wrong, the user sees a short message and the technical detail goes to an error log on your server. Internal folders such as logs, generated PDFs and database backups cannot be opened from a web address.
Your data on your server
BMMS is installed on your own server and uses your own SQL Server database. Network settings, certificates, backups and access to the server remain under your control.
Clean start for training
An administrator can return a training copy to a clean state. The action asks for the database name to be typed, and records that it was done.
BMMS does not make a claim of legal validity or of compliance with any regulation. Check your own requirements with your advisers.
See it working
Write to us with your questions about control, installation and requirements.