Usage

• 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 Macro Security for Trusted Spaces.

• 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 the 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 the macro before it works on any installation where Macro Security enabled. 

Legend 

Column	Description	Example Configuration
Use Restriction	means macro can only be used by authorized users	sql = confluence-administrators
Parameter Restriction	means that one or more parameters can be restricted in total or by value if the parameter indicates this specifically	sql.datasource.* = confluence-administrators sql.datasource.testDS = *ANY
Controlled Parameters	List of those parameters that can be restricted or restricted by value

Enabled Macros

Please note that both the parameter names and values are case-sensitive!

Examples

The Example Configurations page provides sample app configurations you can download and import to use as the starting point for your Macro Security configuration.

Configuration Tips

See Configuring and Enabling Macro Security for basic information and Key Concepts to learn about Macro Security in general and to review several example syntaxes.

• 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.