SeAT - forum: Default director privileges - Page 1

Hi everyone, As we continue to evaluate SeAT for our group’s needs, we ran into something we found really counter-intuitive and that we didn’t expect from the documentation. Apparently Directors of a corp get full access to see everything in the corp member’s mail, skills, wallets, etc. This seems to contradict the way the documentation describes default permissions: ‘In SeAT, the default rule is to deny access. As a result, someone without a permission will not be able to access the requested resource.’ [1] We were convinced the behaviour meant that we had accidentally done something to clobber the permissions during setup, so we actually reinstalled twice before finally realising that this seems to be intended behaviour, though to the best of our knowledge not documented. Though we may well have missed something somewhere of course. The only place we found reference to this is in a GitHub issue [2], which never got resolved and is still open. I didn’t want to just necrobump that issue without a discussion to see if I’m missing something somewhere. Is there a toggle to turn this off? It seems like it’s a one-line code change but it would be helpful if there could be a setting switch for this. Does one exist or could it be added please? I’m new but it also seems to me that this is what Squads are intended to be used for, if a more systematic approach was desired. For context, we do not want this level of permissions going to all our Directors by default, though I recognise the norms in others groups is different. Thanks! [1] https://eveseat.github.io/docs/admin_guides/authorizations/ [2] https://github.com/eveseat/seat/issues/786

I do believe currently the model is that if you are a director in-game, you get access to everything related to that corp including the ability to inspect characters within the corp including mails

the work around is to specifically remove raw "director" in-game, make a title "director" and give it all roles in-game except the actual "director" role

effectively that gives you the same in-game perms without having seat default allow access

Thanks. I don’t want to start messing around with in-game roles just to work around a SeAT issue though, tbh…

To my knowledge, this behavior cannot be disabled. However, I'd support adding a toggle. I agree that adding a toggle probably wouldn't be too complicated. Feel free to open a pull request on github and I'll review it.

Great that you're open to adding this! Thanks. I am not sure I know how to implement such a change, so I'd be open to anyone who wants to help. Otherwise I can try to figure it out