thank you Barry - the design approaches this from two directions: 1) what part of the @org-design does this card on the strategy tree belong to? and 2) who will I add as members, so they receive notifications of all key things taking place on that card? That is, 1) drives the filtering/browsing, and 2) drives the collaboration. For example, you can tag a "strategy sub-action" to "marketing" [see attached image], then separately under the members tab decide who in marketing will be responsible for that card, making only those people the members, rather than the whole marketing team. Of course, if you instead want to add everyone to everything, you can do that in seconds per card using @org-design; although we recommend only adding as members the people who you want to receive notifications. Others in marketing and the wider org can still browse and contribute to right-hand-side social, providing the security level is "restricted".