# Prevent Created By user from deleting entity

**URL:** <https://community.fibery.io/t/prevent-created-by-user-from-deleting-entity/11411>\
**Category:** Get Help\
**Created:** [October 11, 2026, 11:56pm UTC](https://community.fibery.io/t/prevent-created-by-user-from-deleting-entity/11411 "2026-10-11T23:56:49Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [October 13, 2026, 12:46am UTC](https://community.fibery.io/t/prevent-created-by-user-from-deleting-entity/11411/4 "2026-10-13T00:46:55Z")

</div>

Do you need the user to “Create and open” or is it “Submit it and forget about it” kind of situation. I ask because:

1. The “Created by” automatic sharable access templates are limited to the default access templates
2. You can make a “Created by” formula field, which literally just pulls from the created by field, and use that for the automatic sharing, then you can give custom access templates
3. BUT this takes a bit longer to propagate (unfortunately), so “Create and Open” doesn’t really work, takes like 3 seconds.

IF you don’t need the create and open functionality, I would combine this with a formula which returns “True” always, and then trigger the population of the required field when the formula changes. Since it was not changed by a user, it will use admin rights to make the run, not the user who created the entity (i think).

Let me know if this makes sense.

The biggest downside is the delay of granting access due to using a formula field, I with we could use custom access templates on the “Created by” field.

---

_[View the full topic](https://community.fibery.io/t/prevent-created-by-user-from-deleting-entity/11411)._