Organization Ownership Transfer
Hand a workspace to another member without breaking billing or access.
What it adds
A two-sided transfer flow where the current owner offers ownership and the recipient explicitly accepts it.
What your agent is told to do
6
What your agent is told to do
6-
1
Make the transfer two-sided: the current owner initiates, the recipient accepts. Ownership must never land on someone who did not agree to it.
-
2
Require recent re-authentication from the initiating owner, and verify the recipient is an active, verified member of the organization — not an invitee, not a suspended account, not an external guest.
-
3
List everything that moves before confirmation: billing responsibility, payment method, privileged integrations, API credentials, and any owner-only settings.
-
4
Handle billing deliberately. Either the recipient supplies a payment method as part of accepting, or the transfer stops short and the old owner stays on the hook until they do — never leave a subscription with no payer.
-
5
Guarantee the organization always has at least one owner. Block the last owner from leaving, downgrading, or deleting themselves until a successor exists.
-
6
Do NOT quietly demote the outgoing owner to nothing. Give them a defined role, and tell them what they lost.
Edge cases it handles
6
Edge cases it handles
6- A pending transfer must expire, and must be cancellable by the initiating owner until it is accepted.
- If the recipient is removed, suspended, or leaves before accepting, the transfer must void rather than complete against a dead account.
- Integrations and API keys authorised by the old owner will keep working under their identity — either re-authorise them under the new owner or list them as needing attention.
- Two concurrent transfer offers must not both succeed; a single pending transfer per organization is the simplest safe rule.
- The change must be audited and both parties emailed, including a notice to other admins.
- Transfer must be blocked while the organization is mid-deletion or has a failed payment in dispute.
Definition of done
8
Definition of done
8- Ownership only changes after the recipient explicitly accepts.
- The initiating owner re-authenticates and the recipient is verified as an active member.
- Billing responsibility and privileged integrations are transferred or explicitly flagged, never left ownerless.
- The organization can never reach a state with zero owners.
- Pending transfers expire and can be cancelled.
- The transfer is audited and both parties are notified.
- 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.