User Roles
Not everyone should be able to do everything.
What it adds
Role-based permissions, enforced on the server, with a UI that reflects them.
What your agent is told to do
4
What your agent is told to do
4-
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.
-
4
Default to deny. A new endpoint should be inaccessible until explicitly permitted.
Edge cases it handles
5
Edge cases it handles
5- Test every endpoint as a LOW-privilege user, not just as an admin. This is where the bugs are.
- A role change must take effect immediately, not on next login.
- Object-level permissions matter: a user may edit their own record but not someone else's. Role alone isn't enough.
- API endpoints and background jobs need the same checks as the UI.
- The last admin must not be able to demote themselves.
Definition of done
8
Definition of done
8- Permissions are defined in one place.
- Every endpoint is enforced server-side and defaults to deny.
- Object-level ownership is checked, not just the role.
- Requesting a forbidden endpoint directly is refused.
- Role changes take effect immediately.
- The system cannot be left without an admin.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
Account Settings
Account Settings
One place for a user to manage themselves.
What it does
Profile, email, password, and account deletion — the settings every app needs.
How it works
- 1 Group settings into sections: profile, security, notifications, danger zone.
- 2 Changing an email address must be verified at the NEW address before it takes effect.
- 3 Changing a password must require the current password, and should invalidate other sessions.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/account-settings
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.