# Team knowledge - Recognizing words in the Task Description field, Project Overview tab, & Note tab **URL:** \ **Category:** Product Ideas\ **Tags:** project-views\ **Created:** [28 March 2025 05:26 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384 "2025-03-28T05:26:34Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![ka\_nishiyama](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/ka_nishiyama/32/292165_2.png) [@ka\_nishiyama](https://forum.asana.com/u/ka_nishiyama)\ **Post date:** [28 March 2025 05:26 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384/1 "2025-03-28T05:26:35Z")
Hi, I’ve just started using [Team Knowledge](https://forum.asana.com/t/improve-team-onboarding-and-ongoing-collaboration-with-team-knowledge-bases/1026660). (I still don’t understand how it works) As you can see in the attached image, words in the comments field are underlined, but it doesn’t seem to work for words in the description field. ![image](https://us1.discourse-cdn.com/asana/original/4X/d/8/4/d84fe9277ff3bff5c1cdf0d7aaa582a9c79ebead.png) ---
**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:** [28 March 2025 12:25 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384/2 "2025-03-28T12:25:07Z")
That would be awesome indeed! cc @Arthur_BEGOU ---
**Author:** ![Phil\_Seeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/phil_seeman/32/81525_2.png) [@Phil\_Seeman](https://forum.asana.com/u/Phil_Seeman)\ **Post date:** [28 March 2025 15:31 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384/3 "2025-03-28T15:31:20Z")
Yes, @Larry_Berger_lpb noted this shortcoming: > [@Improve team onboarding and ongoing collaboration with team knowledge bases](https://forum.asana.com/t/improve-team-onboarding-and-ongoing-collaboration-with-team-knowledge-bases/1026660/3): > > My feedback: I like the feature, but I don’t think it’s responsible to release it when it fails to work in all task and project Description fields, arguably the most or certainly one of the most needed and expected places users would expect this work. It’s an additional problem not to call that out in the Help Center article or announcement of the feature. The Help Center article for Knowledge says (emphasis mine): Entries added in the Knowledge tab can also be found throughout Asana via conte… Larry, I think you’ll want to vote here! ---
**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:** [31 March 2025 06:42 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384/4 "2025-03-31T06:42:17Z")
I agree and voted, too! ---
**Author:** ![AustinA](https://luna1.co/8d76cd.png) [@AustinA](https://forum.asana.com/u/AustinA)\ **Post date:** [12 May 2025 17:22 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384/5 "2025-05-12T17:22:34Z")
I really think this would be the single most impactful feature to spur widespread adoption in my department. From day 1, we wish new hires good luck in learning all our jargon. We have people who’ve been here 10 years and still don’t know it, in part because because it is changing constantly. The ability to reference jargon definitions seamlessly in-context, and manage it centrally (search and/or sorting of the knowledge base would also help greatly, but is less essential) would be a game-changer for so many of my teammates. Currently, this feature is functionally comparable to a dictionary since the contextual hovercards don’t appear in the description field (or in task titles or Notes views!) as you would expect. Please implement this. I don’t know what technical limitation stopped this from being included in the initial release, but from my point of view it really seems like it would be a massive bang-for-your-buck win for Asana. ---
**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:** [13 May 2025 08:26 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384/6 "2025-05-13T08:26:30Z")
> [@AustinA](#): > > Please implement this. I don’t know what technical limitation stopped this from being included in the initial release, but from my point of view it really seems like it would be a massive bang-for-your-buck win for Asana. Asana always do baby steps, but they are listening! ---
**Author:** ![Nick\_Q](https://luna1.co/8d76cd.png) [@Nick\_Q](https://forum.asana.com/u/Nick_Q)\ **Post date:** [29 May 2025 17:14 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384/7 "2025-05-29T17:14:20Z")
The new team knowledge field could be much more useful it activated on terms in the description of tasks, the overview tab, and the note tab. If team knowledge functioned in these places, it would be help significantly with onboarding. ---
**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:** [29 May 2025 18:54 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384/8 "2025-05-29T18:54:17Z")
@Nick_Q, I’ve merged your post into an existing topic where you can click the title to scroll to the top and vote by clicking the Vote button. Thanks, Larry ---
**Author:** ![AustinA](https://luna1.co/8d76cd.png) [@AustinA](https://forum.asana.com/u/AustinA)\ **Post date:** [11 June 2025 17:17 UTC](https://forum.asana.com/t/team-knowledge-recognizing-words-in-the-task-description-field-project-overview-tab-note-tab/1043384/9 "2025-06-11T17:17:24Z")
Note: Not a solution but marked as such to elevate a key reply Wanted to note that after some research, this feature is actually implemented, but in a way that is definitely not useful to superusers posting here, but can be for other users in certain contexts. If you do not have edit access to a field, the feature functions. So you have to implement your projects, workflows, and access controls in a way that limits user functionality to have access to this specific feature. Some examples of where you can see this: - Project Overviews where the user is **not** a project admin - Task descriptions in reference projects, so long as users do **not** have edit access. If a project admin wants to benefit, they will need to hand control over to another user (who would then not benefit) or to some sort of service account - Task descriptions in working projects, so long as access controls are strict and the user is not personally working on the task (lol) - Note tabs in any project where the user does **not** have edit access Realistically, this means this feature is broadly functional for reference projects, for users who do not need to interact with tasks and projects, and for project overviews. It is explicitly unfriendly to project admins. For a tad more technical detail, it seems this limitation is specifically related to the fields with hover-over edit functionality, which is missing from comments and why we are able to see it function there. I assume that is the technical hurdle where feature development thought best to stop for this initial implementation. Despite being more functional that I/we thought, the feature is still limited enough that I believe it highly valuable to expand on.