Signup email rules: a quick guide

Zemtu checks email addresses during signup to help stop fake and unwanted registrations. If an automatic check gets it wrong, your team can allow a legitimate customer or block an unwanted address.

Open Users → Signup rules. Organization administrators and managers can manage rules for their organizations.

Screen new signup attempts

1. Select your organization and filter by Reviewed → No.
2. Check Last attempt for recent activity, then read the decision and reason. Review both Allow and Block entries: automatic checks can make mistakes in either direction.
3. Look for the customer in Users, if an account was created. Use their registration details and any contact with your team to assess the signup; an unfamiliar-looking email alone isn't proof of abuse.
4. Choose Allow for an address you trust or Block for one you've confirmed is unwanted. Add a short Reason for your colleagues. If you're unsure, leave it unreviewed while you investigate.

This list shows signup attempts, not applications waiting for approval. Leaving an entry unreviewed doesn't pause registration. If an unwanted account already exists, handle it separately in Users.

Help a blocked customer

1. Find their email address in the correct organization.
2. Confirm that it's an address you trust.
3. Choose Allow and confirm. If there's no entry, create an active Email rule with the Allow decision.
4. Ask the customer to retry signup. Zemtu doesn't notify them when you change the rule.

Allow lets that address pass the remaining signup email checks after its format is validated. The customer still needs to complete registration and your normal verification process.

Block an unwanted address

Find the entry, choose Block, and confirm. You can also create a new active Block rule.

• Email affects one exact address, such as alex@example.com.
• Domain affects every address on that exact domain, such as example.com. Use it carefully: it could block legitimate customers too. Subdomains aren't included.

An explicit Email rule takes priority over a Domain rule. For example, you can allow one customer on a blocked domain.

What does reviewing do?

Choosing Allow or Block activates the rule and marks it reviewed. You're deciding how future signup attempts should be treated.

Opening an entry or editing only its Reason doesn't count as reviewing it. Creating a rule or changing Active does.

You can apply Allow or Block to several selected entries, but check them before confirming: every selected rule becomes active.

Active, reviewed Email rules can also provide examples for future AI checks in your organization. They help inform the assessment; they don't automatically block similar addresses or guarantee correct decisions.

Why is an automatic Block inactive?

The list also records automatic signup results. A signup may already have been rejected even though its entry is inactive and unreviewed. Other checks can still reject the address, and a previous AI decision may be reused.

Inactive doesn't mean allowed. To help a trusted customer who was wrongly blocked, choose Allow.

Likewise, an automatic, unreviewed Allow isn't an exception granted by your team or proof of completed registration. Source stays Automatic after review because it describes how the entry was created.

Stop using a rule

Clear Active and save. The history stays, but the rule stops applying and is no longer used as an AI example. Other rules and automatic checks still apply.

These rules affect signup email checks. They don't suspend existing accounts, stop existing customers from signing in, or cancel reservations. Manage those actions separately.