Hi!

I'm currently working on and off a Galene management interface in Pyrite (Screenshot shows some initial work, branch is at https://github.com/garage44/pyrite/tree/feat/9-administration-interface).
The basic idea is that a manager can easily switch between conference mode and manager mode with two separate logins(one for user groups
and one for the manager section). So far, there are two planned features:
* Groups Management
* Recordings Management

Groups can have users assigned to them (through op/presenter/other), however I would like a central place to manager users (a users.json or similar).
Modifying a user there (e.g. a password change) would mean updating all user references in group files as well. This should work, however I'm
curious whether there are alternatives to this.

Also, I don't know yet how to deal with actions like group renaming or deletion. The file action itself is not that complicated, but how
would Galene respond to a removed/renamed group? I assume the group is kept in memory? Should I connected the Galene manager
backend with Galene itself (using protocol.js) and kick all users out, before attempting to remove the group for instance?
If so, would it be an idea to introduce a 'hidden' superuser, that can act on behalf of such a backend without showing up
in the Galene user list?

Jeroen