The answer
No. It changes access responsibilities and needs explicit rules for eligibility, acceptance, and remaining permissions before it can be implemented and tested correctly.
Why should deletion and other advanced settings remain separate features?
Should ownership transfer be added casually while implementing basic wedding editing?
More FAQs in Why should deletion and other advanced settings remain separate features?
Not necessarily. It can appear in the same settings area, but its permissions, confirmation, data handling, and verification should remain a distinct workflow.
Related events, invitations, tasks, and storage objects may remain, so the deletion design must define how each associated resource is handled and verified.
Still have questions?
Browse all our FAQs or reach out to our support team
Want to upskill yourself?
Your learning library
Small steps. Big possibilities.
Find your next course. Build something great.