
| Key: |
VWR-776
|
| Type: |
Meta Issue
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
yukiko omegamu
|
| Votes: |
31
|
| Watchers: |
6
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Relates
|
|
This issue Relates to:
|
|
|
SVC-79 Estate owners/managers should be able to enter their "full" sims
|
|
|
|
 |
|
|
|
 |
|
SVC-456 Meta-Issue: Improved Anti-Griefer Tools
|
|
|
|
|
|
SVC-541 Meta-Issue : Estate Improvements
|
|
|
|
|
|
This issue is related to by:
|
|
|
VWR-9562 Add "Region Managers" to Region/Estate menu, to allow single region management
|
|
|
|
|
|
|
Estate owners should be able to assign their managers any combination of the following permissions :
Parcels
- Immunity to parcel ejects, bans, and access lines of all types, also, cannot be teleported home (NEW)
- Ability to reclaim land back into the hands of the estate owner
- Ability to set land owned by the estate owner as for sale, including sale details
- Ability to modify about land -> ban -> deny by payment status for all parcels
- Ability to modify about land -> options settings for all parcels
- Ability to modify about land -> objects settings for all parcels (e.g. auto-return)
- Ability to return objects on land (including "all objects owned by avatar X"!)
- Ability to terraform anywhere
- Ability to terraform whilst ignoring the "terraform limit" on the sim. (NEW)
Estate / Region
- Ability to send a message to the region
- Ability to restart the region
- Ability to change agent limit / object bonus / maturity
- Ability to change other sim-wide overrides, like "no push" and "no pay info on file"
- Ability to change telehubs
- Ability to teleport home one user
- Ablity to teleport home all users
Estate / Debug
- Ability to disable physics/collisions/scripts sim-wide
- Ability to return/delete all of avatar X's objects on the sim
- Ability to use get top colliders/scripts panels
Estate / Ground Textures
- Ability to modify ground textures
- Ability to modify texture blend values
Estate / Terrain
- Ability to upload terrain files
- Ability to download terrain files
- Ability to bake terrain
- Ability to change sea level
- Ability to change terraform limits
- Ability to alter sun settings
Estate / Estate
- Ability for modify the permissions of other EMs (excluding themselves) (NEW)
- Ability to modify the estate ban list
- Ability to modify the estate access list
- Ability to change estate time
- Ability to change estate public access setting
- Ability to change estate direct teleport setting
- Ability to change estate payinfo setting
- Ability to kick a user from the estate (if enabled, right clicking adds a "TP Home" option to the pie menu, which when used sends the target home and pops up an "add to estate ban list?" prompt - NEW)
- Ability to send a message to the estate
If we had the above permissions system, then we could appoint more estate managers to help us run sims, resulting in a better user experience for Second Life residents.
Currently, giving someone estate manager status pretty much gives them the keys to the castle. Under a system like this, we could give them only the permissions they need to do their jobs.
This would result in more effective governance of sims, as estate owners would be more likely to appoint more estate managers, and those estate managers would be more focussed on jobs they were appointed to do.
It would also close quite a few security holes - estate managers as they are now can wreak havoc on a sim if their account is compromised or if they simply go nuts one day. Under this permissions system, that would be far less likely. Under the permissions system things would be a lot more convenient for the sim owners, as well as a lot safer.
|
|
Description
|
Estate owners should be able to assign their managers any combination of the following permissions :
Parcels
- Immunity to parcel ejects, bans, and access lines of all types, also, cannot be teleported home (NEW)
- Ability to reclaim land back into the hands of the estate owner
- Ability to set land owned by the estate owner as for sale, including sale details
- Ability to modify about land -> ban -> deny by payment status for all parcels
- Ability to modify about land -> options settings for all parcels
- Ability to modify about land -> objects settings for all parcels (e.g. auto-return)
- Ability to return objects on land (including "all objects owned by avatar X"!)
- Ability to terraform anywhere
- Ability to terraform whilst ignoring the "terraform limit" on the sim. (NEW)
Estate / Region
- Ability to send a message to the region
- Ability to restart the region
- Ability to change agent limit / object bonus / maturity
- Ability to change other sim-wide overrides, like "no push" and "no pay info on file"
- Ability to change telehubs
- Ability to teleport home one user
- Ablity to teleport home all users
Estate / Debug
- Ability to disable physics/collisions/scripts sim-wide
- Ability to return/delete all of avatar X's objects on the sim
- Ability to use get top colliders/scripts panels
Estate / Ground Textures
- Ability to modify ground textures
- Ability to modify texture blend values
Estate / Terrain
- Ability to upload terrain files
- Ability to download terrain files
- Ability to bake terrain
- Ability to change sea level
- Ability to change terraform limits
- Ability to alter sun settings
Estate / Estate
- Ability for modify the permissions of other EMs (excluding themselves) (NEW)
- Ability to modify the estate ban list
- Ability to modify the estate access list
- Ability to change estate time
- Ability to change estate public access setting
- Ability to change estate direct teleport setting
- Ability to change estate payinfo setting
- Ability to kick a user from the estate (if enabled, right clicking adds a "TP Home" option to the pie menu, which when used sends the target home and pops up an "add to estate ban list?" prompt - NEW)
- Ability to send a message to the estate
If we had the above permissions system, then we could appoint more estate managers to help us run sims, resulting in a better user experience for Second Life residents.
Currently, giving someone estate manager status pretty much gives them the keys to the castle. Under a system like this, we could give them only the permissions they need to do their jobs.
This would result in more effective governance of sims, as estate owners would be more likely to appoint more estate managers, and those estate managers would be more focussed on jobs they were appointed to do.
It would also close quite a few security holes - estate managers as they are now can wreak havoc on a sim if their account is compromised or if they simply go nuts one day. Under this permissions system, that would be far less likely. Under the permissions system things would be a lot more convenient for the sim owners, as well as a lot safer. |
Show » |
made changes - 19/May/07 10:37 AM
| Field |
Original Value |
New Value |
|
Priority
|
Critical
[ 2
]
|
Normal
[ 4
]
|
made changes - 22/Jul/07 06:03 PM
|
Description
|
this is probly one over due feature that would greatly improve the estate managment tools for estate managers
1. ability to have estate owners choose the premission levels of the mangers they choose
2. ability to reclaim land if sim owner is gone for long period of time if persons teir is over due]
3. ability to set the premissions and access to closed of f sim land
4. ability to set group access and access list
5. an estate manager control panel simalar to estate/region with less options
6. ability to return prims on land not owned
7.ability to eject freeze and teleport home user on pie menu for estate managers and owners
8. ability to leave estate powers if needed too without sim owner kicking person out of it with email and im stateing he or she leaveing the admin group and powers
9. better tools for estate owners and managers needed
|
There needs to be a flexible system of permissions for estate managers.
Estate owners should be able to assign their managers any combination of permissions, including the following new ones :
1) Ability for modify the permissions of other EMs
2) Ability to reclaim land
3) Ability to modify access list and ban list settings for land
4) Ability to modify all land settings
5) Ability to change sim settings
6) Access to the region/estate control panel
7) Ability to freeze/eject/TPhome people anywhere on the sim
8) Ability to resign from EM status
9) Ability to modify the estate ban list.
In general, better tools are needed for Estate owners and managers.
There are MANY instances where you want to give people permission to, for example, modify the estate ban list, without allowing them to terraform anywhere, change sim settings, etc.
The above would be a good start to a flexible permissions system for estate managers.
|
|
Priority
|
Normal
[ 4
]
|
Major
[ 3
]
|
made changes - 22/Jul/07 06:50 PM
|
Link
|
|
This issue is related to by SVC-301
[ SVC-301
]
|
made changes - 22/Jul/07 07:20 PM
|
Link
|
This issue is related to by SVC-301
[ SVC-301
]
|
|
made changes - 22/Jul/07 07:28 PM
|
Link
|
|
This issue is related to by SVC-241
[ SVC-241
]
|
made changes - 22/Jul/07 10:11 PM
|
Summary
|
estate manager premission levels for private islands
|
flexible custom permissions for estate managers
|
|
Description
|
There needs to be a flexible system of permissions for estate managers.
Estate owners should be able to assign their managers any combination of permissions, including the following new ones :
1) Ability for modify the permissions of other EMs
2) Ability to reclaim land
3) Ability to modify access list and ban list settings for land
4) Ability to modify all land settings
5) Ability to change sim settings
6) Access to the region/estate control panel
7) Ability to freeze/eject/TPhome people anywhere on the sim
8) Ability to resign from EM status
9) Ability to modify the estate ban list.
In general, better tools are needed for Estate owners and managers.
There are MANY instances where you want to give people permission to, for example, modify the estate ban list, without allowing them to terraform anywhere, change sim settings, etc.
The above would be a good start to a flexible permissions system for estate managers.
|
Estate owners should be able to assign their managers any combination of the following permissions :
Parcels
* Immunity to parcel ejects, bans, and access lines of all types, also, cannot be teleported home (NEW)
* Ability to reclaim land back into the hands of the estate owner
* Ability to set land owned by the estate owner as for sale, including sale details
* Ability to modify about land -> ban -> deny by payment status for all parcels
* Ability to modify about land -> options settings for all parcels
* Ability to modify about land -> objects settings for all parcels (e.g. auto-return)
* Ability to return objects on land (including "all objects owned by avatar X"!)
* Ability to terraform anywhere
* Ability to terraform whilst ignoring the "terraform limit" on the sim. (NEW)
Estate / Region
* Ability to send a message to the region
* Ability to restart the region
* Ability to change agent limit / object bonus / maturity
* Ability to change other sim-wide overrides, like "no push" and "no pay info on file"
* Ability to change telehubs
* Ability to teleport home one user
* Ablity to teleport home all users
Estate / Debug
* Ability to disable physics/collisions/scripts sim-wide
* Ability to return/delete all of avatar X's objects on the sim
* Ability to use get top colliders/scripts panels
Estate / Ground Textures
* Ability to modify ground textures
* Ability to modify texture blend values
Estate / Terrain
* Ability to upload terrain files
* Ability to download terrain files
* Ability to bake terrain
* Ability to change sea level
* Ability to change terraform limits
* Ability to alter sun settings
Estate / Estate
* Ability for modify the permissions of other EMs (excluding themselves) (NEW)
* Ability to modify the estate ban list
* Ability to modify the estate access list
* Ability to change estate time
* Ability to change estate public access setting
* Ability to change estate direct teleport setting
* Ability to change estate payinfo setting
* Ability to kick a user from the estate (if enabled, right clicking adds a "TP Home" option to the pie menu, which when used sends the target home and pops up an "add to estate ban list?" prompt - NEW)
* Ability to send a message to the estate
If we had the above permissions system, then we could appoint more estate managers to help us run sims, resulting in a better user experience for Second Life residents.
Currently, giving someone estate manager status pretty much gives them the keys to the castle. Under a system like this, we could give them only the permissions they need to do their jobs.
This would result in more effective governance of sims, as estate owners would be more likely to appoint more estate managers, and those estate managers would be more focussed on jobs they were appointed to do.
It would also close quite a few security holes - estate managers as they are now can wreak havoc on a sim if their account is compromised or if they simply go nuts one day. Under this permissions system, that would be far less likely. Under the permissions system things would be a lot more convenient for the sim owners, as well as a lot safer.
|
made changes - 23/Jul/07 03:32 PM
|
Link
|
|
This issue is related to by SVC-456
[ SVC-456
]
|
made changes - 23/Jul/07 03:32 PM
|
Link
|
This issue is related to by SVC-241
[ SVC-241
]
|
|
made changes - 30/Aug/07 09:53 PM
|
Link
|
|
This issue is duplicated by MISC-186
[ MISC-186
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to MISC-468
[ MISC-468
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to SVC-243
[ SVC-243
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to WEB-136
[ WEB-136
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to MISC-313
[ MISC-313
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to MISC-136
[ MISC-136
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to SVC-508
[ SVC-508
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to SVC-541
[ SVC-541
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to SVC-217
[ SVC-217
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to VWR-1649
[ VWR-1649
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to SVC-456
[ SVC-456
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to SVC-452
[ SVC-452
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to VWR-1750
[ VWR-1750
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to VWR-1363
[ VWR-1363
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to VWR-2075
[ VWR-2075
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to SVC-451
[ SVC-451
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to SVC-79
[ SVC-79
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to VWR-538
[ VWR-538
]
|
made changes - 30/Aug/07 10:08 PM
|
Link
|
|
This issue Relates to VWR-1643
[ VWR-1643
]
|
made changes - 10/Nov/07 02:53 PM
|
Link
|
This issue is duplicated by MISC-186
[ MISC-186
]
|
|
made changes - 22/Dec/07 01:12 AM
|
Workflow
|
jira
[ 11537
]
|
jira-2007-12-21
[ 21248
]
|
made changes - 22/Dec/07 01:33 AM
|
Workflow
|
jira
[ 21248
]
|
jira-2007-12-21
[ 22464
]
|
made changes - 22/Dec/07 02:54 PM
|
Workflow
|
jira-2007-12-21
[ 22464
]
|
jira-2007-12-22
[ 30207
]
|
made changes - 22/Dec/07 03:14 PM
|
Workflow
|
jira-2007-12-21
[ 30207
]
|
jira-2007-12-22
[ 31467
]
|
made changes - 22/Dec/07 07:58 PM
|
Workflow
|
jira-2007-12-22
[ 31467
]
|
jira-2007-12-22a
[ 37102
]
|
made changes - 22/Dec/07 08:16 PM
|
Workflow
|
jira-2007-12-22
[ 37102
]
|
jira-2007-12-22a
[ 38055
]
|
made changes - 22/Dec/07 09:13 PM
|
Workflow
|
jira-2007-12-22
[ 38055
]
|
jira-2007-12-22a
[ 41014
]
|
made changes - 22/Dec/07 09:31 PM
|
Workflow
|
jira-2007-12-22
[ 41014
]
|
jira-2007-12-22a
[ 41921
]
|
made changes - 20/Mar/08 10:13 AM
|
Affects Version/s
|
|
1.19.0.5
[ 10260
]
|
made changes - 20/Mar/08 10:15 AM
|
Link
|
This issue Relates to SVC-217
[ SVC-217
]
|
|
made changes - 20/Mar/08 10:15 AM
|
Link
|
This issue Relates to MISC-313
[ MISC-313
]
|
|
made changes - 20/Mar/08 10:15 AM
|
Link
|
This issue Relates to VWR-2075
[ VWR-2075
]
|
|
made changes - 20/Mar/08 10:15 AM
|
Link
|
This issue Relates to VWR-1643
[ VWR-1643
]
|
|
made changes - 20/Mar/08 10:16 AM
|
Link
|
This issue Relates to WEB-136
[ WEB-136
]
|
|
made changes - 20/Mar/08 10:16 AM
|
Link
|
This issue Relates to MISC-468
[ MISC-468
]
|
|
made changes - 20/Mar/08 10:16 AM
|
Link
|
This issue Relates to VWR-1363
[ VWR-1363
]
|
|
made changes - 20/Mar/08 10:16 AM
|
Link
|
This issue Relates to VWR-538
[ VWR-538
]
|
|
made changes - 20/Mar/08 10:16 AM
|
Link
|
This issue Relates to SVC-508
[ SVC-508
]
|
|
made changes - 20/Mar/08 10:16 AM
|
Link
|
This issue Relates to SVC-243
[ SVC-243
]
|
|
made changes - 20/Mar/08 10:16 AM
|
Link
|
This issue Relates to VWR-1750
[ VWR-1750
]
|
|
made changes - 20/Mar/08 10:17 AM
|
Link
|
This issue Relates to MISC-136
[ MISC-136
]
|
|
made changes - 20/Mar/08 10:17 AM
|
Link
|
This issue Relates to SVC-451
[ SVC-451
]
|
|
made changes - 20/Mar/08 10:17 AM
|
Link
|
This issue Relates to SVC-452
[ SVC-452
]
|
|
made changes - 20/Mar/08 10:17 AM
|
Link
|
This issue is related to by SVC-456
[ SVC-456
]
|
|
made changes - 29/Aug/08 04:51 PM
|
Issue Type
|
New Feature
[ 2
]
|
Meta Issue
[ 6
]
|
|
Affects Version/s
|
|
1.19.1.4
[ 10290
]
|
|
Affects Version/s
|
|
1.20
[ 10350
]
|
|
Affects Version/s
|
|
1.21 Public Nightly
[ 10352
]
|
|
Affects Version/s
|
|
Source code
[ 10012
]
|
|
Affects Version/s
|
|
1.21 Release Candidate
[ 10360
]
|
made changes - 05/Oct/08 11:29 AM
|
Link
|
|
This issue is related to by VWR-9562
[ VWR-9562
]
|
made changes - 13/Nov/08 10:59 AM
|
Workflow
|
jira-2007-12-22a
[ 41921
]
|
jira-2008-11-14
[ 61769
]
|
made changes - 13/Nov/08 11:15 AM
|
Workflow
|
jira-2007-12-22a
[ 61769
]
|
jira-2008-11-14
[ 66802
]
|
made changes - 13/Nov/08 04:29 PM
|
Workflow
|
jira-2008-11-14
[ 66802
]
|
jira-2008-11-14a
[ 86731
]
|
made changes - 13/Nov/08 04:39 PM
|
Workflow
|
jira-2008-11-14
[ 86731
]
|
jira-2008-11-14a
[ 89917
]
|
made changes - 13/Nov/08 04:50 PM
|
Workflow
|
jira-2008-11-14
[ 89917
]
|
jira-2008-11-14a
[ 93484
]
|
made changes - 13/Nov/08 05:03 PM
|
Workflow
|
jira-2008-11-14
[ 93484
]
|
jira-2008-11-14a
[ 98173
]
|
made changes - 13/Nov/08 05:20 PM
|
Workflow
|
jira-2008-11-14
[ 98173
]
|
jira-2008-11-14a
[ 104585
]
|
made changes - 13/Nov/08 05:36 PM
|
Workflow
|
jira-2008-11-14
[ 104585
]
|
jira-2008-11-14a
[ 110629
]
|
made changes - 13/Nov/08 05:51 PM
|
Workflow
|
jira-2008-11-14
[ 110629
]
|
jira-2008-11-14a
[ 115538
]
|
made changes - 13/Nov/08 06:10 PM
|
Workflow
|
jira-2008-11-14
[ 115538
]
|
jira-2008-11-14a
[ 122869
]
|
made changes - 13/Nov/08 06:26 PM
|
Workflow
|
jira-2008-11-14
[ 122869
]
|
jira-2008-11-14a
[ 128743
]
|
|