Member Directory
Show who is in the workspace and how to identify them.
What it adds
A searchable, read-only roster of workspace members with their role, status, and the profile fields they have chosen to share.
What your agent is told to do
6
What your agent is told to do
6-
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.
-
4
Make search server-side and match on name and handle. Client-side filtering of a fetched list leaks every member's data to anyone who opens the page.
-
5
Do NOT expose raw email addresses by default. Where contact matters, prefer an in-app action over publishing the address.
-
6
Paginate rather than loading everyone; a workspace of five thousand people should open as fast as one of five.
Edge cases it handles
6
Edge cases it handles
6- Counts in the header must match what the current viewer is allowed to see, or the numbers look broken.
- Deactivated members must still resolve by name on old content, even when they are filtered out of the default view.
- External guests must be labelled as such and must not see the full internal roster.
- A member with no avatar, no display name, or an unaccepted invitation must still render a sensible row rather than a blank one.
- Search must match accented and non-Latin names, and must not fall over on a query of one character.
- The viewer's own row should be marked, and admin-only columns must be absent for non-admins rather than merely hidden with CSS.
Definition of done
8
Definition of done
8- Every member is listed with name, role, and a visually distinct status.
- Private profile fields are absent from the API response, not just from the page.
- Search and pagination happen server-side and stay fast on large workspaces.
- Guests and non-admins see a correctly reduced view, including reduced counts.
- Deactivated members remain resolvable on existing content.
- Invite, role, and seat controls link to their owning features rather than being reimplemented.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Account Merge
Account Merge
Collapse two duplicate accounts into one without losing work.
What it does
A controlled flow that merges a source account into a target account, resolving conflicts across ownership, billing, and content.
How it works
- 1 Require proof of control over both accounts in the same flow — a verified challenge to each, not just being signed into one.
- 2 Show the user a merge plan before anything moves: what will be kept, what will be reassigned, what will be discarded, and what cannot be undone.
- 3 Resolve each conflict class explicitly — workspace memberships, subscriptions, usernames, handles, preferences, API keys. Pick a rule per class and state it in the UI rather than guessing.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/account-merge
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
Password Reset
Password Reset
Let people back in without opening a hole for everyone else.
What it does
A request-and-reset flow with expiring single-use tokens, identical public responses regardless of whether the account exists, and session cleanup afterwards.
How it works
- 1 Return the same message and the same rough response time whether or not the address has an account. The reset form is the most common account-enumeration oracle in any app.
- 2 Store tokens hashed, expire them within an hour or so, and consume them on use.
- 3 After a successful reset, revoke all other sessions and notify the account by email that the password changed.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/password-reset
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.