How to use the list
The list is meant for the last week before go-live, but it is worth closing some items earlier, because they require the agreement of other departments. Each item has an owner on the IT side and evidence that stays in the rollout documentation. A missing piece of evidence means the item is not closed, even if everything works.
The instance is isolated: it has its own database and its own email system and runs in Docker containers, also on the customer's server. This way the list covers one environment, not the whole infrastructure of the plant.
Accounts and authentication
The first area is accounts. Feeding accounts from the user directory is not a standard, because the feature documentation does not describe it, so the account list comes from the plant's preparation or from an agreed option. An account whose email already exists is not linked automatically with the account from the portal: it requires a password or a badge at the first login.
MFA is an option enabled per installation, off by default. The email code is valid for 10 minutes with a limit of 5 attempts, and a trusted device remembers the verification for 7 days. The decision to enable it and on trusted devices is recorded before go-live, together with information for users.
MFA parameters to agree before go-live
Sending email
The plant's email may flag system messages as spoofing when they arrive from an external domain, and the display name is the company name. The shared sending address sits in the InnerWeb domain, the SPF, DKIM and DMARC records remain unchanged, and only the displayed sender name and the Reply-To address change.
Test before go-live: send system messages, such as password reset and MFA code, to mailboxes in several roles and check that they reach the inbox and not the spam folder. System messages have no Reply-To, and the footer appears in 6 languages.
Monitoring and logs
Error reports go to one shared Sentry project. An internal limit on reports protects the project from being flooded with repeated entries, but security alarms are not silenced. IT checks that the instance runs a release version matching the deployed image.
The audit trail covers entities changed by a person. Timestamps use the Europe/Warsaw time zone from October 2026, and earlier entries were not recalculated, so when analysing older data this has to be kept in mind.
Network and alarms
If the host has blocked outbound traffic, alarm webhooks are stored durably and an external poller picks them up over an inbound channel. Before go-live one full alarm test is run, from the event to the notification, and its result is recorded as evidence.
Checklist
Video
Frequently asked questions
How long does it take to tick off the list?
It depends on the scope. Most items are short checks, and the longest is usually agreeing the account list and email with other departments.
Are all items mandatory?
No. MFA and feeding from the directory are options, but the decision about them is recorded regardless of the result.
Is changing SPF required?
No. The SPF, DKIM and DMARC records stay unchanged, because only the displayed sender name and the Reply-To address change.
Sources
Let us go through the list with IT
Let us arrange a short meeting with your IT department: we will tick off the items and record the open decisions with an owner and a deadline.
Let's talk