Initial setup
This page guides you through the setup after the installation, from the first sign-in to the first modules.
As of: November 2026, COD 3.8.6
Documentation
First sign-in
The setup wizard creates two accounts.
| Account | Purpose | Sign-in |
|---|---|---|
| First superadmin | first administrator of the installation | with the e-mail address from the wizard |
| Manager account | built-in emergency and administration account. The only account that enables modules for the tenant | with TOTP |
- The wizard shows the QR code for TOTP and a key exactly once. Set up TOTP in an authenticator app right away and keep the key in a safe place.
- The e-mail address of the manager account cannot be changed later.
- The interface is in English.
- A session lasts up to 7 days.
HTTPS
HTTPS is mandatory for every access. COD sets its session cookies for secure connections only. Without HTTPS, sign-in only works locally on the COD server.
| Approach | Setup | Note |
|---|---|---|
| Certificate authority of the installation | in the setup wizard | COD brings its own certificate authority for this |
| Your own certificate | "Backend config", card "TLS": provide certificate, key and CA | The certificate is issued for the name under which users open COD |
| Reverse proxy | proxy in front of COD, enable "trust proxy" in COD | The proxy must pass WebSocket (terminal) and server-sent events (Passkeepr). You receive a sample configuration as part of the project. |
Note: Saving in "Backend config" restarts COD for all users. If you do not confirm the change within 120 seconds, COD returns to the previous setting.
Enable modules
- Sign in with the manager account.
- Open "Admin Area > Tenant > Modules".
- Select the licensed modules and save.
- Sign out and sign in again. Only then does COD show the modules.
- Roll out the modules per location. The procedure is under Installation: roll out modules.
Order of the setup
Set up a new installation in this order. Later steps build on earlier ones.
- Organisation (tenant) and modules, see Enable modules
- Locations
- Roles, see Roles and rights
- Users
- Directory connection, see LDAP and Active Directory
- Mail per location, see Mail per location
- Asset catalogues: types, manufacturers, families and models. Do not rename the built-in type "Firewall". See Inventory
- Module addresses per location under "Location > Module URLs"
- Naming scheme, see Names and addresses
- Assets and network objects, see Inventory and Network
- Monitoring, see Monitoring
- Firewall, see Firewall
- Captive Portal, see Captive Portal
- Ansible configuration, see Automation
- GRC, see GRC
- Optional integrations, see Integrations
- Branding
Roles and rights
- Agree with your partner which roles you create.
- The location is the smallest boundary for rights and data. There are no rights per device.
- Branding, asset catalogues and asset names apply to the whole installation. Asset names are unique across the installation and at most 50 characters long.
- Only the manager account enables modules.
LDAP and Active Directory
- COD opens the connection to the domain controller.
- LDAPS is enabled by default ("Use LDAPS"). Store the CA certificate of your directory service in COD.
- The connection fields exist per tenant and per location. Domain aliases are possible.
- You grant rights through a directory group that you enter on the role.
- Keep a local access for a directory service outage, for example the manager account.
Mail per location
The mail setting belongs to the location. In practice it is required.
COD uses it to send:
- messages through the feedback channel
- reachability messages
- certificate messages
- invitations and links to set a password
Also note:
- "Send test e-mail" in the location's mail settings shows the mail server's response.
- Backup and NAC have their own mail settings for their messages. The Backup instance reports failed backups by mail if mail is enabled there.
First modules
The recommended order is Inventory, Network, Monitoring, Backup. The inventory is the basis for all other modules.
Inventory
| What you do | How you see that it works |
|---|---|
| Check the catalogues (type, manufacturer, family, model). Create assets manually, by CSV import or by import from i-doit | The assets appear in the location's asset list. |
See Inventory and CMDB import.
Network
| What you do | How you see that it works |
|---|---|
| Set the network flag on the asset and choose the right manufacturer and model. Create a network object with address, SNMP community and SSH access. Enable "Routing" for layer 3 | Ports and port status appear. Port status is refreshed every 30 seconds. No object shows "port discovery failed". The layer 2 map shows links between devices whose LLDP system name matches the asset name |
See Network and MikroTik and Preparing network devices.
Monitoring
| What you do | How you see that it works |
|---|---|
| Enter the Zabbix connection per location: API address, API token, optionally a filter on host groups. The token needs write rights on its own server groups | Hosts and problems from Zabbix appear in COD. The list of unmonitored assets shows which asset still lacks a Zabbix host. The nightly sync links assets and Zabbix hosts with the same name |
See Monitoring.
Backup
| What you do | How you see that it works |
|---|---|
| Roll out Backup per location. Create a host with address, user and password, choose a template (Download, Command or MariaDB dump), set a schedule | After "Execute Now" or the first scheduled run, a version with a timestamp appears. If a run fails, the host shows ERROR and the error is visible in the overview |
See Backup.
Customers and partners receive the list of connections and firewall rules as part of the project.