# Restrict Fields To Only One Project

**URL:** <https://forum.asana.com/t/restrict-fields-to-only-one-project/719761>\
**Category:** Ask the Community\
**Tags:** custom-fields, projects, tasks\
**Created:** [26 February 2024 12:02 UTC](https://forum.asana.com/t/restrict-fields-to-only-one-project/719761 "2024-02-26T12:02:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ed\_Williams2](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/ed_williams2/32/228492_2.png) [@Ed\_Williams2](https://forum.asana.com/u/Ed_Williams2)\
**Post date:** [26 February 2024 12:02 UTC](https://forum.asana.com/t/restrict-fields-to-only-one-project/719761/1 "2024-02-26T12:02:10Z")

</div>

Hi,

We have a team structure where requests come in through a request channel and are added to a central Asana project of which multiple subteams are members.

We then add these projects to other projects which each subteam then manages. Our problem is that we have many fields which are relevant only to one project but not to others. At the moment our stacking fields are making the tasks messy.

We would like to restrict the fields to appear only on certain projects, so they don’t clutter up the task.

I already know that we can have global fields, which will then be updated across projects, which is great,  
I also know that non-global tasks will not show data across projects.  
I also know that fields only appear to those who are members of both projects, and that in a sense the viewing of fields could be restricted that way, but this does not work for us as, we are all members of all the projects.

Is it possible to prevent fields entirely from carrying over between projects? Or are there ways we can adapt membership to limit the fields we can see across projects, while still maintaining editing rights?

Thank you!

---

<div class="post-metadata">

**Author:** ![Andrea\_Mayer](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/andrea_mayer/32/39226_2.png) [@Andrea\_Mayer](https://forum.asana.com/u/Andrea_Mayer)\
**Post date:** [26 February 2024 12:42 UTC](https://forum.asana.com/t/restrict-fields-to-only-one-project/719761/2 "2024-02-26T12:42:48Z")

</div>

Welcome to the Asana Community Forum @Ed_Williams2 👋

I have found this feedback request thread that I think is relevant in your case:

> [@By default, collapse the Custom Fields that aren't directly applied to a Project](https://forum.asana.com/t/by-default-collapse-the-custom-fields-that-arent-directly-applied-to-a-project/100149):
>
> I love that all Custom Fields are shown on tasks when the tasks are multi-homed. However, the more you multi-home tasks the longer the list of Custom Fields becomes. This can create some confusion and introduce a barrier to clarity. In some cases, these fields are associated or useful for the purpose in which the task belongs to the Project in view. Much like how a limited number of subtasks are shown on a task (by default), I think it would be super useful to only show the Custom Fields for th…

And this one as well

> [@The ability to hide Custom Fields applied to a task that don't belong to the project in which the task is being viewed](https://forum.asana.com/t/the-ability-to-hide-custom-fields-applied-to-a-task-that-dont-belong-to-the-project-in-which-the-task-is-being-viewed/79740):
>
> I really like the solution that was recently introduced which provided the ability to hide Custom Fields on subtasks within a Project. I believe that many would appreciate the opportunity to hide Custom Fields on task AND subtasks in the same way IF the Custom Fields pertained to another project. Through the use of multi-homing you can assign tasks to multiple projects. This then consolidates ALL the Custom Fields across those projects within the task. However, you can only view the tasks as a f…

---

<div class="post-metadata">

**Author:** ![Hannah\_Ferris](https://luna1.co/8d76cd.png) [@Hannah\_Ferris](https://forum.asana.com/u/Hannah_Ferris)\
**Post date:** [18 June 2024 23:43 UTC](https://forum.asana.com/t/restrict-fields-to-only-one-project/719761/3 "2024-06-18T23:43:45Z")

</div>

Is there a solution for this yet? I don’t love that custom fields show up every time I add a project member’s board to a central project. I have multiple “status” fields because each member has their own and it makes it really confusing to tag tasks in the project. Help!

---

<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:** [19 June 2024 01:05 UTC](https://forum.asana.com/t/restrict-fields-to-only-one-project/719761/4 "2024-06-19T01:05:14Z")

</div>

The tools available to you were mentioned in the original post in this topic and nothing has changed, I’m afraid.

Thanks,

Larry
