• 1
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      Currently, in order to use a paid plugin in Confluence a license has to be purchased that matches the user license in Confluence. This causes an issue, for example when an instance is set up for 2000 users, but only ~100 users use this macro.

      Suggested Solution

      Allow for smaller licenses to be purchased, and set up plugin permissions to only allow the amount of licensed plugin users to use the plugin.

      Workaround

      No existing workaround other than purchasing the full plugin.

            [CONFSERVER-52322] Allow for smaller plugin license based on usage

            frog added a comment - - edited

            Disappointing to see this rejected/delayed like JRASERVER-59932.

            We're on a 250-user license for confluence for the organisation and cannot justify the cost of a 250-user license just for a team of 30 to have some additional plugins. As we've grown in total users, we've stopped renewing plugins and are finding free alternatives for anything that's not used across the majority of the organisation.

            frog added a comment - - edited Disappointing to see this rejected/delayed like  JRASERVER-59932 . We're on a 250-user license for confluence for the organisation and cannot justify the cost of a 250-user license just for a team of 30 to have some additional plugins. As we've grown in total users, we've stopped renewing plugins and are finding free alternatives for anything that's not used across the majority of the organisation.

            Thank you for raising this suggestion.
            We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
            For more context, check out our Community blog on our updated workflow for Suggestions
            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our updated workflow for Suggestions Cheers, Confluence Product Management

              Unassigned Unassigned
              dponzio Daniel Ponzio
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: