• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: VWR-8634
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: StarSong Bright
Votes: 9
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
1. Second Life Viewer - VWR

Prim Permissions - make this more intuitive!

Created: 20/Oct/07 01:28 AM   Updated: 12/Aug/08 07:10 PM
Return to search
Component/s: Permissions
Affects Version/s: None
Fix Version/s: None

Environment: all
Issue Links:
Duplicate
 


 Description  « Hide
The current way that permissions are handled on prims is very cumbersome. ESPECIALLY WHEN BUILDING AS A TEAM. I would like to propose the following:

On bulk upload (textures for example) allow the permissions to be set before the upload begins so that it is not necessary to go back to every item in the back and click all the buttons to set permissions to all.

Give us a preference for the DEFAULT PERMISSIONS of all of our newly created items. I am mostly working with a partner these days, it would be helpful to me to be able to say in my preferences - "Ok, everything I make right now has full perms until I change this setting again". In large builds it is SO difficult to catch every little prim and set it. I want to just be able to create and not worry about this crap until the end when I am done.

Add some sort of "cascadability" to permission setting to allow multiple items to change permissions at once. I realize you can select multiples and sometimes you can reset them all at once, but the process doesn't seem to work consistently for me. For example, the ability to change all the permissions on all the children prims in a linked object, so that if unlinked all of the prims keep the permissions of the top linked item. I want the ability to apply permissions from the top down - "apply perms to this object and all its children".

I find the way the permissions work on scripts inside my prims when working at a team to be completely counter-intuitive. My partner and I have been having serious issues when he adds a script to one of my items and then they wont be editable to me or cause other problems with the prim. The only thing that seems to work is to have every box checked in the perms, but this leaves us with the question of what happens for the next owner of our objects. The problem seems to stem from where I am the prim creator and he is the script creator.

I almost wish there was another level of trust for "mod my objects".... It would be scary but... it would be helpful to be able to give a partner builder full "treat him like he's me" rights to the things I am building. Just the objects i am the creator for (not things i own necessarily) - so that if my building partner wants to copy a window i made and use it elsewhere in our build he doesn't have to worry about if i have set the rights or not. But this last thing may open other cans of worms. I think that if i had a way to set the preference for the perms on my prims overall as i am making them that this last thing would not be necessary.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Lex Neva added a comment - 20/Oct/07 10:03 AM
Very much agreed on the upload permissions. I'd love those "default upload permissions" settings in my preferences. I want everything to be full-perms AND shared with group, since almost everything I do in SL is group work.

As to your problem with scripts: when your partner drops a script into an object you own, an ownership transfer is processed, and the script's next-owner permissions are applied. This means that the script will lose permissions if you're not careful. Also, if your partner didn't click "Share with group" in the SCRIPT'S permissions before dropping it into your object, he won't be able to edit the script once it's in your object. It all makes sense, but it definitely is cumbersome.


Bill Friis added a comment - 30/Jan/08 02:03 PM - edited
This is really four proposals.

1) Be able to set your default permissions so that everything you create after that automatically has those permissions. This is a great idea. It should probably return to normal on your next log in, but maybe that could also be an option.

2) Be able to change the permissions of multiple objects at once. Another great idea. And already proposed. See: SVC-593 A comment there links to Torley's workaround video, which just emphasizes how much nicer it would be to not need the workaround.

3) Be able to change permissions of an object and all its linked / contained items at once. There is a proposal, MISC-626 , which asks for this for scripts. But really, you want it for everything contained in an object including other objects which contain notecards which contain objects which contains sounds and scripts, and textures, etc. You make a house with many cool scripted features, sounds, changing textures, temp on rez goodies, and when you are done, realize that you want to give it away. Heaven help you. I know of no reasonable workaround. Educators who want students to turn in projects for grading are having a big problem with this.

4) Be able to set another avatar to modify your objects exactly as if that avatar was you. You are correct, having the first three would render this "scary" proposal unnecessary.


McCabe Maxsted added a comment - 12/Aug/08 07:10 PM
Duplicates a number of issues. You should look at them and reword your issue accordingly, keeping it focused to a single task (i.e. a new setting more permissible than "edit my objects", or expanding that).