Moving my comments to Cloud Version of this issue/request.

• Confluence Cloud: https://jira.atlassian.com/browse/CONFCLOUD-39235
• Jira Cloud: https://jira.atlassian.com/browse/JRACLOUD-59932

Please consider visiting, watching, and voting for both of the issues listed above.  

This feature is definitely necessary for our organization. I would love to see this prioritized! 

This would be useful in regards to the HTML macro. We require the HTML macro to run javascript in HTML but need to restrict non logged in users from using the html macro

This is not just cost-oriented.  It could be the scenario of canary deployment where one wants to confine features deplyment to a small set of users for analyzing risk and security, etc., prior to deploying to the entire Confluence site.

We are looking for ability to have control so that we can enable and disable plugins and add-ons for specific spaces.

We want to restrict certain macros to admin usage only.

We would not expect to lower the cost or otherwise affect any add-on pricing; we simply want to control usage of the item(s) we paid for.

This would be great as it mean's you have more control in terms of Macro Costs'

Hi!

 Talk - Advanced Inline Comments has a feature that allows setting visibility restrictions for the comments on a space level or/and for the specific comment thread. Say, you want your comments to be visible only internally. You can set space permissions for the comments only for a group or/and users who can view them. However, any user who can make comments can change restrictions for specific comment threads.

This means, that by default all the comments in the space will be visible only to the groups and users listed. But if a user wants to change viewing for a specific comment (for example, to discuss something privately or restrict comment only for himself), they can do it.

+1

only need one or two users to have access to gliffy diagrams but will be getting charged for 25 confluence users who will not be using the add on but will only want to view the diagrams written in the documentation.  Definitely needs to be considered as an improvement as we are likely going to have to just live without the add-on due it being too costly.

Limiting the users adding macros on a single page would definitely be a good feature and help resolving 502 page load errors for the the pages which have abundance of macros to be loaded.

Would be great to enable more risky plugins like iFrame to only certain key users.

The [Macro Manager for Confluence |https://marketplace.atlassian.com/apps/1220598/macro-manager-for-confluence?hosting=server&tab=overview] allows you to restrict macros to the confluence-administrators group. Maybe this could be a start?

Doesn't make sense from an administrative standpoint to put editing restrictions on pages when macros allow for contents to be edited without strict permissioning.

inline commenting macros make sense to allow edit for form fields but macros like staffing tables makes sense to offer view only.

I search for this function, because we need this to restrict our macros or add-ons in Confluence.

Some macros should not be used by the end users.

I'm currently evaluating Seibert-Media's Space Privacy "extranet for Confluence" plugin and it sure would be nice to restrict who can use the add-on to create extranet spaces; The add-on itself doesn't provide this ability (from what I can determine).

+1

+1 

Even the Bob Swift does not restrict Confluence macros, only their own. 

+1 needed urgently!

Buying another Addon (Macro Security, would be 4000 USD in our case) to restrict the other addons cannot be the solution

+1
Need this!

+1

+1

Ditto!

+1

Same for us.

+1
Even if it is an older request, we have a similar requirement, but not to spare licence cost. We only want to make sure that some plugins that aren't easy to handle can't be used by anyone. But it's not possible to restrict the user permissions by page or space, because they must be able to see and even edit these pages only without editing the specific plugin macro.

+1
But be aware that with this your are possibly introducing the thing everyone's want with marketplace licensing and which was existing before Marketplace licensing
The ability to restrict Add-ons to group and so to pay only for that users count.

For that reason I doubt that Atlassian will introduce an option for restricting Add-ons to a group.