Global classes in Bricks are added to the individual element itself (as Yan illustrated in his last reply).
I agree that this isn’t ideal as the CSS rules defined on the class itself are only available in combination with the element. And it’s something we have to address in a future update. To manage expectations: It’s not a small feat, and not something we can tackle right away.
The reason the classes are applied this way is because Bricks doesn’t have a per-element CSS selector for individual element settings (at the moment). Those selectors are defined via PHP. In order to make global classes apply their styles to the same selectors, they are bound/linked to the element. Otherwise element ID styles & global class definitions would lead to mixed results on an element.
@khan360 Unfortunately, as of right now, all I can advise to is adding the global class definitions (of classes you programmatically add via JavaScript) via the “Custom Code” in the global Bricks settings.