Sender addresses

Two conditions, both required

An address is usable as a sender only when both are true:

1. You proved you control it — by a one-time code sent to the mailbox, or by authenticating the whole domain
2. Amazon SES has verified the identity — so the message will actually be accepted for delivery

Either alone is not enough. Proving you own a mailbox does not make the mail provider willing to send from it; a verified identity does not prove the address is yours.

Verifying a single address

1. Settings → Sender emails
2. Enter the address, request a code
3. Enter the six-digit code Kognit emails you
4. Watch for a second email from AWS and click its confirmation link

Both steps are needed. Teams frequently do the first and wonder why sending still fails — the AWS confirmation is the one that makes the address deliverable.

Authenticating a domain

Better, if you can edit DNS. One setup lets you send from any address at the domain, with stronger deliverability. See Verify your sending domain.

Why you can't send from an arbitrary address

Kognit checks the from-address against your workspace's own verified senders on every send. Being able to type an address is not authorisation to send from it.

This matters more than it might appear: all workspaces share sending infrastructure, so without this check one customer authenticating a domain would make it sendable by everyone. The check is what keeps your domain yours.

If you see "You can't send from that address", add and verify it first.

Removing an address

Remove it from Settings → Sender emails. Background checks stop and the domain claim is released, so the domain can be connected again later — by you or, if you have genuinely given it up, by another workspace.

Which address gets used