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