Perhaps this depends some on how you set up the groups and permissions
to start with. I never give any specific user access to anything.
Every permission is bound to a group. So that the users permission
just depends on which groups they are part of.
On 3/31/06, Jorge Godoy <[EMAIL PROTECTED]> wrote:
>
> "Elvelind Grandin" <[EMAIL PROTECTED]> writes:
>
> > I have to somewhat agree with Paul. Setting the permissions for the
> > system is the developers jobb not the admins. The admins handles the
> > users and adds them to the correct groups depending on what their
> > permissions should be.
>
> And what about commercial systems? You'll tell your client that he's tied to
> you to a simple task as that of saying who can and who can't access what? I
> mean, he'll have to pay your hourly costs for this task all the time something
> changes? And he'll have to "rethink" if the existing permissions apply always
> when he hires a new employee? (Remember: he'll want to avoid costs with that,
> so security *will be* sub-optimum...)
>
> --
> Jorge Godoy <[EMAIL PROTECTED]>
>
> >
>
--
cheers
elvelind grandin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
