# Custom Field Permissions

**URL:** <https://forum.asana.com/t/custom-field-permissions/1085254>\
**Category:** Ask the Community\
**Tags:** custom-fields\
**Created:** [30 July 2025 13:33 UTC](https://forum.asana.com/t/custom-field-permissions/1085254 "2025-07-30T13:33:00Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christine\_Bolton](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/christine_bolton/32/66614_2.png) [@Christine\_Bolton](https://forum.asana.com/u/Christine_Bolton)\
**Post date:** [30 July 2025 13:33 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/1 "2025-07-30T13:33:00Z")

</div>

I’m creating a private project that’s part of an organizational workflow that not all contributors should have access to. Their individual contributions are not private, but others might be. The organization wants the task collaborator to be able to edit all custom fields, but I haven’t found a way to allow that with the new permission system. I set the task collaborator as a project admin, but the custom field is still grayed out. They’re able to delete the value, but not update it.

The only workaround I’ve found is to add the contributor to the project directly.

Is there another way to configure this that I might be missing?

 ![image](https://us1.discourse-cdn.com/asana/original/4X/5/1/7/5171feb611de769e70035f8c49e8c10427b4834e.png)

 ![image](https://us1.discourse-cdn.com/asana/original/4X/3/7/2/372e5fbbf884d58290efa2d317a6a7a579b4f70a.png)

---

<div class="post-metadata">

**Author:** ![Emily\_Roman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/emily_roman/32/283076_2.png) [@Emily\_Roman](https://forum.asana.com/u/Emily_Roman)\
**Post date:** [5 August 2025 09:31 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/2 "2025-08-05T09:31:36Z")

</div>

Hi @Christine_Bolton, good question! We have a similar question on this topic, adding here for visibility: [Limit Project Custom Field visibility so it's only visible to the project members (not collaborators)](https://forum.asana.com/t/limit-project-custom-field-visibility-so-its-only-visible-to-the-project-members-not-collaborators/869143)

There are a couple of things that some to my mind, could you confirm if the users are guests or members? and are the tasks where they can’t see the fields “subtasks”?

cc [@ambforumleader](https://forum.asana.com/groups/ambforumleader) [@pforumleader](https://forum.asana.com/groups/pforumleader) in case you have any workarounds to share with Christine!

---

<div class="post-metadata">

**Author:** ![Christine\_Bolton](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/christine_bolton/32/66614_2.png) [@Christine\_Bolton](https://forum.asana.com/u/Christine_Bolton)\
**Post date:** [6 August 2025 02:29 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/3 "2025-08-06T02:29:18Z")

</div>

The users that were having the issue were full members. I did test with a guest and the issue persists the same. They can see the field, they can event delete the data in the field, they just can’t edit it.

This field is intended to trigger subtasks once it’s changed. The collaborator is the assignee of the task.

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [6 August 2025 04:39 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/4 "2025-08-06T04:39:48Z")

</div>

Hi @Christine_Bolton , I’m afraid this is expected behaviour for as long as I can remember. I don’t think it has to do with custom field permissions.

The only way for collaborators to edit fields is for them to either be part of the project or access it. Or create smaller projects (which contain just the fields you want them to edit) with just tasks that are assigned to them - that is the only workaround I know of.

The fact that the collaborators can view the field value, not being able to ‘edit’ it but actually have the ability to X (clear) the values of single-select and multi-select fields is mind boggling, something I have raised in the past with @Larry_Berger_lpb and @Bastien_Siebman but never managed to get Asana to change it (or fix it, depending on how you look at it).

---

<div class="post-metadata">

**Author:** ![Larry\_Berger\_lpb](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/larry_berger_lpb/32/276017_2.png) [@Larry\_Berger\_lpb](https://forum.asana.com/u/Larry_Berger_lpb)\
**Post date:** [6 August 2025 04:49 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/5 "2025-08-06T04:49:34Z")

</div>

Yes, I think you’re correct, @Richard_Sather, even though it never made sense to me. Perhaps this is the same thing?:

> [@Custom fields can be edited (and deleted!) by users outside a project](https://forum.asana.com/t/custom-fields-can-be-edited-and-deleted-by-users-outside-a-project/219811):
>
> [edit: rumor has it there’s a way to fix this, in the Enterprise+ plan] Available on Asana [Enterprise](https://asana.com/enterprise) and [Enterprise+](https://asana.com/enterprise) tiers, as well as the [Legacy Enterprise](https://asana.com/pricing-legacy) tier. Too bad for the rest of us cry [/edit] Briefly describe (1-2 sentences) the Bug you’re experiencing: I have a custom field on Project A, that is not in the library, nor on Project B. However, if I move the task to Project B, I can see the field’s name grayed out – which is fine, but also shows an X to delete the field and its v…

Thanks,

Larry

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [6 August 2025 04:59 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/6 "2025-08-06T04:59:07Z")

</div>

Yes, that’s it, @Larry_Berger_lpb  
Thanks for adding that link, I was having trouble finding it - I recall us having a conversation about it elsewhere too.

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [6 August 2025 05:01 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/7 "2025-08-06T05:01:42Z")

</div>

Ah, here is something I recall:

> [@Unable to edit custom fields value when assigned task without the project invitation.](https://forum.asana.com/t/unable-to-edit-custom-fields-value-when-assigned-task-without-the-project-invitation/433471):
>
> My client has a private project with the set of custom fields added to the library. He wants to assign tasks from this projekt to the man that is not member of this project. This person sees the task on his My Tasks list, he sees the custom fields value but cannot edit it. He can only remove it (then the custom field disapear from the task. Is it expected behaviour or bug? I reproduced it in my Asana. Here the project with example custom fields CS A, CS B and CS C: And here is scree…

And you merged into (another) post that no longer exists…  
[https://forum.asana.com/t/task-details-remove-the-ability-to-delete-the-value-of-a-custom-field-in-the-library-that-is-in-a-private-project/425136](https://forum.asana.com/t/task-details-remove-the-ability-to-delete-the-value-of-a-custom-field-in-the-library-that-is-in-a-private-project/425136)  
I think that was mine 🙄

---

<div class="post-metadata">

**Author:** ![Larry\_Berger\_lpb](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/larry_berger_lpb/32/276017_2.png) [@Larry\_Berger\_lpb](https://forum.asana.com/u/Larry_Berger_lpb)\
**Post date:** [6 August 2025 05:02 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/8 "2025-08-06T05:02:42Z")

</div>

And thanks for your initial reply here. @Christine_Bolton’s post definitely sounded familiar, but I didn’t have time to recreate it and I wasn’t 100% sure without doing so, until you replied–teamwork!

---

<div class="post-metadata">

**Author:** ![Jan-Rienk](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jan-rienk/32/227709_2.png) [@Jan-Rienk](https://forum.asana.com/u/Jan-Rienk)\
**Post date:** [6 August 2025 08:06 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/9 "2025-08-06T08:06:23Z")

</div>

> [@Christine\_Bolton](#):
>
> They can see the field, they can event delete the data in the field, they just can’t edit it.

> [@Richard\_Sather](#):
>
> I’m afraid this is expected behaviour for as long as I can remember.

It might be what the developers are expecting to happen, but it doesn’t sound like it’s what the users should expect.

Some bugs are not in the software but in understanding.

Curious if it is possible to start a conversation on this and similar “expected” behaviours.

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [7 August 2025 18:35 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/10 "2025-08-07T18:35:46Z")

</div>

Hi @Emily_Roman, can you help rectify this broken link?

[https://forum.asana.com/t/task-details-remove-the-ability-to-delete-the-value-of-a-custom-field-in-the-library-that-is-in-a-private-project/425136](https://forum.asana.com/t/task-details-remove-the-ability-to-delete-the-value-of-a-custom-field-in-the-library-that-is-in-a-private-project/425136)

Thanks!

---

<div class="post-metadata">

**Author:** ![Emily\_Roman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/emily_roman/32/283076_2.png) [@Emily\_Roman](https://forum.asana.com/u/Emily_Roman)\
**Post date:** [8 August 2025 08:01 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/11 "2025-08-08T08:01:57Z")

</div>

Done @Richard_Sather! ✅

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [8 August 2025 08:44 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/12 "2025-08-08T08:44:40Z")

</div>

Thanks, @Emily_Roman !

I’ve reopened this for voting 🙂

---

<div class="post-metadata">

**Author:** ![Christine\_Bolton](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/christine_bolton/32/66614_2.png) [@Christine\_Bolton](https://forum.asana.com/u/Christine_Bolton)\
**Post date:** [15 August 2025 08:44 UTC](https://forum.asana.com/t/custom-field-permissions/1085254/13 "2025-08-15T08:44:59Z")

</div>

Closed on 15 August 2025 08:44 UTC

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
