Every financial action is recorded against the account that performed it, so each person needs their own login — a shared account cannot answer who did this. A role sets the starting permissions; individual permissions below override the role in both directions.

Removing a tick here also removes the ability: the same permission is enforced inside the database, so an officer who is denied an action is denied it whether they use this application or not.

Creating an account and resetting a password are Super Admin actions. An officer with Manage users and permissions can set roles and permissions on people who already have a sign-in, but cannot mint or re-key a credential. Forgotten passwords come here too: this deployment sends no email, so Reset Password below — a temporary password handed over in person — is the way an officer gets back in.