Global tags

global tagging represents a significant advancement over existing capabilities, which were previously limited to account level functionalities this global approach enables the creation of universal tags that can be applied across all accounts within bridge, thereby enhancing the efficiency of administration and management this streamlined process reduces the need to manage numerous identical tags across multiple accounts, especially when dealing with large quantities of tags and their corresponding values main considerations administrators are responsible for maintaining and organizing the global tags the “global ” prefix has been reserved for global tags the system will automatically add this prefix, so there is no need to add it manually global tags can only be created from the bridge operations account, and global tag definitions can only be managed from this account once a tag is created in the global control pane, it gets added to the tag repositories of all accounts in bridge for example, if a tag is created and classified as global with the key "env," it will be represented as "global env," this tag will be compliant even at the account level tag repository because the tag definitions for it exist in the global tag definition the "global " prefix is prohibited in non operational accounts, as it is designated only for global tags created from the operations tenant to get started, open the global menu and select control tower this central hub allows you to manage various functions across multiple accounts in the tag management section, you'll find the global tag definition and global tag repository features global tag definitions the tag administrator can only create a global tag key from the global tag definition, available in the operations tenant once an active global tag key is created, it will be available in the tag repository of all other accounts in bridge all capabilities are available for the standard tag definitions docid\ bk pjyh9cgzyhqfxthev3 also apply to the global tag definition, such as view details access detailed information about the current definition edit open the related definition in edit mode, with key name, type, and state as read only use as template aliases and tag keys are not pre populated delete ability to delete the current definition provider and resource docid\ bk pjyh9cgzyhqfxthev3 type scope applies to global tags, and the change history functionality remains unchanged from account level tags upon creating new tag definitions, the risk of duplication is eliminated creating a new tag labeled "os" will follow the same validation rules, preventing duplicates global tag repository tag administrators can only create a global tag from the global tag repository global tags are ' read only ' in tag repositories of other (non global) accounts all capabilities available for the standard tag repository docid\ fmc8 wunznzvenbj11jsi also apply to the global tag repository, in which the user can add tags to the tag repository in multiple ways, as described next capability 1 add tag values to the tag keys created from the global tag repositories if the user adds tag values to these tag keys that are outside the allowed values defined in the constraints of the definition, an error message is displayed indicating that this action is not supported capability 2 create and save a new key or value pair directly within the global repository capability 3 import tags to the tag repository page can also be done for global tags the global tag repository only displays the global tags, while the account specific tag repository showcases both global tags and account level tags all the other capabilities of the tag repository docid\ fmc8 wunznzvenbj11jsi also apply to the global repository, such as delete conditions global tag deletion is only allowed in the bridge operations tenant view tag details access detailed information, such as compliance