Hi everyone, i have a question regarding usage of Glossary through UI and access policies. Is it possible to create such a set of policies and/or ownership assignments that would let a group of users have all of the following permissions : 1. view all terms in glossary 2. add new glossaryTerms only in one designated glossaryNode/"Term Group"; let's call it Inbox or Draft ◦ this is a core question - i don't see this is possible at the moment, but maybe i'm wrong 3. edit only glossary terms that they are assigned to as owners (wherever in hierarchy of glossaryNode/Term groups they are) ◦ i see that this kind of policy can be formulated And what follows is a bit longer read for anyone who might be interested in the idea behind this and why i ask this .... :-) In essence i'm investigating if it is possible to simulate some kind of a l*ight workflow with what is available in DataHub an this moment*. I want people in group A to be able to add new terms freely and work on it's definition/documentation in a specific glossaryNode (Inbox/Draft) and when they think they are finished i would like a another group of people who would be glossary admins (group B) to review them (naming, basic quality of the description, classifications) and move those terms from Inbox/Draft to the most appropriate place in glossary node hierarchy. This is the time when a glossary admin could also assign the owner of the term (either original group A or some other group C) Those owner groups can than further update and maintain this term documentation, if changes would be needed in the future. But essentially, once the term is moved out from the Inbox/Draft glossaryNode it can be considered as "published" Basic idea here is to let a group of people nominate and start working on terms on their own, directly in DataHub, but not have them create it wherever in hierarchy they want before some group of experts review the naming of the term; basic quality of description and classifications. In effect, we would like to visually separate terms that are in draft from those that can be considered as published and have some kind of enforced gatekeeping between those two stages. If i would be able to establish the permission policies (1-3) listed at the beginning of the post; this approach with a special Inbox glossaryNode might serve us well. Any other creative ideas on how to approach it are welcomed :-)

Great question - thank you for the rich details. @bulky-soccer-26729 has been working on something similar to this for the past few days - It will be available in Acryl's cloud version of DataHub. cc @loud-island-88694 to follow up!

Any plans to make it open source as well?