Connections: improve privacy on connections
François-Xavier LEPOUTRE
Prevent a developer from using a connection that gives access to sensitive data.
If the connection is to be used again (on an edit or a new scenario), it should request credentials again.
For instance, the use case is the following:
If a specific Google Account connection gives access to sensitive HR data, then we would like only authorized Integromat developers to use this app in new or existing scenarios. They would have to authenticate each time they'd like to modify the module in the scenario, or use a new module with this connection.
Log In
Lara Hendrikx
Is there a workaround for this issue until this is placed on the product roadmap by Make (other than creating a private Team for each colleague)?
Autopilot
Merged in a post:
Make it possible to create private connections
Jasper van der Straten
I'd like to be able to mark my connections as Private so only I can use them without having to create a separate Team with just 1 member in it.
This way connections to, for instance Office365, can't be used by Co-workers to go through my email and or files.
Pete Schaefer
Competitors such as Zapier, n8n, and Workato provide connection-level security, allowing connections to be private by default and selectively shared. By comparison, Make is behind its competitors and the industry standard.
Engineering Admin
Honestly, I can't believe we have to ask for this. It should have been in the product from day 1
Emi Andre
We have the same issue on our org, we don't want to add connections since anyone could reuse them
Henrik Samils
+1 On this request, currently we are limited of using Integromat functions since one connection to sensitive data is available to all integromat users in the org.