Domain Verification
Prove an organization controls a domain before unlocking domain-wide powers.
What it adds
A DNS or file-based challenge that verifies domain ownership and gates features like enforced SSO and domain-wide join.
What your agent is told to do
6
What your agent is told to do
6-
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.
-
4
Make clear in the UI exactly what verification unlocks — enforced SSO, automatic joining, directory visibility — so the consequence of verifying is not a surprise.
-
5
Do NOT let a verified domain silently absorb existing accounts. Adding existing users to an organization is a separate, consented action.
-
6
Do NOT verify public email domains such as the large consumer mail providers; maintain a blocklist and refuse them outright.
Edge cases it handles
6
Edge cases it handles
6- The same domain claimed by two organizations must resolve deterministically — first verified wins, later claimants are refused with a route to dispute.
- Apex domains and subdomains are distinct claims. Decide whether verifying an apex covers its subdomains and enforce that consistently.
- DNS propagation means the first check often fails legitimately — retry on a backoff and let the user re-check manually, rather than invalidating the token.
- Verification tokens must expire, and re-issuing a token must invalidate the previous one.
- Internationalised and punycode domains must normalise to one canonical form before comparison, or the same domain verifies twice.
- Losing verification must not instantly lock users out of an organization with enforced SSO — warn the admins first and define a grace period.
Definition of done
8
Definition of done
8- Ownership is proven by a unique token via DNS TXT or an HTTPS-hosted file.
- Verification is performed server-side.
- Verified domains are re-checked periodically and revoked when evidence is gone.
- A domain can only be verified by one organization at a time, with a documented dispute path.
- Public consumer email domains are refused.
- The features a verified domain unlocks are stated before verification, and existing accounts are never absorbed without consent.
- 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
Member Directory
Member Directory
Show who is in the workspace and how to identify them.
What it does
A searchable, read-only roster of workspace members with their role, status, and the profile fields they have chosen to share.
How it works
- 1 Build this as a read view. Inviting members is owned by Team Invitations, changing roles is owned by User Roles, and seat counts are owned by Seat Management — link out to those rather than duplicating their controls here.
- 2 Show each member's display name, avatar, role, and status. Status is not decoration: pending, active, suspended, deactivated, and external guest must be visually distinct and filterable.
- 3 Respect per-field profile visibility. A field the member marked private is not rendered, not returned by the API, and not searchable — hiding it in the template while shipping it in the payload is not privacy.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/member-directory
Account Linking
Account Linking
Let one account sign in several ways without spawning duplicates.
What it does
Attach and detach sign-in methods — password, OAuth providers, SSO — on a single existing account.
How it works
- 1 Model sign-in methods as separate identity records attached to one account, rather than columns on the user.
- 2 Require a fresh re-authentication before any link or unlink. A stale session is enough to read the app; it is not enough to change how the account is entered.
- 3 Refuse to link an identity that is already attached to another account. Explain the conflict and point the user at recovery — do not silently steal the identity or silently create a second account.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/account-linking
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.