Would it be at all possible to decouple "Create Objects : Group" from solely the group that owns the land?
Let me quickly outline:
Our land is owned by the 'Luskwood' -group- which really is only meant for the four of us who run the place. Since there are other security "issues" with inviting every Tom, Dick and Harry into the primary group that owns the land --
we have most regulars and residents in a "Luskwood Residents" group.
We'd like to grant -them- ability to create, without inviting every single one of them into the same group that owns the land, object, scripts, etc.
Simply a pulldown that would say: Create Permitted For Group: (group name).
Would that be feasible? It'd really, really, solve a whole lot of problems -- including caging and 'prim griefing'.
Just to underscore: some folks do use disparate groups for different things like this, and honestly I think it's a good way to keep future problems from cropping up.
I can't really see any -negatives- in it, unless it's somehow not workable in the system.
As it stands, if the "group landowner = only allowable create group = only allowable entry group" model persists I'm worried that we'll *never* have any way to stop caging/prim griefing without inviting EVERYONE into our primary group, which opens up a whole new can o' worms.
(There are still issues and behaviors that make inviting the general public into a group which owns the land and a majority of objects on the land... plus it kind of opens up the door for more chaos in future exploits and bugs... We'd really like to keep a wall of separation between the group which owns the land and the general public, but still allow a 'general' group to create on our land, without letting the entire world do it.)