Must be Group Owner to add/delete members via LAPI? Not just a Group Administrator?

Ivan Filippenko

The title pretty much asks the question.

I'm trying to add and delete members to/from a group using the LAPI calls LAPI_USERS.AddUserToGroup() and LAPI_USERS.DeleteUserFromGroup, respectively.  Although I'm a Group Administrator, these calls return errors (codes 400201 and 400801, respectively).  If I set myself as the Group Owner, then the calls work.

Oddly, I'm able manually to add/delete members even when simply a Group Admin -- no need to be Owner in the manual case.

Must I really be the Group Owner in order programmatically to add/delete members?  This throws a monkey wrench in the works, as I need to perform this admin function even on groups I don't own (but administrate).

Please help!  Thanks!

Appu_Nair1

In livelink core business rules are like this so I think LAPI would obey it

You 123456 creates a user John Doe(56789) so you are owner.You can delete/change this is basically the login priv 'Can Create Modify User'

You 123456 creates a group TimpityTee(56789089) so you are owner.You can delete/change group this is basically the login priv 'Can Create Modify Group'

the above two privs will work only on Groups/User you own or I think it is flexible on the Group Leader.Until I played with code on the permutation/combinations of GL I would not be able to say what livelink is looking for so what I am hearing you say is the webgui is behaving one way and lapi is another way.Unfortunately I do not have the time to check that .Perhaps OT lapi experts could come to your rescue. I would use the next approach

If you need un impeded access for changing users/groups in your system your login should have the priv  'User Administrator'.That trumps the other two settings so if your lapi user has that you should be fine.

Note what I am talking is not an object's ACL these are privileges for the login id it ranges from LOGIN,PA,CCMU,CCMG,UA & SA.