Customer Admin endpoint: LiveRamp and Innovid

[sergi0aranda]

LiveRamp has requested that we make a Customer/Client Admin endpoint available so they can automate adding, editing and deleting users whenever they have personnel changes. @hollinger indicated that we need to create a new role "Customer Admin" or "Client Admin" and then develop an endpoint so customers can make changes to IQMedia UI without requesting them to Kinetiq.

[jmylet]

What kind of edits or changes on users/customers are we looking to enable through the API? I'm assuming things like changing roles, changing passwords, and basic info like their names or emails; would there be anything else that we were thinking of allowing them to edit or conversely something that we definitely do not want them to be able to change? I'm thinking then that most of what we do allow them to modify would also be available or required input when creating a new user, or would there be some difference between the two?

Would we also then need a client modification endpoint as well then? I'm also assuming that we don't want client creation or deletion endpoints since they probably wouldn't be useful to anyone but us.

[sergi0aranda]

Good questions @jmylet. One quick one is that NO, we will not need a client modification endpoint. I was thinking we allow them to perform the basic customer functions: create, delete (isActive=0) and edit basic fields like password, email, login (if possible), phone and isActive. If we want to get fancy and allow them to edit Customer Roles, then this need to be within what is available to the Client... meaning the should not be able to add Timeshift if the Client does not have it.

[sergi0aranda]

Hi @jmylet , just to confirm that the delete or de-provision customer function should not be a "dirty" delete but just setting the isActive field to 0. In case the employee comes back to LiveRamp they want the ability to re-provision/reactivating by setting isActive back to 1.