Use Case

I want all users within an organization or group to be able to access apps installed for that organization.

Example

The XYZ company is one of our customers and they have three different users (Jon, Cindy and Mike) each with their own user accounts. John purchases an app called “My XYZ App” and Cindy also needs access to use that app so instead of having to log in with Jon’s account, Cindy can log in with her account and use the app as if it was her own.

Implementation Strategy

In order to identify a group of users that should be able to have shared access to one another’s apps simply provide the same groupId value for each of those users using the Create/Update User API method.

For Example, the XYZ company is identified internally by your system as having a static, un-reusable organization Id of “4556841222”. In this case, when user accounts are created in your system, call the Create/Update User API method to create the new user and set the groupId to “4556841222”.

 Normally, you don’t have to explicitly create a user in OpenChannel and a user will get created automatically when an action is first performed using their userId.

It’s important to choose groupId’s wisely. For security reasons, never reuse or hash groupIds. Providing unique and properly managed groupIds is important for keeping users from unintentionally gaining access to another user’s apps.

Users with the same groupId share the full ownership license for installed apps. If you are looking to implement role based controls where only certain users can perform actions then blocking actions (like the ability to install/uninstall an app) will have to be made on your server side before calling our API.