# If the Form Editor was a 🍪 cookie jar, how might one keep hands out of it?

**URL:** <https://forum.asana.com/t/if-the-form-editor-was-a-cookie-jar-how-might-one-keep-hands-out-of-it/124363>\
**Category:** Forum Leader tips\
**Tags:** forum-leader-tip\
**Created:** [7 June 2021 21:01 UTC](https://forum.asana.com/t/if-the-form-editor-was-a-cookie-jar-how-might-one-keep-hands-out-of-it/124363 "2021-06-07T21:01:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![LEGGO](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/leggo/32/94022_2.png) [@LEGGO](https://forum.asana.com/u/LEGGO)\
**Post date:** [7 June 2021 21:01 UTC](https://forum.asana.com/t/if-the-form-editor-was-a-cookie-jar-how-might-one-keep-hands-out-of-it/124363/1 "2021-06-07T21:01:07Z")

</div>

Today any member of a project that has edit rights is able to modify the content within Project [Forms](https://asana.com/guide/help/premium/forms). Since there aren’t any form-specific permissions, this could create some complications and perhaps introduce some confusion for those that aren’t as familiar with the feature. In this tip I will describe a scenario and offer 3️⃣ suggestions _for better form management._

In some instances, it might be by design to 1️⃣ **provide placeholders within the drop-down options of a question**. Say for instance a team is using a [Custom Template](https://asana.com/guide/help/premium/custom-templates) to collect information from the field where a form is leveraged to standardize the data entry. As such, a part of the prescribed workflow, might be to require users to pre-populate certain areas of the form for the scope of their data capture.

* * *

_How might this be achieved if we want to limit the interactions users have with the Form Editor?!?_

The answer lies within [Custom Field mapping](https://asana.com/guide/help/premium/forms#gl-mapping). As seen in the GIF from the link, you are able to 2️⃣ **connect drop-down options to Custom Fields within the project**. If the fields are setup properly for the scope of a generic project, a template can be used which then allows users to customize the options within said fields. Users can then be instructed to [edit fields from the customize menu or column header](https://asana.com/guide/help/premium/custom-fields#gl-edit). If a user _was_ to attempt to change the drop-down options from a form they will be sent back to the same field editor. They won’t be able to simply introduce a new option to an already-connected custom field which provides a nice layer of control.

* * *

**Disclaimer:** this is one of the few instances where our org will purposefully not [add this field to the org library](https://asana.com/guide/help/premium/custom-fields#gl-reusable). This is done because this field is meant to be modified to suit the needs of a specific project and not to report aggregated data.

* * *

Wait… hold the phone ☎… rewind the clock 🕥… you might be asking, _why might one want to limit the user interaction with the editor?!?._… Well… without form permissions, if your experience is anything like mine, a decent subset of users mistakenly will try to submit form data through the editor 🤦‍♂️… creating unnecessary rework!.. It’s true… it happens… For this reason, when it comes to Forms we prefer to 3️⃣ **ONLY advertise the [Form Link](https://asana.com/guide/help/premium/forms#gl-share) and we avoid drawing any unnecessary attention to the Form tab which contains the editor**.

* * *

Be the change, vote for a better tomorrow here: [[Forms] Ability to manage Forms permissions](https://forum.asana.com/t/forms-ability-to-manage-forms-permissions/51796) 😉

**Is this helpful? How do you creatively manage Forms and the uninviting manipulation of its content?**

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [9 June 2021 05:08 UTC](https://forum.asana.com/t/if-the-form-editor-was-a-cookie-jar-how-might-one-keep-hands-out-of-it/124363/2 "2021-06-09T05:08:19Z")

</div>

> [@LEGGO](#):
>
> without form permissions, if your experience is anything like mine, a decent subset of users mistakenly will try to submit form data through the editor

oh yes. A client of mine butchered the 5 first questions I prepared by trying to answering them within the editor ^^

---

<div class="post-metadata">

**Author:** ![Peta\_Williams](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/peta_williams/32/28768_2.png) [@Peta\_Williams](https://forum.asana.com/u/Peta_Williams)\
**Post date:** [14 June 2021 21:56 UTC](https://forum.asana.com/t/if-the-form-editor-was-a-cookie-jar-how-might-one-keep-hands-out-of-it/124363/3 "2021-06-14T21:56:59Z")

</div>

Yep, this regularly seems to happen 🤦‍♀️

---

<div class="post-metadata">

**Author:** ![Stephanie\_Oberg](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/stephanie_oberg/32/80033_2.png) [@Stephanie\_Oberg](https://forum.asana.com/u/Stephanie_Oberg)\
**Post date:** [2 November 2022 17:28 UTC](https://forum.asana.com/t/if-the-form-editor-was-a-cookie-jar-how-might-one-keep-hands-out-of-it/124363/4 "2022-11-02T17:28:07Z")

</div>

It’s easily understandable, I can hardly blame the **form** user for thinking that they naturally will only have permissions to edit somewhere that is permissible. That’s the way it is is 99.99% of apps & websites we encounter…

---

<div class="post-metadata">

**Author:** ![Peta\_Williams](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/peta_williams/32/28768_2.png) [@Peta\_Williams](https://forum.asana.com/u/Peta_Williams)\
**Post date:** [2 November 2022 19:49 UTC](https://forum.asana.com/t/if-the-form-editor-was-a-cookie-jar-how-might-one-keep-hands-out-of-it/124363/5 "2022-11-02T19:49:38Z")

</div>

This problem has pretty much been resolved for me since the form permissions release: [[Forms] Ability to manage Forms permissions - #52](https://forum.asana.com/t/forms-ability-to-manage-forms-permissions/51796/52)

---

<div class="post-metadata">

**Author:** ![Stephanie\_Oberg](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/stephanie_oberg/32/80033_2.png) [@Stephanie\_Oberg](https://forum.asana.com/u/Stephanie_Oberg)\
**Post date:** [2 November 2022 20:15 UTC](https://forum.asana.com/t/if-the-form-editor-was-a-cookie-jar-how-might-one-keep-hands-out-of-it/124363/6 "2022-11-02T20:15:39Z")

</div>

That’s brilliant, thanks for the update!
