Restrictable Instance Custom Node


Would it be possible to add a configuration to Instance Custom Nodes to restrict it use by organizations id or filtered by tag?
For exemple, a common need for organizations of internal developments could be resolved with instance custom node. But if that involves restrict information that should not be available in customer organizations, then the custom node can no longer be used to solve the issue.

The same could apply to Application Templates and Templates Libraries.


Hi @Bruno_Matheus_Warmli !

This is an interesting feature request. I’ll file an internal ticket for consideration. Thanks for the suggestion!

1 Like