This a good feature to have. 

To give a detailed context one of the teams in our company is using confluence server version which is been deprecated now. And they are using below plugin

https://marketplace.atlassian.com/apps/1210933/draw-io-diagrams-whiteboards?hosting=cloud&tab=overview

Now they want to migrate to our confluence which has data center license and already configured with Lucid charts. But initially they want to use the draw.io plugin for sometime till migration is complete to Lucid.

So for this team only we want to install the draw.io plugin for sometime and then remove it. However within that period if other start using it then we will not be able to remove it and end up buying it. 

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