Email verification TL;DR
As of 16th October 2026, Kato requires an extra verification step when you sign in with your email address and password. This process ensures your account has an additional layer of security - protecting your deal data and customer information.
After you enter your password, we’ll send a verification code to your registered email address. Enter the code in Kato to complete your login.
Q. What is changing?
A. If your organisation uses email and password to access Kato, you’ll be asked to verify your email address when you log in. SSO customers are not impacting by this change.
The login process will be:
Enter your email address and password as normal.
Kato sends a verification code to your registered email address.
Enter the code on the verification screen.
Once the code is verified, you’ll be logged in.
Q. Why is Kato introducing email verification?
A. Email verification adds another layer of security to your account and data.
Your password confirms that you know your login details. The verification code also confirms that you have access to the email address registered to your Kato account.
This helps protect your organisation’s confidential information and reduces the risk of unauthorised account access.
The security landscape has shifted quickly. Attackers are now using AI tools to turn previously obscure vulnerabilities into working attacks within days rather than years, and the same tools are being used to generate convincing phishing emails and to test stolen passwords at scale. Passwords alone are no longer considered a strong enough defence against this, which is why the extra verification step is now required rather than optional.
Email verification aligns us with the ISO 27001 security standards, which requires strong authentication controls for systems holding client data. Many of our agency customers are asked about exactly this kind of control by their own clients during procurement and security reviews, so it's increasingly expected as standard across the industry - not just within Kato.
Q. Who will need to use email verification?
A. Users who log in to Kato with an email address and password will need to complete email verification. If your organisation uses Single Sign-On (SSO), your login process will not change as part of this update.
Q. How often will I need to authenticate my login?
A. A standard user session will last 24hrs so that is as frequently as you will need to re-authenticate. However, if you switch browsers or devices during a session, then you will need to re-authenticate each time you do so.
Q. When is this change happening?
A. Two-Factor authentication will become mandatory to all non-SSO account users from October 2026.
Q. When will I need to verify my email?
A. Once email verification is enabled for your organisation, you’ll need to complete it from your next eligible login onwards.
Registration, account approval, activation and your first login will continue to work as they do today.
If you’re a new user who joins Kato through a schedule invite, you won’t be asked to complete email verification during your first login. You’ll be asked from your next login onwards.
Q. Where will my verification code be sent to?
We’ll send the code to the email address registered to your Kato account.
The verification screen will show a masked version of this address so you can confirm where the code has been sent.
Q. Where will my verification code be sent from?
We’ll send the code from verify@kato.app
We recommend your IT team whitelisting the kato.app domain and users add verify@kato.app to their safe senders list, contacts or VIP lists.
Q. I haven’t received my verification code. What should I do?
A. First, check your inbox and your spam or junk folder.
If the email still hasn’t arrived, you can request another code from the verification screen after 60 seconds.
You can resend the code up to three times.
If the problem persists, then please contact the Kato Support team.
Q. My verification code is taking too long to arrive. What should I do?
A. Kato delivers verification codes within seconds (7 on average) of you requesting them. If a code takes longer than this to reach your inbox, the delay is usually caused by your organisation’s email security settings. Many email filtering tools hold incoming emails while they scan them, before releasing them to your inbox.
To fix this, ask your IT team to:
Allowlist emails from verify@kato.app in your email security gateway (for example, Microsoft 365, Mimecast or Proofpoint).
Base the allowlist rule on the sender and a DKIM pass for the kato.app domain. All Kato verification emails are signed for kato.app, so this lets genuine Kato emails through quickly without weakening your security.
Exclude Kato verification emails from link and attachment scanning (for example, Safe Links or URL protection).
While waiting for a code, we recommend:
Checking your spam, junk, “Other” and quarantine folders.
Waiting at least a minute before requesting a new code. Requesting several codes in quick succession adds more emails to the queue and can make the delay worse.
Always entering the code from your most recent verification email.
To reduce how often you need a code, try to use the same browser and device. A session lasts 24 hours, but switching browsers or devices will ask you to verify again.
If codes are still slow after your IT team has made these changes, please contact the Kato Support team and ask to speak with a human. We can trace delivery times for your account to help your IT team find the cause.
Q. My verification code doesn’t work. What should I do?
A. Check that you’ve entered the code from your most recent verification email.
If the code still isn’t accepted, request a new one from the verification screen and try again.
Q. I no longer have access to my registered email address. What should I do?
A. Contact your Organisation Admin, who will be able to amend the email address registered to your Kato account via this link https://settings.kato.app/users
Q. Can I use an authenticator app or SMS instead?
A. No. Email is the only verification method available for this update.
Your verification code will be sent to the email address registered to your Kato account.
Q. Does this affect organisations using SSO?
A. No. If your organisation uses Single Sign-On (SSO), you’ll continue to sign in through your existing SSO process.
You won’t be asked to complete Kato’s email verification step as part of this update.
Q. Does this change how new accounts are created?
A. No. Registration, account approval, activation, and first login will continue to work as they do today.
Email verification applies to eligible logins after that point.
Q. I can't log in, and my organisation admin is unable to help?
A. If they are unable to resolve the problem, then please contact help@kato.app with the steps you have taken and ask to speak with a human.
Q. Can I share my login with a colleague or PA so we can both be logged in at once?
A. No. Sharing a single licence between two people, or using one account simultaneously on multiple devices by different individuals, is not permitted under our terms.
This isn't unique to Kato - it's standard practice across software platforms. Sharing a licence:
Weakens your organisation's security posture, since there's no reliable way to tell who actually performed an action from a shared login.
Has GDPR implications - if there's a data breach or other incident, it becomes unclear which individual is responsible.
Can cause data issues from conflicting or simultaneous edits made under the same identity.
Means two people are using the infrastructure and support resources of a single paid seat, which isn't sustainable at scale.
If you need a colleague or assistant to work in Kato alongside you, they should have their own account. A free account can do a lot of basic tasks; a Pro account is needed for features like CRM access, publishing, or downloading. Speak to your Customer Success contact if you'd like to discuss options for your team.

