...
As with any security implementation, you should develop a plan for what needs to be controlled and who needs to have access. Access can be given to individual userids or groups. In many cases, confluence-administrators is likely one such group to whom you provide access. Also, review Macro Security Managed Macros to understand what elements can be controlled.
...
| Table plus | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Steps for Use Case #1
- Install the CMSP add-on.
- Do not enable security from the add-on's configuration page.
- Create and edit a macro-security.properties file that allows only the access you have planned.
- Go to a convenient location in Confluence and add the file as an attachment. Using an attachment is convenient as it is automatically versioned by Confluence for future reference and change control.
- The file can be named differently if needed.
- See Example Configurations to review some sample configuration files you may wish to use as a starting point.
- See Key Concepts to learn how the the properties file Use Restrictions and Parameter Restrictions work.
...
It is a best practice to create a page for your Confluence user community that documents how you've configured Macro Security. This guides them as to the "edit" page restrictions they must add to any page that will be using a restricted macro, and what spaces you've configured to use Macro Security for Trusted Spaces.