We’re thinking internally of creating security classification as its own metadata aspect that could be attached to lots of things (datasets, containers, dataFlows etc.) The levels we currently have are: Highly Confidential Confidential Internal Public Currently we use glossaryTerms to do this, but have run into the issue where people can assign multiple to the same entity (resulting in a conflict) and we’re really looking for something more like a SELECT ONE (where a drop down menu appears and they can pick one of the different levels of security classification). Just checking if this is something that would be worth trying to contribute back? Or if we should just try and build this ourselves and see. Curious to hear thoughts!

Hey Matthew! Thanks for sharing this use case -- we have some work in-flight for what we're calling Structured Properties that will address this exact use case.. you can check out a live demo I gave at the Oct Town Hall here! Of course, as live demos go, we had some issues with my screen resolution 😅 let me know if anything there is unclear/if you have follow-up questions!