[consulting] Restrict Group Access to one User Login Account

Laura pinglaura at gmail.com
Thu Oct 8 17:37:23 UTC 2009


What happens when a nurse leaves the program and should no longer have  
access? Change the password and tell 1000 people?

Laura

On Oct 8, 2009, at Thu 10/8/09 11:22am, Brian Vuyk wrote:

> I agree - if the accounts aren't meant to be personal, don't hold any
> personal information, then where is the harm, other than it's not a  
> use
> case most Drupal developers don't have in mind?
>
> One of my past clients had ~3000 users worldwide over ~10 departments.
> It was much easier for them to use 10 generic, per-department accounts
> to access various data than manage 3000 separate user accounts.
>
> Brian
>
> Sam Cohen wrote:
>>
>> On Thu, Oct 8, 2009 at 12:18 PM, Eric Goldhagen <eric at openflows.com
>> <mailto:eric at openflows.com>> wrote:
>>
>>
>>    I have to agree with all the folks that think it's a terrible  
>> idea to
>>    share accounts.
>>
>>
>> I don't get it.   Maybe there's something I don't understand. Why is
>> it such  a terrible idea to share accounts?  It seems to me the risk
>> of something happening is next to nothing.  I mean, I'm not  
>> advocating
>> it as a general practice, but I fail to see why it would be such a
>> problem or what types or risks it poses.
>>
>> Sam
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> consulting mailing list
>> consulting at drupal.org
>> http://lists.drupal.org/mailman/listinfo/consulting
>>
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting



More information about the consulting mailing list