Email Verification
Confirm the user actually controls the address on the account.
What it adds
A verification email with a single-use expiring link, a resend path, and defined behaviour for every way that link can be opened.
What your agent is told to do
5
What your agent is told to do
5-
1
Issue single-use tokens with a stated expiry, stored hashed. A token you can read out of your own database is a token support can be tricked into using.
-
2
Decide what unverified accounts may do and enforce it on the server. Hiding features in the UI while the endpoints stay open verifies nothing.
-
3
When the user changes their email, verify the new address before it replaces the old one, and notify the old address that a change was requested.
-
4
Rate-limit resends per address and per account, but keep a path forward when delivery genuinely fails — a hard lockout after three bounces turns into a support ticket.
-
5
Never confirm or deny whether an address already belongs to an account in any response, including timing and error copy.
Edge cases it handles
6
Edge cases it handles
6- Clicking an already-used link must show 'already verified', not an error.
- Clicking a link while signed out, or while signed in as a different user, must be handled explicitly rather than verifying the wrong account.
- Requesting a new link must invalidate the previous one, and the copy must say so — otherwise people click the older email.
- Email clients and security scanners pre-fetch links; a GET that consumes the token will be burned before the user sees it.
- An expired link must offer a one-click resend, not send the user back to the start.
- Changing the email again before the first change is confirmed must not leave two pending addresses.
Definition of done
8
Definition of done
8- Verification tokens are single-use, expiring, and stored hashed.
- Restrictions on unverified accounts are enforced server-side.
- Already-verified, expired, and reused links each have their own clear state.
- Email changes verify the new address before it takes effect and notify the old one.
- Resends are rate-limited and always recoverable.
- No response reveals whether an address is registered.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
User Roles
User Roles
Not everyone should be able to do everything.
What it does
Role-based permissions, enforced on the server, with a UI that reflects them.
How it works
-
1
Define roles and their permissions in ONE place. Scattering
if user.admin?through the codebase is how authorization bugs happen. - 2 Enforce every permission server-side, at the controller or service layer.
- 3 Hide UI the user can't use — but never rely on hiding as the enforcement.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/user-roles
Workspace Deletion Workflow
Workspace Deletion Workflow
Close a whole workspace without one click erasing everyone's work.
What it does
An owner-only deletion flow with an explicit inventory, a recovery window, and cascading cleanup across internal and external systems.
How it works
- 1 Restrict deletion to owners and require recent re-authentication plus typing the workspace name. This is the most destructive action in the product and should feel like it.
- 2 Show an inventory before confirming: how many members lose access, what happens to billing, how many files and records are affected, which integrations disconnect, and which shared links die.
- 3 Schedule the deletion rather than executing it. Mark the workspace as pending deletion, block access to it, notify every member and admin, and only purge after a stated recovery window.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/workspace-deletion-workflow
Domain Verification
Domain Verification
Prove an organization controls a domain before unlocking domain-wide powers.
What it does
A DNS or file-based challenge that verifies domain ownership and gates features like enforced SSO and domain-wide join.
How it works
- 1 Generate a unique, unguessable token per organization and domain, and verify it via a DNS TXT record or a file served over HTTPS at a fixed path.
- 2 Check the challenge server-side from the app's own infrastructure. A verification the browser performs can be faked.
- 3 Re-check verified domains on a schedule and mark a domain unverified when the evidence disappears, rather than trusting a one-time pass forever.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/domain-verification
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.