Permissions explained

Permissions
===========

The permissions system is designed to foster the best possible content and sanctify the best possible experience in Second Life. We track four basic permissions - move, modify, copy and transfer. The move, modify, and copy permissions can be applied to four categories - owner, group, everyone else, and next owner. By applying different permission sets to different categories of people, you can control how items you create in Second Life are used and distributed.


Example Applications
====================

* You want to sell some clothing that someone can alter, copy into new outfits, but never sell:

YES: next owner modify
YES: next owner copy
NO: next owner transfer


* You want to sell someone a single motorcycle that they can change the shape and color, but cannot examine or modify the script:

bike -
YES: next owner modify
NO: next owner copy
YES: next owner transfer

scripts -
NO: next owner modify
NO: next owner copy
YES: next owner transfer


* You want to sell someone a texture that they can use to wallpaper their entire house, but they can never sell the texture or anything textured with it?

YES: next owner modify
YES: next owner copy
NO: next owner transfer


* You want to give someone a whole bunch of useful stuff with some comments explaining everything. Put it all in a note card!

YES: next owner modify
YES: next owner copy
YES: next owner transfer


* You want to build a fortress for with your group, which will continue to evolve to meet group needs after it has been deeded.

YES: share with group
YES: next owner modify
YES: next owner copy


* You have built a statue that will be deeded to your group, but you do not ever want it to be altered or incorporated into other group projects.

YES: share with group
NO: next owner modify
NO: next owner copy
YES: next owner transfer



Permissions Settings
====================


* Modify

If modify is enabled, you can edit properties like item name or object scale. Modify permissions also grant you the ability to delete an object - for example, if an object has been shared with group in world, then any member of the group can modify, and therefore delete the object.

When an object is next owner no-modify, that permissions setting is interpreted as 'no one can create derivative works.' For example, if you sell a motorcycle without modify permissions, the buyer cannot make a slightly longer or re-textured version of that motorcycle without building one from scratch.

If an inventory item inside of an object is no-modify, the object itself can still be modified. Conversely, if an object is not modifiable, it's contents cannot be modified.


* Copy

If copy is enabled, you can make as many copies as you want of the original item. Copies maintain creator information, and can never be more permissive than the item being copied.

The copy property applies outward. If an inventory item inside of an object is no-copy, the object itself cannot be copied until that item is removed. Conversely, if an object is no-copy, that does not imply that the contents are no-copy .


* Transfer

If transfer is enabled, the owner can transfer the item to another person. If an item is not transferable, the owner cannot sell, give away, release or embed in something they sell, give away, or release. The transfer permission only applies to the owner, since no one else can initiate a transfer.

During a transfer, the next owner field is copied into the owner field and dependent permissions fields are recalculated given the new owner permissions.


* Move

If move is enabled, the object can be moved.



Categories
==========

The permissions track four primary categories for each object - owner, group, everyone else, and next owner. Each category has its own set of permissions. Group and next owner permissions can never be more permissive than the owner permissions field. The everyone permissions field can never be set modifiable, and can never be more permissive than the group field.

Group owned objects conceptually collapse the owner and group categories into the same value.



Fair Use Rights
===============

To further the goal of best possible content and best possible experience, the permissions system comes with a set of fair use rights. Fair use rights apply to the owner of the item.

* Deletion - you are always allowed to delete something you own.

* Move - you are always allowed to move anything you own.



Right of First Sale
===================

The right of first sale applies when an item is transferred without next owner copy. Since you are allowed to specify no derivative works by specifying next owner cannot modify, this right is interpreted as next owner can always transfer that single instance of the item to anyone else.

Great info. Thanks, Phoenix!

does that also mean they can't give it to anyone else?


does that work with textures in clothes and tattoos too so they couldn't sell (or give away i hope) any clothes or skins they make?


are these the permissions for the notecard or the useful stuff in it? i'm totally confused by this one. and can you put objects in notecards? do they keep their permissions or take those of the notecard?

and if you give someone modify permissions to your things do they have the exact same rights you do to all your things? or do these permissions still apply?

There can be no distinction between giving and selling (as far as the system is concerned) because, even with selling blocked, you can still arrange to have someone pay you in return for "giving" them the item.
The permissions are for the notecard, in that example. Anything in a notecard is just like it being in a box, with the same permission restrictions. (I've never done it, myself, but I think you just drag an item into a notecard to add a "hyperlink" to it that people can then click to take.)

yes, but what about the bug where it the object is created by "nobody)" i have had this happen to me several times, Lee even forced full permissions and it did not help a bit.

Whoa, weird, and it wasnt a ghost either?

I haven't seen that bug since pre-1.1.

Ooh I think I noticed one of my thingys created by "nobody" a few days ago, didn't really think much of it. It was probably a piece of junk I really didn't need.

Permissions are unfortunately broken now I can't set object permissions inside the contents of something, thus I can't rez things with specific permissions, which stinks. Think this can be fixed, seeing as how it ruins some things I'm trying to do...

Hiya Phonix, may i take a copy of this and put it on a note card and offer it up for free at Freebies, Inc.

I think its very informative and useful.

Thanks

Cath

PS; last time I checked the "copy" was broken so I have everyone set their freebies for sale to L$0 now. (Thanks Cubey for pointing out that bug!!)

Dave,

If I remember correctly, the ability to edit object permissions in the inventory was deliberately removed in v1.2. The problem was that the permissions set in-world and in-inventory didn't match, which led to *hilarious* consequences

I'd like to see this feature re-implemented. If it works, it would be very useful.

Thank you so much Phoenix! Such vital information and so well presented.

I'm building the Ivory Tower Library of Primitives which is meant to be a complete resource on prims and building. May I please use this information in the library?

Thank you!

Lumi

Ok, I'll bite...

There is an instance that is not covered I think. Or a bug in 1.3.4, Or I don't understand the system.

Example:

Object: (next owner settings)
Mod on
Copy off
Resell/give on

Script: (next owner settings)
Mod on
Copy off
resell/give on

I DO want the next owner to be able to edit settings INSIDE the script (to change performance characteristics).

But this does not seem to be the case with these settings (in SL 1.3.3 or 1.3.4). Is there not a way where the next owner is allowed to edit the contents of a script, but not move it to their inventory, or copy it to another object?

I understand that they 'could' copy all the code from within my script and paste that into a new script. This I am not so worried about, as I just want a way to 'keep honest people honest'. those who would steal the script and use it as their own, will get what they deserve in the end.

Set aside the issue of someone stealing code in this mannor. If I want folks to edit the script but just not easily move the script to other items. Is there no combination of settings that would allow this scenario?

Any and all clarification on this is greatly appreciated.

Mickey

As far as I understand it the perms aren't that fine-grained.
If you give someone mod perms they can pretty much take your object and pull it to bits, if they like. *shrug*

The usual way of user-configurability at the moment (such that I'm aware of anyway) is one of two things:
1) The script takes chat commands in-world, and keeps track of its state, so you'd say something like "/topspeed 30", and it would store that.
2) The config details are stored in a user-writable notecard in the object. Object has mod perms, notecard has mod perms, but the script does not and is therefore locked. Good for vehicles with alot of config options, and also allows you to have comments related to each vehicle parameter so the user can get a handle on what they do.

Seems like permissions changed in last 3 months?

Before, if you made an object nomodify, clients couldnt drag stuff out of it to their inventory?

Now, it seems you can, which seems undesirable.

Is this a deliberate change or is this a slip in a recent release?

Azelda

Mickey, scripts require both Mod and Copy set in order to be viewable. If you set one or the other it will not show up. I assume the reasoning for this is because code can be copy/pasted if you can see it. Therefore, modify implies copy. I'm not sure if mod has any real effect except to work in tandem with the copy bit.

As for the most desirable set of permissions, I'd suggest mod/copy/no-transfer. Someone can still copy/paste the code but cannot actually copy and use the script item directly.

Thanks Phonix! Could you start a thread on "Groups Explained" purdy please!

Cath

That becomes difficult when you want to create something that uses that script and then either give it away or sell it and you can't because the script involved in the item is no-transfer.

I agree, having a script MOD/COPY is just the same as making it transfer too, I think anyone willing to sell on your scripts is willing to copy and paste.

Permissions seem to do such weird things, I dont know if it's me or there is some trick to it or what!

I link together something I made (everything, all of the prims and textures are mine, and it says that the creator is me). Sometimes I can "Take Copy", sometimes I cant. Sometimes when I "Take Copy" it says "no transfer" in my inventory. But I cant modify the permissions on the thing at all. When I go into edit mode, it says I have modify permissions, but all the permission boxes underneath it are dimmed out and I cant check or uncheck anything.

Please help!! I want to sell my land, but I want to copy my building to put it on the next place I go to. Right now, it is too frustrating

Excellent!

Thank you Phoenix.

I can't seem to uncheck the transfer button on my furniture that I make and sell.... ? Ideally i'd like no modify, no copy, no transfer.

objects must either be transferable or copiable.

by checking transferable you insure that you get paid for every instance of your furniture.

thanks Jau!

Good point. Disallowing any permission on a script, should automatically disallow viewing of the script, as all three of the permission restrictions on the script can be bypassed, if any and all forms of viewing of the script is allowed. (This even includes viewing without being able to select the text for copy/paste, as people can manually type it out, after taking whatever screen shots they need.)