Use Restrictions - 4.x

Description

Each macro that can be restricted must have at least one entry in the Macro Security configuration scree. This is known as a Use Restrictions.

For example, the Cache macro might have an entry that looks like the following:

In the above example:

  • "cache" is the Macro being restricted..
  • *ANY is used to denote that anyone (any user) can create and edit content that uses the Cache macro, effectively making its use "unrestricted."
  • The"confluence-administrators" group can create and edit content that uses the Cache macro. (Content using the Cache macro would require an "edit" page restriction indicating only members of the "confluence-administrators" group can edit the page or, alternatively, an "edit page restriction to one or more userids who are members of the confluence-administrators group.)
  • The specific user "bob" can create or edit content that uses the Cache macro. (Content using the Cache macro would require an "edit" page restriction indicating the user "bob" can edit the page.)
  • Content within the space having a spaceKey of "ds" (Demonstration Space) can use the Cache macro. (The space would require space-level permissions that indicate only trusted users and/or groups can add pages, blogs or comments. These trusted users and/or groups need not be listed in the configuration entry—like this one—that uses space-based Macro Security.)

Log a request with our support team.

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.