context
I manage a fairly large instance of Confluence (13k active users). We've grown quickly and a few things have become apparent to me as this has taken place.
The largest of which centers around Confluence's out of the box permission system. It's a fine system when an instance is relatively small. The granularity isn't an overhead.
problem
However, it quickly became a significant operational cost (not only to myself, but also to the wider user base). The reality being, what is loud and clear from the large group of people who have to add and remove people from space permissions lists is that a better solution needs to be developed, so we started tackling the issue.
The obvious answer was groups, however, you can't expose groups in such a way that a simple space admin user can access them without giving them far more than just groups, and I don't want to open up groups to a wide audience anyway. That's a bad decision.
our solution
So, with the help of Confiforms and Scriptrunner, we built access through APIs to the groups functionality such that, when a space is provisioned, it's provisioned with an admin (eg, spacekey-admin), edit, and a readonly group (if the requested space wants restrictions), and a space admin level user (with no back end access) can interact with a form to add and remove users from their space specific groups in real-time.
It works, and over the past 12 months, it's been a life saver drastically cutting down support requests and the rest.
question
I wanted to ask, are there any plans to formally introduce a system like this to the product? When your user base scales, it's about short, simple interactions and the space permissions page is generally not that.
