The ability for the user who has created the page to delete it. Today it is possible to display the delete button a the screen for one item, but I guess this button will be visible for all users. The request is to make it visible only for the user who have created the item (a product in my case).
Note that I will link the user table to the product table, hence having a “user” property (relation) in the product table.
Hey Julien! Welcome to the NotionApps community! That sounds like a fair request. Quick question, do you want other users to see the product created by this user?
Hello Jatin,
Yes. Definitely 
You could solve this using our “user-specific” data permissions. You can read about it here, https://docs.notionapps.com/users/personalize-data.
Hi Jatin,
I understand that this solution restricts who can view the list of products to the current user (using its email). This is not what I want to do. I want all my users to see the list of products but only the user who has created a specific product to be able to delete it.
Let me know if I miss something.
I will discuss this feature internally and get back to you, Julien! However, a workaround is possible if one could hide/show components based on the logged-in user properties. With this, one could create a status property input and only the owner of the order could see it. The owner can then mark the status as DELETE. I’ll keep you posted once we start working on it.
Hi Jatin,
I like your approach. I think that having a Role Base Access Control (RBAC) approach would be powerful and will allow addressing various use cases.
That being said, I was thinking about an alternative that is probably even better for my specific application: Apply a filter on the “Update items” screen (and only on this specific screen, not on the “View items” screen as the user see all products published by all users) so that the user can view only the product he has created (and not the one created by other users). From there, the user can access and update each individual product (“Update item” screen) or delete the whole product (I’ll add a Delete button). I believe that this will be cleaner (and a more standard pattern) in my specific case.
Hope that makes sense. Let me know if you have any questions. Happy to provide any details needed. Thank you!
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.
Everyone who can open an item can see Delete. The person who created the row should be the only one who can delete it, while everyone else can still see the row.
This is the same roadmap item as Limit deletions to items created by the logged-in user.
Apps where people share a catalog or a board, and only the author may remove their own row.
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.
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.
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.