On 2018-01-26 11:02, Luciano Rossi wrote:
> Hi Cédric,
> 
> El 25/01/18 a las 12:36, Cédric Krier escribió:
> > On 2018-01-25 11:24, Luciano Rossi wrote:
> >> Hi!
> >>
> >> I need to create an interface to manage the users. For now, I add to my
> >> module the menu item Administration -> Users.
> >>
> >> The problem that i'm having, is that I want to restrict the groups that
> >> the user can add or remove from the groups field (many2many).
> >>
> >> I added a restriction to the groups field, modifying the definition of
> >> the domain attribute of the groups field, so when choosing the groups to
> >> be added, it will restrict the list of them. But, I don't know how I can
> >> restrict the lines (groups) that the user can remove.
> >>
> >> For example, the user can add to the user the groups Accounts and
> >> Purchase. But, if the user already has the group Sale, I do not want
> >> that this group to be remove it.
> >>
> >> Any idea?
> >
> > For me, this is strange. If a user can add some groups to its profile, I
> > do not see why not add all the allowed to the user by default so he does
> > not need to edit himself this sensitive field. I see no reason a user
> > will want to remove himself from some groups and thus restrict himself
> > his access rights..
> 
> Well, I think it's not strange if the idea is to sell Tryton as SAAS. 
> Probably you will want to give to the customer the possibility to create 
> or modify users, but for example, you will not want him to access to the 
> Administration group (if the customer grant access to that, it could 
> activate modules).

It is still strange for me even on SaaS.
I do not see any problem to allow user to *activate* modules as far as you
control the modules that are *installed*.

-- 
Cédric Krier - B2CK SPRL
Email/Jabber: [email protected]
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

-- 
You received this message because you are subscribed to the Google Groups 
"tryton" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton/20180126150617.GS23162%40kei.

Reply via email to