Gliffy

As it stands the gliffy license must match the confluence license in terms of the number of users. We have roughly 80 users of Confluence and a license for 100 users. Of those 80 users a group of at most 25 users will need access to gliffy functionality. therefore, we have licenses for 55 more users than we need. A bit of background on the issue: We've seen a similar issue before with the Balsamiq confluence and jira plugins. Balsamiq checked for it's users in a special group that the user needed to manually create called mockups-editors. If the number of users in this group exceeded the Balsamiq license limit, the plugin would cease to work until numbers were reduced. Our problem was that we use Atlassian Crowd for user management for both Jira and Confluence. When Confluence and Jira each use their own user management, it's not a problem, as they can both maintain a user group called mockups-editors with different users in that group within Jira and Confluence. However, when using Crowd, only one group could have the mockups-editors name. So both Jira and Confluence looked to that single group to check the number of licensed users was not exceeded. So even though we had valid license for 10 users in Jira, and another 10 users in Confluence, we could only have 10 users at any given time for both combined. The solution the Balsamiq developers came up with was to keep the remaining mockup-editors group and also add mockups-editors-jira and mockup-editors-confluence groups that would capture which users were to allowed to use Balsamiq in which application. The general idea here is that it would be useful if there was a specific user group for the jira plugin and another group for the confluence plugin. This would have the following benefits: 1. Users could only allow a subset of the complete confluence-users group access to gliffy functionality 2. The seperate user groups will ensure that gliffy plays nice with Atlassian crowd. I realise that you might lose out in terms of the revenue you currently obtain from what are currently dead licencees (like us, with a 100-user license when all we need is 25), but you'd also make the plugin more attractive by disconnecting it from the number of licensed confluence users, which might prevent people from buying the plugin in the first place