This is not the same as this request which is also cool.
I would like a field library for teams so I can set up custom fields just within a team.
Use Case
How many variants of Task Progress will pile up as different people set selections based on their needs. If allowed to save to a Team, then the name can be the same, but just at a team level. You can do this on a project level, but then you can’t have progress bubble up into other project within that same team.
Thanks for sharing your feedback with us, @Getz_Pro! I believe that in order to achieve this we would also need an option to add the custom field to the Team’s library instead of the entire Organization’s library 
Yes. I guess I didn’t say that clearly.
@Emily_Roman are any improvements like this in the works? It’s been so frustrating trying to come up with shared custom fields within my org because similarly named custom fields are already in our company library. I haven’t found a good solution other than really long titled custom fields which is not ideal.
I am looking to have linked custom fields (named the same) across my team’s projects so I can share tasks, without making them available across the company. Other business areas have similar/same custom fields but their options would be different than ours depending on their workflows, and I want our projects to contain only our options to keep user error to a minimum. Is there a way to have custom fields saved to the team level so only my team has access? If not, is there any sort of idea submission where I can throw that in?
Does anyone have a workaround?
Thank you!
Angie
I’ve merged your request with an existing one so that you and others can vote at the top of this thread now.
In the meantime, until/if that becomes available, many orgs use a naming convention for their shared custom fields, e.g.:
Also, it’s good etiquette (but of course not everyone follows this) to respect the warning at the top of the custom field dialog and check the change history for more context:
Larry
I believe I have another use case for this scenario. If we had team specific custom fields than only people that are part of the team can see the custom field.
Example: We are looking to have the task’s proposal price tied to it. If we include it as a custom field than all employees are able to see the contract price, while we would only like the management/sales team to have access to it.
Just came here to request this and saw your post already requesting it.
I deeply need this! I’m a Sr. Design Program Manager at Amazon and as you can imagine at a company the size of Amazon our custom field library has become MASSIVE and unruly and nearly impossible to create fields with clean names anymore. For example I would like to create a custom field for our UX team just called “Priority” - but this is already taken and used in a way different than what we need. So now everyone is forced to change the name so for example there is: UXPriority, UX-Priority, CSUX-Priority, Priority(UX), Priority(Team Name), etc. etc.
So changing this so that custom fields library is on a Team Level would completely solve this giant headache, allowing us to use desired names for fields while having them be utilized across all projects under that team to maintain consistency.
A couple other thoughts:
My bet is that a large portion of these names that are already taken, are taken by people/teams that are no longer with the company. So having this default to a Team level, and if you need to put a field to a Company level needing an Asana Admin to perform this, would be ideal. That way if the team gets deleted it will take all their custom fields with them and not impact the rest of us. And it would give Admins more control to keep things clean at a company level. (Trash data only hurts us all)
Second thought, it would also be nice to have the option to select multiple teams. I cover several teams and would love to keep them all unified and consistent. So being able to select all the teams I admin would be great. If the field already exists for one of these teams you can provide me with an error “Field exists for UXO team” so I can investigate and correct.
+1 from an Amazon employee. Having a organization library for a company of this size just makes things way to complicated and the amount of customization needed makes the names so long when they don’t need to be.
Recently (Release notes July 2024) we’ve been given the ability to set up and edit the details of custom fields (Asana Help).
Also asana is rolling out Team Sharing for projects.
I think it would be awesome to marry the two and be able to add Teams with certain specific access rights to the custom fields.
A logical next step, indeed! 
Agreed.
This would be useful. We’ve actually begun adding team initials at the end of the the custom field name to make them searchable.
Adding my support for this feature.
I really like the idea of having a TEAM Custom Field library, where those CF’s can be shared across the projects within the team, without having to share them across the entire organization - the only current option for multi-project CF use.
Rough example of what I’m imagining, utilizing the same privacy UI from the project creation process:
I agree. This could be very powerful and useful.
We need to have the option when creating a custom field to not only add it to the company’s library but also to have the team’s libraries with the option to add it to one or multiple teams.
There are definitely fields that need to be a teams level instead across the entire company.
Good news! It’s coming: [ Upcoming ] Custom fields Team Sharing
Hi everyone,
Just a quick heads up that we’ve introduced team sharing for custom fields! With this update, custom field admins can now share fields with entire teams, not just individual users 
You can read the full announcement here: New! Share custom fields with entire teams
While this doesn’t introduce a full team-level library view for custom fields, it does help streamline and consolidate access across teams. Looking ahead, we’re hoping to add a “filter by teams” option to the custom field library in a future iteration. No ETA just yet, but it’s on our radar!
With that in mind, I’m updating the title of this thread to better reflect the scope of the launch, since the main issue has now been addressed. If you’d still like to submit a request specifically for a team-level library view, feel free to start a new topic in product-feedback.
)Hi @Vanessa_N, I don’t think this new feature solves the initial request, which is asking for a specific field library dedicated to a particular team. Do you agree?
