Change 'Knowledge'/key definitions from a tab in Teams to an Org-wide object / create an Org dictionary for AI Teammates

The Knowledge tab in Teams is currently an extremely localised dictionary whose access is limited by design to Team association. Given the move to Teamless-projects and a completely interconnected Work Graph, siloing key definitions and context behind Teams does not make sense. This is inefficient for several reasons, predominantly for AI but also for users when editing and sharing key definitions.

If you have an identical entry across Teams - for example, a product name or client description that both Sales and Marketing would need - you have to create that entry as many times as you have teams. If you want to modify the definition, you have to update every entry manually and ensure consistency yourself. A much better approach would be to have a single definition and assign access permissions to it the way we do most every other object in the Work Graph.

More importantly, Knowledge entries represent incredibly useful context that I suspect is being repeatedly and manually typed into AI rule actions or AI Teammate skill files. Being able to reference Knowledge definitions in AI workflows would be so useful. Also, whilst Asana states that these Knowledge entries are considered by AI, it’s unclear how permissions function here, and whether data might be leaked to users that aren’t supposed to have knowledge of Knowledge entries.

My current workaround for AI is to have an Asana Page with most of my Org’s key definitions and context in it that I definitively control the permissions on and can use in a skill on AI Teammates or reference in rules. This isn’t ideal, however, as it’s another thing to ensure stays synced. I’d also love to reference key definitions in Pages themselves!

Side request: definitions in the Knowledge tab only seem to be highlighted when used in a Team’s Overview → Description field. The key words are underlined in blue and hovering over them brings up the definition. This does not happen when using the key words elsewhere for me, like in goals, projects, or tasks. It would be great if key words were highlighted everywhere - it could really help new users get accustomed to a company’s terminology quickly.

@AnAsanaUser,

In case you haven’t already considered and rejected this workaround…

Many of us recommend having an “All” or “All Staff” team that includes everyone, which comes in handy in a few different ways. If you had that, it would provide a place to single-source those org-wide knowledge bits.

Thanks,

Larry