[#SVC-2621] Meta-Issue: New/modified permissions

2. Second Life Service - SVC

Meta-Issue: New/modified permissions

Created: 08/Jul/08 06:54 PM Updated: 21/Sep/09 01:40 PM

Component/s:

Permissions

Affects Version/s:

None

Fix Version/s:

None

Issue Links:

Parent/Child

This issue parent of:

SVC-4842 Additional Permission options based on account status, with server side checks and stops.

Relates

This issue Relates to:

SVC-1083 revocable transfer permissions

SVC-2815 'Modifiable contents' flag

SVC-3070 New Permission Request "Restrict scripted reading of primstats"

SVC-2623 New permission for textures (For Build Only)

SVC-2622 Add permissions for owner-after-next

SVC-2594 Extended options for setting permissions.

SVC-468 New Permission Request "Resize only"

SVC-1654 Revision of SL's Permission System

SVC-2624 Add "Not for Resale" flag to permissions

SVC-2626 Copyleft/share-alike permission for SL Items

SVC-701 Copyright/license/notes fields on assets, to allow proper attribution and provide license and configuration information.

SVC-407 Creator Access Only Script Permissions Attribute

SVC-1656 Add a new next owner permission: Scriptable

SVC-995 Change of Transfer system (Resell/Transfer -> Resell and Gift)

~~MISC-400~~ Freeware items (restricted transfers)

SVC-3444 Meta-Issue: Transfer of Objects: Permission Issues

MISC-398 Meta-Issue: Meta-Issue Organization

This issue is related to by:

VWR-14648 Suddenly my copy-mod kitchens have turned no copy mod, copy no mod, or no perms. Inside the kitchens are copy no mod items which rez on touch.

VWR-11862 Mod ok texture products need full permission to use.

SVC-3448 Texture asset permissions viral to prims

SVC-4529 Prim items, made from scratch, no scripts, say mod, but aren't modifiable

~~MISC-2376~~ No mod items that contain sounds/scripts/animations will no longer allow the owner to set more restrictive permissions to items in contents

~~VWR-13236~~ strange problem plaguing me with my own created objects---permissions to edit/reposition DENIED

~~VWR-13317~~ cannot change perms on my own objects

~~SVC-4722~~ no transfer textures such as sculpts and pattern textures unuseable by next owner

~~VWR-10197~~ Can't reposition -- permission denied Message when trying to move prims long(er) distances

~~MISC-543~~ loss of transfer rights on self created objects

~~VWR-14667~~ Personally built objects with no mod contents, While in-world the overall object is made mod for the next avatar, animation maintaining no mod of course. When taken into the inventory and given to another avatar the overall object becomes no mod.

~~SVC-3813~~ Selecting "Share with group" fails if "Transfer" is not enabled.

~~SVC-3816~~ SchitzoPermia: Perms different between editing and properties

SVC-3709 We need no-copy AND no-transfer objects

VWR-10525 New Asset policy type - Allow (or not) next owners to change the contents folder of a object

SVC-3748 There is a need for the original owner of an object to be able to remove next owner copy and/or trans perms after putting their object in a third party vendor

VWR-11902 No copy object will not link to a no transfer object

SVC-2619 Review of No Modify behavior w/r/t containers and contents

MISC-2140 Limited Transfer ability

VWR-11678 Add an OK button to all permissions dialogs

MISC-2297 Marking MOST items NON TRANSFER needs to be stopped

VWR-13237 New Texture Perm: transfer on prim only

SVC-4233 Ability to set others objects to group

VWR-11907 Ability to give yourself a Next-Owner permission version of any transferable object.

SVC-3675 Stop treating "no modify" as "no rename".

~~SVC-3800~~ Ability to link no-copy objects to no-transfer objects if user confirms they are ok with it being irreversable.

SVC-3444 Meta-Issue: Transfer of Objects: Permission Issues

Description

« Hide

This is a meta-issue for organizing various issues relating to changing or adding to the permission system. It's not in support of permission change. For that, individual issues should be looked at.

All

Comments

Change History

Sort Order:

There are no comments yet on this issue.