Who these recommendations are for and why
The recommendations are addressed to the system administrator on the vendor or plant side who prepares the demonstration instance before a demo for the board. A mistake at this stage can be costly for reputation: an e-mail with an SOS alarm reaching a real employee or manager breaks trust faster than a failure.
The system sends push and e-mail notifications, and events may trigger an external webhook. Since the demo simulates alarms, every account taking part in the scenario must be isolated from the outside world.
Recommendation 1: addresses in a domain reserved for testing
Demonstration accounts should have addresses in a domain reserved for testing, such as example.invalid. Such a domain is never assigned to a real mailbox, so even if the demo sends an e-mail, it will not reach anyone.
Do not use the business addresses of employees or your own private addresses. It happens that the person preparing the demo adds their own address for the convenience of testing and then forgets about it before the demo for a client meeting.
Sample set of accounts in the demo
Recommendation 2: roles matched to the scenario
Prepare only as many accounts as there are roles in the scenario. A typical set is the employee account whose watch triggers SOS or stillness, the account of the person issuing the permit, and the dispatcher account watching the map.
Name each account so that the presenter does not have to think about who is logging in. Generic names are enough: hall employee, issuer, dispatcher.
- employee with a watch or the app: source of SOS and stillness,
- permit issuer: creates the work in the wizard,
- dispatcher: watches the isometric map and alarms,
- visitor: only if the scenario includes registration at the kiosk.
Recommendation 3: the password as a variable, not a file
Store the password of the demonstration accounts as a CI/CD variable, not in the repository or in a configuration file. This way the password does not end up in the code history and can be changed without modifying the repository.
The rule also applies to accounts that exist only for a few hours. A temporary password in a text file is often later copied into further environments.
Recommendation 4: a database backup before changes and marking of data
Before changing data on the demonstration instance, make a database backup: a gzip-compressed dump and a check of its file size. An empty or suspiciously small file means the backup failed and must not be treated as protection.
Mark the locations and transmitters of the demo with an external identifier. Then after the demo you clean up only your own data, and you delete the markers of the finished demo only for demonstration accounts.
How to check that the accounts are ready
Before the meeting, log in with each account, trigger one event and check that it appears on the map. Confirm that no message has left the environment: the test mailboxes do not exist, so the check consists of reviewing the sending logs, not an inbox.
Write down which accounts were used. After the demo, change the password, and delete the demonstration data marked with the external identifier according to the procedure for stopping the demo.
Video
Frequently asked questions
Why example.invalid?
It is reserved for testing and never points to a real mailbox, so notifications from the demo do not reach anyone.
Where should the password of the demonstration accounts be kept?
In a CI/CD variable, not in the repository or a configuration file. After the demo it is worth changing the password.
Is a database backup needed for the demo instance?
Yes. Before changing data, a gzip-compressed dump is made and its size is checked, so that it is possible to return to the starting state.
A safe demo with no risk to people
We will prepare the demonstration instance and test accounts, so you can show the system to your board without sending notifications to real people.
Let's talk