Use Case

I want all developers within an organization or group to be able to access and manage apps created by any user within that organization.

Example

The XYZ company is one of our partners and they have three different developers (Jon, Cindy and Mike) each with their own user accounts. John creates an app called “My XYZ App” and Cindy needs to make a change so instead of having to log in with Jon’s account, Cindy can log in with her account and make the change to Jon’s app.

Implementation Strategy

In order to identify a group of developers that should be able to have shared access to one another’s apps simply provide the same groupId value for each of those developers using the Create/Update Developer 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 developers accounts are created in your system, call the Create/Update Developer API method to create the new developer and set the groupId to “4556841222”.

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

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 developers from unintentionally gaining access to another developer’s apps.

Developers with the same groupId have full read/write access to each other’s apps. If you are looking to implement role based controls then blocking actions (like the ability to update an app) will have to be made on your server side before calling our API.