Constituent API and user security groups

Kristin Neimi-Gillig

We've got a question around a client's production application that's using the Constituent Management API. We have been using the server API to update constituent records and move them between groups which had been working fine. However, one of the groups has been changed to be a user security group so that it could be used to secure content which should be available to members of that particular group. It now appears that the API will not add users to that particular group, although it will still add/remove users from the standard non user-security groups. Looking at the API docs it says that it would be a problem if it was an admin security group but doesn't mention user security groups.

Can you give us some advice?

Thank you very much!

Alan Gallauresi

David Hart

I'm 90% sure that I know what the problem is. It looks like we may have forgotten to assign a permission to the Constituent Management API role that is necessary to manipulate security groups. I will need to verify that this is the problem, and if it is we should be able to get you a fix pretty quickly.