What does "share with group" do?

Other than allowing "deed to group", what does "share with group" do?

Does it give avs wearing group tag permissions on the object? Specifically which ones?

What does it mean for object contents, if the object is shared?

What does it mean for object contents, if both object and contents are shared?

Thanks
Jeff

To edit scripts or notecards in a group deeded object, I have to open it up and set the script or notecard itself to "share with group."

Share with Group doesn't seem to do much for the item itself. Perhaps group members can take a copy if it's copy/transfer?

They can take, move, copy, etc. within the limits of the permissions. They can also retexture shared items.

"Share" is probably the most redundant option ever, unless you wish to allow other group members to work on the object.

Generally, it's advisable to leave this option OFF, since you need only one malicious member to take it away, change it, whatever.
It's really an odd option between "Set to Group" and "Deed to Group". Even Deed to Group is probably a safer option for your items than Share with Group is. So just don't use it, unless the object isn't transferable, while other group members do need the ability to edit it.

Share with group can be very handy in situations where you have a group of people all having objects on land set to the group. I have 10 or so people with objects rezzed in the Gardens and I ask them all to set their stuff to Share With Group so that I can move them around when I need to reconfigure. I can drag/copy items with copy perms but the new copy retains the other person as owner.

Contrariwise, once you've finished the build, UN set Share With Group...and Lock the object as well. This will prevent, for example, tenants from taking copies of/taking originals of/moving/deleting/messing up your beautiful build.

I’ve seen several scripted objects that use group membership as a way to set permissions such as unlocking doors or using an animations.

Thanks folks, very helpful. The sticky about permssions covers it slightly, but the additional info here rounds it out nicely.

That can be done already by just setting the object to the required group, there is no need to also share the object to allow it to do that.
Seriously, if you do not want others in the group to manually alter or remove or whatever an object, then by all means, turn off that share option, just to prevent other group members to mess it up, whether that happens accidentally or intentionally.

There have been plenty of groups where members accidentally picked up or moved an object that was supposed to stay put. There have also been plenty of groups already where (ex) members intentionally stole contents from scripted objects (breaking the functionalityof them in the process), changed textures (to something like "this place sucks" for example), moved objects hundreds of meters up in the air, broke walls out of private rooms, resized prims on intricate designs, etcetera. Just because the object was SHARED with the group, instead of only being SET to the group.

Most of the time that you really want someone else to edit an object of yours, you'll be able to give him/her those permissions in your friends list, and trust him/her enough not to abuse it on other property you may have.
If you trust people a little bit less on that, but enough to work on said item, just give them a full perm copy of the object to alter.
Sharing with a group should only be done if you indeed want the whole group in on it, and this is usually only an issue in small groups of cooperating builders, maybe also in a partnership group, where you and your spouse are the only members.

See http://jira.secondlife.com/browse/SVC-585.
Note that Soft Linden would like to add an extra group permission checkbox for "access shared objects" so we might actually decide what it does.