Wormholes

CCP are looking at working on corp roles. So I'd like to get some input and feedback from everyone in w space.

We all know at the moment there bad. What i'd like is stuff you think could be improved on and how. ideas on what you think should be there thats not.

Couple examples.

When changing standing you have the option to click a box and that will let the people you are altering standing with know its been altered (ceo director diplo)

letting directors know when some one has left not just the ceo.

All the good stuff I will take from here and put on conflunce so ccp can see it much much eaiser.

To simplify, I would love to see a far more granular access assignment. Let me as CEO create roles, then simply apply check access boxes at the lowest levels for each possible task. Obviously have some canned roles in there if people want to use them. This may take a while to set up but in the end, by un-linking all the various access levels and allowing them to be independently selected, each CEO can create the exact role and access levels they want.

It would be great to see individual members added into the access levels for each POS module as well, particularly SMA/CHA. It would be a huge benefit to set it such that the POS owners could be set, and then the access levels only applied to them. I.E. 3 members can manage their own POS fuel and anchoring/unanchoring, but not for every other POS in the corp.

In a nutshell, allow access levels to be defined at the lowest possible level so no undesired linking takes place.

access to pos mods should have an allow list option, like chat channels, where you can set exactly who has what access.

I had to deal with POSes for years now and I am very happy that CCP is finally looking into roles which will have a huge impact on people living out of a POS.

Tooltips for roles would be nice.
Something like "Diplomats can set corporation standings" or "Starbase Fuel Techincians can put fuel in but cant take it out".

Roles should only enable to do one thing and one thing only
For instance, if you want someone to be able to create medals you also have to grant him the ability to invite new members to corp also he needs access to a wallet. This is bad.

Organizing Access Levels
My main concern with roles in w-space is that they offer way too limited options for the organization of access to structures. Tabs in hangars help with that but for SMAs only four access layers (ally, corp, starbase fuel technician, config starbase equipment) are useable. In reality - people in eve think that being a **** is cool - only 2 are useable on a corporation level.

Suggestions:
1. We need "access roles" to organize access levels for individual POSes, structures, tabs, etc.
It would be cool if you could grant a member the roles so he could do stuff in POS a but could not mess with all the other POSes. Also you should not have to enter the force field passwords if you have the right access role for that POS.

How could this work:
CeOs creates a bunch of access role names -> CeO sets POS or POS structure or TAB in a hanger to be only accessible/useable if member has that access role. If a POS requires access role a and a structure within access role b a member would need both access roles to access/use that structure.

2. Tabs for SMAs would be cool.
Tabs are a great way to organize stuff. While you are at it introduce large SMAs (similar volume as 3 regular SMAs), since we would not need 3 SMAs per POS if we had a proper way to organize access levels.

3. Add roles for organizing access... and only that!
see 1

It also bugs me that there is no log of who takes and puts stuff in.

Remove the necessity to have access to a corp wallet for most activities
Should work like if you buy stuff in a station. If you have access to a wallet you have the option to use it and if not you have to use your personal wallet for that.

My vote would be to just add the titles to the corp access dropdown. Currently you only have the option of Starbase Fuel tech and Starbase config. If you can add all the titles to that list it would be awesome.

The ideas of access control to a POS via title is neccessary.

Also, would be good if all of this stuff stuck, and there was a log of all changes to structure access permissions. I am sick of checking and re-checking and triple-checking and then discovering access permissions have been changed.

I also think that the industry access via corp roles and titles is....well, i can't even figure this crap out, and hence the majority of peons in the corp cannot do industry and don't do industry.

i also agree that roles can be a bit too broad. In W-space, for instance, you need Communications officer role to survive, because you need to be able to blitz 250 wormhole bookmarks and clear room for the next rageroll. So everyone has to have this role. But this allows people to spam corp and alliance mails, delete bulletins, etc.

The basic problem is that roles etc. were created before anyone even knew what people wanted or needed in a corporate system in w-space. This requires a root and branch rethink, with the whole system burned to the ground and rethough from the ground up....in tandem with POSs, because as said above, any redo of the corp roles system needs to work with the POS system.

The current system is set up to fail, and it regularly does fail, and when CCP eventually caves in and allows allliance bookmarks we will see the mega WH corps blow up into 300 one-man corps all in the same Alliance, sharing Alliance bookmarks and living in their own secure one-man corp POSs because this is the most secure method of doing it, and right now you can only synthesise it to some degree via personal POSs.

So, thought needs to be started with "What do you need to do as a CEO? What roles do corporations need to do in order to function?"

1) First and foremost, i think, the access at HQ, Based At and Other are unneccessary complications which can be reversed into (as above) access being handled on the domain-level (ie; per structure) via allowing the activity to each title class. eg, you do not need to set the Based At attribute for a character (eg, to a branch office in Heimatar) if you can then just click on he list of corporate offices or POSs and set the access to a title class directly.

Right now you have to keep a matrix of who is allowed to access what. And the access based at and access (other) are the most important, so it's in effect a three dimensional matrix. With give/take and view roles for hangar slots AND THEN FOR MOFUQIN CANS inside said hangars.

So, to conclude, simplify this.

2) Remove the container access restriction level. The number of times people get hung up on having chucked a can into an array and been unable to access the contents and I have to fly over, changing passwords to enter the field, find their bloody can and empty it or eject it or store it back in their stupid ship and remind them about the no containers in containers rule. OMG. Give me my game time back. Like, seriously, if anyone is stupid enough to store corp BPO's in cans inside an array, let them get their crap stolen as dumb tax. Doesn't matter if you have 3,000 BPCs you can use the search function, so cans are a redundancy anyway.

3) Config equipment role. At least rename this to Anchor Bubbles role, because there's literally no other use for this role. Also some corps may not even care about corp bubbles being nicked by adventurously cavalier members, so maybe this whole role can be an opt-in. Maybe a tickybox in the roles screen "Do you want to restrict anchoring in your corp? Y/N? If Y, pick a title to grant it."

(reserved for more ranting, later)

I think a POS (and all pos access rights) should belong to an individual, not a corp. And that individual can give rights (like shield access and access to the fuel bay) as they like, including to their corp and alliance.

Similarly, all modules floating in space should belong to an individual (not to a corp or pos), and that individual can set the access rights. If the module (like a SMA, for example) is placed by the individual on grid with his pos, then it's default access rights should mirror the pos's, but they are adjustable independently.

This should sort out the problem with Starbase Config roles.

Also, Industry (esp reactions) should not be tied to the tower, but instead to the reactor module. Access rights to the reactor module (and any processes therein) should be controlled by the individual who placed it.

Finally, all modules not protected by a shield (including dead sticks) should be able to be offlined, unanchored, and stolen by anyone. This should occur with an appropriate eve-mail to the owner and an appropriately significant unanchoring time (which could be several hours, and could be much shorter for the owner). Perhaps we can add a new 'module hacking' skill to allow non-owners to do this. This could introduce a problem of blues 'stealing' the guns outside the shield, but that can be fixed by making them 'grey' when they start this process and then having to deal with the pos defenses.

We do not use roles but titles (bundles of roles) exclusively. I never worked with "grantable roles" feature and am not sure if this actually is useful but "grantable titles" would defiantly be an interesting feature for me.

SMA tabs w/ grantable access by title. Give an SMA 15 tabs, so we can assign one tab to Billy, one to Stephon, one to Sally and so on. We can also assign a tab as Corp rolling ships and grant that to all 3.

When you access the SMA and you happen to be Billy, you can see your Billy tab and the Corp roller tab. If you don't have rolls to do Sally then you can't see her goodies.




POS access by director assignment. (get rid of the whole manual PW garbage). Directors can assign who has access to which POS by title.

Just a table of the POS that you have anchored across the top and the list of members down the left hand side. Let the directors check off who has access to which POS and be done with it on the corp member level. Still provide the PW funcionality for non corp members. Having POS access grantable by title would be sweet for bigger groups (refueling lackey title would allow your refueling lackey access to all POS, but once in a POS only allows fuel to be put into the fuel bay)



General update of grantable roles.

Fuel Lacky - can access any POS, but allows ONLY adding fuel and nothing else.
Refiner Dude - Can online and offline ore cruncher thingers, fill them, use them, empty them
Research Dude - can use a research facility
Bob the builder - can use the various arrays that make things
Reactor Rick - can use the various reactors/silos and what not to make moon goo or gas stuffs into other stuffs.

It would be a productive round table to talk with various groups to get your arms around how POS are being used differently and what the best actual roles to have are. I can think of several user groups that use POS in distinctly different ways.

WH guys, HS indy towers, reaction towers, staging towers, LS/null indy towers.

Specifically with roles, the ui itself needs to be updated. Spreadsheet formats don't work as they are too large, too long, etc.

Convert the roles ui to a drag and drop system. Drag a role, drop it on the person, done.
To clarify, in corporations, roles are setup using a graphical top down tree. It's the boss, then supervisors below them, then peons, Etc.

Put that top down graphical list in the game (basically Visio for eve). You assign roles to the circle, drag the person to the circle, done.