Today our apps permission are by default created with permission:
Everyone - Viewer
Apps creator - Owner
Tulip role “AccountOwner” - Owner
Tulip role “WorkspaceOwner”-Owner
In our context Tulip role “Workspace Owner” are not used (too much priviledge on connector) and we used a custom role “xx Workspace Owner”.
The consequence: workspace owner need to add manually all apps builder working in the team for every apps. If it is not done, the apps couldn’t be manage if the only owner is on holiday or left the company.
It would be very useful to have the ability on Workspace setting to select Custom Role or even better User Group as default application owner.
Hello Nicolas, to make sure I understand- would the ideal case be the ability to assign user groups to apps as owners, and that would solve the problem at scale because you could assign the right users to the right apps easily? Or is it that you really want Workspace Owners to be owners of all apps, and simply cannot do that due to the connector permissions?
Because of how our company uses Tulip, when we release a global application, we copy it to a dozen or so location-specific Tulip instances. One step in our publishing workflow is to then assign a short list of the same named users on every instance to be the owners of the app, then change “Everyone” to view only. It would be much preferred to just make these same few people a group we could just select one time for each app we publish in each instance, rather than having to open the list of all users, locate and click through adding several of the same people on each instance x 12 instances. Very tedious.