System Configuration
The per-type form holding the panel login, activation code, recovery email and network settings — and where the user and engineer codes actually live.
System Configuration
Every system you look after has details an engineer needs to get into it again: the panel's admin login, the code that activates a cloud account, the email the manufacturer will send a password reset to, the IP address it answers on. System Configuration is where those live, and it asks for whatever that type of system needs — so the card looks different on a CCTV system than on a fire alarm.
You do not build the form. It comes with the system type.
Open a project, choose Systems under the Site group, pick a system. System Configuration is in the middle column, with the system type on a badge beside it. Press Edit to fill it in.
What you see
| On the card | What it means |
|---|---|
— |
Nothing recorded yet |
•••••••• with an eye |
A password, code or answer. Click the eye to reveal it, click again to hide |
| A copy button on every value | Copies it, and says Copied! — for typing long codes into a panel at the top of a ladder |
| Security questions | The question is always visible; each answer has its own reveal |
If a system type has no configuration of its own, the card does not appear at all.
What each type asks for
Anything with a network port — CCTV, Intercom, Access Control, Intruder Alarm — asks for the same core: an admin username and password, the verification code the unit was activated with, the reserved email it will mail a password reset to, three security questions, and its network settings (IP address, subnet mask, default gateway, DNS, MAC).
On top of that:
| System type | Also asks for |
|---|---|
| CCTV | Hik-Connect account email and password, HTTP / HTTPS / RTSP ports, ONVIF username and password |
| Intruder Alarm | ARC account number and receiver, ATS reference, cellular APN and SIM ICCID |
| Access Control | Server URL, operator / engineer login, database password, site key / facility code |
| Intercom | SIP server, extension and password, door release relay output |
| Fire Alarm | ARC account and receiver, commissioning date, cause & effect document reference, loops in use, detectors and sounders fitted, last full test date |
| Emergency Lights | Designer and qualification, battery system, minimum lux on the escape route, test schedule, last function and duration test dates |
| Networking | Subnet, gateway, DHCP server and pool, DNS, VLAN plan, management portal and its login, VPN type |
| Electrical Installation | Supply type and earthing arrangement, Ze, Ipf, supply protective device, main switch and bonding, last and next inspection, departures from BS 7671 |
Leave what does not apply empty. A Texecom panel has no cloud account; a residential alarm has no ARC. One form covers every make, and you fill in what the equipment in front of you actually has.
The user and engineer codes are not here
The codes that open the panel itself — User Code and Engineer Code — live on the system's own details, next to its location and key location, not in System Configuration. They are the same two fields for every system type, they are what the engineer sees on a job, and they are the only place those codes are kept. No system type asks for them a second time.
Devices have their own
A device — a camera, a call point, a distribution board — has its own configuration, and you reach it by editing the device rather than the system. The form is split in two: Configuration for the operational detail, Credentials for anything secret.
If a device type has no template yet, the form says so where its fields would be. That is a gap in the app, not something you can fill in from the page — tell whoever looks after it.
How it is stored
Anything that is a password, an access code, a site key or a security answer is encrypted before it is written down. Everything else — ports, addresses, references, dates — is kept as ordinary text so it can be searched and reported on.
Changing one of these is recorded in the system's history, so you can see that a password was changed and by whom. The value itself is never written into that history.