Data Governance based on Tags or more flexible security policy for Tagging

Is your feature request related to a problem? Please describe.

There is an incomplete list of actions and restrictions on working with tags in the policy.

The existing tag policy does not have the ability to restrict the use of a tag only for its owner. Also it would be great to have the ability to apply some tag conditions.

Describe the solution you'd like

We have data managment rules which base on LDAP Access rules. Management will show its intention by affixing the appropriate tag on some Datasets. After that, some code will have to be put into action. The code run on Thrid party platform or etc.

One of the main use case is to request dataset by one team from another by tagging datasets. exp: Marketing team want to request dataset which owns by Sales team. So Marketing person who is memper of ldap group Marketing and this group also owns tag Marketing put this tag to Sales dataset. After this action it thrid party code identify changes and run some code on Data platform. in term of tag condition in the policy also good to have conditions which alows to add tag Marketing if other tag like “online” exist on some dataset. I would also like to say that the Sales team can remove the “Marketing” tag even if it is not the owner of this tag because the sales department is the owner of the dataset.

Describe alternatives you've considered

Just run a thied party code to identify tag changes and make some checks and run some code if checks are “ok” else delete just setted up tag (if checks are not ok)

Additional context

The tags as itself give us an unlimited possibilities to manage data. There are should be a flexible enough solution to own tag, apply it, delete. etc. All those things make Policies more usable.

More context and workaround in Slack: https://datahubspace.slack.com/archives/C02QMLWJG12/p1693310820544549

Current tag policy options:

(there is no policies like “add this tag if you own this tag" etc..)