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.
|Use Restriction||means macro can only be used by authorized users|
|Parameter Restriction||means that one or more parameters can be restricted in total or by value if the parameter indicates this specifically|
|Controlled Parameters||List of those parameters that can be restricted or restricted by value|
Please note that both the parameter names and values are case-sensitive!
The Example Configurations page provides sample properties files you can download and use as the starting point for your Macro Security configuration.
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.