What follows from the feature documentation
The system offers two MFA factors: a 6-digit email code valid for 10 minutes with a limit of 5 attempts, and TOTP compatible with Google Authenticator. MFA is an option switched on per installation and is off by default. A trusted device remembers the verification for 7 days thanks to a cookie, so during that time the user does not have to enter a code again on that device.
The API and mobile apps use JWT: the access token is valid for 12 hours, and the refresh token for 7 days and is single-use. This sets the rhythm in which an ordinary user meets the login screen. These parameters determine the number of logins per year, which in turn determines the support load.
Assumptions of the sample calculation
We assume a plant with 500 users who use the system once per working day for 48 weeks a year. A helpdesk ticket takes 15 minutes at a sample rate of 100 PLN per hour, which is 25 PLN per ticket. We assume 2 password resets per user per year and 0.5% of MFA codes reported as a problem.
We compare the two MFA variants by the number of code requests. Without a trusted device the user enters a code at every login. With a trusted device valid for 7 days, the user enters a code once per working week. These are sample assumptions, not a measurement from any specific plant.
Yearly cost of helpdesk tickets about MFA codes
Result: password resets
Password resets amount to 1 000 tickets a year (500 users with 2 resets each), which is 25 000 PLN a year at 25 PLN per ticket. This cost does not depend on MFA. MFA changes the number of tickets about codes, not about passwords.
Result: MFA codes without and with a trusted device
Assuming 5 logins a week over 48 weeks, a user has 240 logins a year. Without a trusted device this gives 120 000 code requests a year for 500 people. With a trusted device the code is required once a week, that is 48 times a year per person and 24 000 requests in total.
At 0.5% of tickets about a code problem, this gives 600 tickets a year without a trusted device (15 000 PLN) and 120 tickets with a trusted device (3 000 PLN). The difference of 12 000 PLN a year is an 80% lower cost of handling codes, if the assumptions are confirmed.
What changes the result in practice
A trusted device lowers the cost, but it also reduces how often verification happens, so the plant should decide what risk it accepts on shared computers. On terminals used by many people, remembering the verification is not a good choice.
The cost also depends on email quality: when the message with the code lands in spam, the number of tickets grows. The system's email uses a shared sending address in the InnerWeb domain, and the SPF, DKIM and DMARC records remain unchanged, so it is good practice to add this domain to the trusted list on the plant side.
Sample calculation of login support
| Parameter | Value |
|---|---|
| Number of users | 500 people |
| Logins per person | 240 per year |
| Password resets | 2 per person per year |
| Cost per ticket | 25 PLN |
| Tickets about codes | 0.5 % of code requests |
Result: Password resets: 25 000 PLN a year. MFA codes: 15 000 PLN without a trusted device and 3 000 PLN with one, a difference of 12 000 PLN a year.
Note: Sample calculation on our own assumptions. Replace the values with data from your own helpdesk; it does not describe a specific plant.
Video
Frequently asked questions
Does MFA increase the support cost?
It increases the number of code requests, but the cost depends on trusted devices and email quality. In the sample calculation, a device trusted for 7 days lowers the number of requests by 80%.
Is a trusted device suitable for a shared terminal?
It is not a good choice. The 7-day verification memory is tied to a cookie, so on a device used by many people it increases the risk.
Do the figures in the calculation apply to a specific plant?
No. They are sample assumptions, which the plant replaces with data from its own helpdesk.
Sources
Let's count the login support for your plant
We will put data from your helpdesk into the calculation and check whether MFA with a trusted device makes sense in your plant.
Let's talk