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
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.