The basis of Macro Security is to prevent certain “restricted” macros from being deployed or edited within Confluence pages by unauthorized users, unless the edit restrictions defined for the page match the security restrictions defined for the macro OR the macro has been configured for and is being used in a space referenced by the Trusted Spaces approach for Macro Security.
In some cases, you may opt to secure only specific macro parameters rather than the entire macro.
Once a macro (or a macro parameter) has been configured for restricted use, you need to review any existing Confluence page that uses that macro to ensure its page restrictions match that macro's newly configured security restrictions.
For enabled macros that are marked as Use Restriction below, a security configuration entry is required for that macro before that macro will work on any installation where Macro Security enabled.
Set less specific values first, then more specific.
Use generics to set parameter values if necessary. Example: sql.datasource.* = confluence-administrators.
Use *ANY to not restrict a specific setting. Example: run = *ANY.
Set a value for every macro that can be controlled (for instance, a value of *ANY). Lack of a value normally means it is not authorized.
If a page containing a restricted macro will be viewed or updated by a user using remote REST APIs, including an account used for automation purposes, that Macro Security configuration must give that user authorization to use that restricted macro.
Macro security is not available on Cloud (OnDemand). Behavior of macros for Cloud is the same as if Macro Security was not installed.