Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Nathan Jameson
|
Posted - 2010.09.09 04:26:00 -
[1]
Following some helpful advice from another thread, I set up my POS permissions so that up to 14 individuals could use the Corporate Hangar Array and have access to only their items:
* The first group would have the permissions (Query/Take=Yes, Take Container=No) and could see and access all the items in their divisions, but couldn't move or open GSCs in their divisions. * The second group (the "overflow group") would have the permissions (Query/Take Container=Yes, Take=No) and could see all the items in the divisions, but could only move and open their GSC containers.
I double-checked the permissions several times with an alt, and the results worked out. Both groups could see each other's items, but they couldn't move anything but their own items.
A couple hours later, I find out that my corp members were having problems. The second group was no longer able to touch their containers. In fact, whenever they tried to remove them, nothing would happen--no "You do not have permissions" text, nothing. The division lists "Read Only" next to it, and nothing is touchable or moveable for the second group. (Permissions are still fine for the first group.)
My question is: what changed? Why did permissions that work originally suddenly get screwed up? And what options do I need to change to correct the problem?
Looking forward to any helpful tips, Nathan
|
Tau Cabalander
Caldari
|
Posted - 2010.09.09 05:20:00 -
[2]
Edited by: Tau Cabalander on 09/09/2010 05:24:10
It doesn't work the way you hope it does.
You need Take on hangar to take ANY items. You need take on container to take containers, but this doesn't prevent accessing the container contents.
Originally by: Roles and access rights: Access Right Types Hangar Access
A pilot can have either a query right or a take right from a hangar division. Having a take right automatically gives a pilot the query right as well. With a query right a pilot can view anything in that hangar division, but can not take anything or otherwise interact with the items there. With the take right the pilot will have full unrestricted access to that hangar and may take items from there as he pleases except audit log containers (see container take rights below). A pilot with take rights can still open such containers, just not move them to his own hangar. Hangar access rights are divided into Headquarters, Based At and Other.
Container Access
This access right will allow a pilot to remove audit log containers or any other container types from a corporation hangar he has access to. Without this role that pilot will receive an error message when he attempts to do so. Note that the pilot in question will still be able to open the container and access items in it if they have the hangar take access right to that hangar. - Unless of course, the take rights are restricted any further by audit log container configuration settings.
|
Nathan Jameson
|
Posted - 2010.09.09 08:58:00 -
[3]
Well, that sucks. Since unlike station hangars, POS hangars do not permit you to open containers while they are still inside. You actually have to physically take the containers out of the Corporate Hangar Array to interact with them, and having rights to do that means you have rights to take them all.
It looks like there is no good way of doing this past 7 people per POS. Thanks again for the help.
|
Eve Gurl
|
Posted - 2010.09.09 14:18:00 -
[4]
passwords?
|
Tau Cabalander
Caldari
|
Posted - 2010.09.09 15:51:00 -
[5]
Edited by: Tau Cabalander on 09/09/2010 15:51:26
Of course you can always anchor GSC and password them for private storage. Requires Anchoring 1.
I think containers within control range of a POS never get garbage collected, otherwise they have to be accessed every 30 days.
Make sure to set the password after anchoring, not before.
|
Nathan Jameson
|
Posted - 2010.09.10 15:47:00 -
[6]
Originally by: Tau Cabalander Edited by: Tau Cabalander on 09/09/2010 16:05:09
Of course you can always anchor GSC and password them for private storage. Requires Anchoring 1.
I think containers within control range of a POS never get garbage collected, otherwise they have to be accessed every 30 days.
Make sure to set the password after anchoring, not before.
Yeah, that's what I'm doing now. Inconvenient, but the only real option left. Thanks just the same.
|
Celgar Thurn
Minmatar Uttindar Union for Minmatarian Affairs
|
Posted - 2010.09.10 20:20:00 -
[7]
When you say 'within control range of a POS' do you mean just inside the forcefield of the POS or outside the forcefield as well?
|
Tau Cabalander
Caldari
|
Posted - 2010.09.10 21:00:00 -
[8]
Originally by: Celgar Thurn When you say 'within control range of a POS' do you mean just inside the forcefield of the POS or outside the forcefield as well?
If I recall, you can't anchor a container inside the bubble.
Show info on the control tower, and look at the attributes for Maximum Structure Distance. Anchr stuff inside that range. I recommend not riding the limit (subtract 5 km), as I've had personal experience with structures anchored at the limit becoming detached the control tower.
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |