Permissions management - what are the rules?
Portion of an email to ________________ within ________________ :
... one thing I can take away from your email is re "permissions", in terms of who should be responsible for what... Background suggestion is that:
-
The notion that head office projects don't, and never have, even when you were all paper-based back in my time as a h/sup, developed and rolled out in isolation from each other
-
This was highlighted in the feedback I got when I did your ________________ training in regions, and married up with my personal experience across all those years in DAS: namely, that out there, head office projects are often referred to as "silos" that should see each tool 'in batch' along with all the others
-
Which is of course the whole premise of EMSOnline, if you track that tool's development back: juxtapose the various tools, so sups can flip from one to the other quickly via a single menu
A corollary to this is permissions, which we think are nearly settled down enough for ________________ to take over. The above guiding principles would suggest that if a supervisor just now let ________________ know that he or she is the supervisor of C1234, and got the cluster manager to verify that, then that person is not going to be impressed if ________________ or ________________ asks them the same question
...
|
Last modified at 25/02/2010 13:41 by Damien Ryan-Green
|
|