# Assign to me (automatically)

**URL:** <https://community.fibery.io/t/assign-to-me-automatically/2442>\
**Category:** Get Help\
**Tags:** automations\
**Created:** [January 24, 2022, 3:28pm UTC](https://community.fibery.io/t/assign-to-me-automatically/2442 "2022-01-24T15:28:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![uniquelau](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/uniquelau/32/3836_2.png) [@uniquelau](https://community.fibery.io/u/uniquelau)\
**Post date:** [January 24, 2022, 3:28pm UTC](https://community.fibery.io/t/assign-to-me-automatically/2442/1 "2022-01-24T15:28:13Z")

</div>

I would like to automatically assign an entity to the person creating it.

Use case: “Employee adds an Expense, it is automatically assigned to them”

If this is **not** possible, I will create a separate field called “Creator override”, and then take this as the source of truth if set, and otherwise default to the ‘creator’. Rather than having a “User” field, as currently when creating an entity we have to make 7 clicks to assign the user and nobody got time for that 😉

/Laurence

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [January 24, 2022, 3:40pm UTC](https://community.fibery.io/t/assign-to-me-automatically/2442/2 "2022-01-24T15:40:22Z")

</div>

Yet, it is possible via Formula, like this. Formula can be access via … near field that you want to update

 ![Screenshot 2022-01-24 at 5.39.40 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/4e635ad8304102870739f857e9ce524b81a81e13.png)

---

<div class="post-metadata">

**Author:** ![uniquelau](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/uniquelau/32/3836_2.png) [@uniquelau](https://community.fibery.io/u/uniquelau)\
**Post date:** [January 24, 2022, 5:28pm UTC](https://community.fibery.io/t/assign-to-me-automatically/2442/3 "2022-01-24T17:28:16Z")

</div>

Perfecto! Thanks

---

<div class="post-metadata">

**Author:** ![Nick](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nick/32/4744_2.png) [@Nick](https://community.fibery.io/u/Nick)\
**Post date:** [February 13, 2022, 7:21pm UTC](https://community.fibery.io/t/assign-to-me-automatically/2442/4 "2022-02-13T19:21:30Z")

</div>

Oh my god! This comment save me a couple of hours (or days)! Thanks a lot.

---

<div class="post-metadata">

**Author:** ![anadin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/anadin/32/5376_2.png) [@anadin](https://community.fibery.io/u/anadin)\
**Post date:** [April 13, 2023, 5:05am UTC](https://community.fibery.io/t/assign-to-me-automatically/2442/5 "2023-04-13T05:05:59Z")

</div>

Sorry to update this from so long ago, I don’t see a similar function to auto assign on update (e.g. a User changes a task from To Do to In Progress)

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [April 13, 2023, 5:15am UTC](https://community.fibery.io/t/assign-to-me-automatically/2442/6 "2023-04-13T05:15:01Z")

</div>

You can use an automation similar to the one @mdubakov posted, but choose to trigger on entity updated (instead of created) and pick the state field as the one to be monitored.  
Then add a filter to only execute if the state is In Progress.

---

<div class="post-metadata">

**Author:** ![anadin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/anadin/32/5376_2.png) [@anadin](https://community.fibery.io/u/anadin)\
**Post date:** [April 14, 2023, 6:43am UTC](https://community.fibery.io/t/assign-to-me-automatically/2442/7 "2023-04-14T06:43:58Z")

</div>

Yup I tried that but I could not see a way to assign to the current user even in a formula, only to assign to a specific user. I have probably missed something?
