This request is on the roadmap. Status: not started. It is next in the queue.
Vote on this thread to tell us whether we should re-prioritize it. We pay attention to the votes.
Problem
Delete should be available only for rows the logged-in person created.
This is the same roadmap item as Delete only for the user who has created the item.
Who it is for
Apps where people share a list, and only the author may remove their own row.
What happens today
Delete can be shown or hidden for a whole audience, such as a role. It cannot yet depend on “this person created this row.” Data restriction can hide other people’s rows. That is a different job. Here, everyone should still see the row.
Requirement
The maker can limit Delete so it appears only when the logged-in person is the one who created the row. The maker chooses the property that means “created by,” such as the user relation already stored on the row.
Everyone who can open the row still sees it. Only the creator sees Delete, and only the creator can delete it. With the limit off, Delete stays available to everyone the maker already allows.
Out of scope
This does not hide the row from other people. It does not change who can edit the row. It does not remove a separate admin path the maker has already allowed.
Success criteria
- The creator opens their row, sees Delete, and can delete it.
- Another person who can open that same row does not see Delete and cannot delete it.
- That other person can still see the row.
- With the limit off, Delete remains available to everyone the maker already allows to see it.