Thank you for the inspiring conversation. Am Dienstag, 28. März 2017 14:31:33 UTC+2 schrieb Melvyn Sopacua: > > > > > From an object perspective, you need to send the invoice to the group > "Approvers". Again, best solved at the group level. > > And it's questionable if superusers should be in there. They are the > equivalent of the Posix 'root' user, which has the power to lock/unlock > everything in and about the system. Data privilege and system privilege are > always in fight and in this case it's questionable if superusers should > automatically be Approvers and while they still could do it, the UI > shouldn't present them. > >
My favorite search engine did not reveal much to the topic "Data privilege vs system privilege". Do you have any further readings about this topic? > > > As said, a good group structure solves a lot of your problems - > > > Yes, groups exist as container/list data type for users. On the other hand just because groups exist, I think there are other ways to specify a list of users. Example: All people with a particular OCEAN Vector <https://en.wikipedia.org/wiki/Big_Five_personality_traits> > in fact you wouldn't need a user selection to begin with, as the mail can simply be sent to all members of the Approvers group. A mail to everyone is like a mail to no one (not always, but often). Again .... system vs data privs ... sounds interesting. Regards, Thomas Güttler -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/12b2c209-3e24-4cc9-b7e2-40df744d92c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
