Users Management: Custom Organization Roles
complete
Alexander Wahler
Right now, I have to give a user the "Admin" role, if I want them to create/edit scenarios.
With admin role, they can also edit the organization and process payments. That are too many rights, for someone who only should edit scenarios.
If I choose operator, they cannot edit scenarios or add them.
Log In

Ilia Sablukov
updated the status to
complete
Edwin Rood
yes, we need more user role control. the standard given roles are far from ideal... we are not able to pass quality control with only admins for edit...
Ian Kamanda
I second this suggestion. At the moment I would like to limit what scenarios certain team members have access to but cant. This makes working with other teams very challenging especially if I dont want them to have access to certain types of data. Zapier makes sharing of Zaps in folders very easy to do. A similar feature would go a really long way in on Make/Integromat.
Richard Cotton
In general it would be great to be able to have more fine grained control over what a Role can do.
That is define a new role but can set fine grained controls (examples ):
can edit scenarios
can edit scenarios not in their team etc
can add/delete scenarios
can activate/deactive scenarios
can add users
can delete connections
can add data stores
can add/edit data structures
can create templates
This will allow more enterprise minded orgs to limit the blast radius of what a user can do without totally locking them down or giving them too much control to accidentally break stuff.
Tomáš Křivánek
This is crazy, I don't understand how this is even possible. It's absolutely crucial feature if you want to use Integromat in a bigger company. We were considering Integromat as a Zapier replacement in a company with 1000+ employees (Zapier doesn't have their data center in the EU, which is essential for a business under regulation). But honestly, this is an absolute show-stopper.
Adam Coster
Yep, this is an enormous "Principle of least privilege" hole. Basically everyone on the team is an admin and can edit anything. Even outside of the security concerns its is way too easy for users to accidentally break something or use the wrong credentials (since connections are also completely accessible to everyone all the time).
The absence of granular permissions within an organization would make Integromat a poor choice for anything but very small organizations (luckily for me that's my situation, but it's still super worrying).
Henry chew
Yes agreed. An extra role would help. One in between admin and operator.
Tom Harwood
Agreed. For us it's the access to connections that we want to restrict. We might use a connection to a particular app that has higher permissions or access than the Integromat user would otherwise have access to. I want to be able to limit their ability to add new modules with that connection, or edit existing modules that use that connection.
Alex Sirota
I second the need for a special role between admin and operator. Specifically I want an operator to be able to clone scenarios, but not add scenarios or delete anything. There is nothing about cloning in the role definitions.