Thanks Troy, but the roles chart doesn’t address the use case I’m looking for.
I want to enable a user to view the history of all Zaps shared with them, but I specifically do NOT want them to be able to edit any Zaps that they don’t personally own.
The idea is to let a non-technical user monitor Zaps without giving them the ability to break anything.
Hi there, @Geoff RSM
Currently only Super Admins and Owners have the ability to view the Zap history for another member’s Zap. There’s isn’t an option to allow a team member to view the Zap history (for all or specific Zaps) without granting edit access. I can definitely see how it would be useful though so I’ve passed your comments here over to the Product Team so that they can look into adding that sort of functionality. While I can’t make any promises around when/if it would be added we’ll definitely let you know if it is!
In the meantime it may help to know that if you share a Zap with the member but don’t share any of it’s app connections then they would be able to view the Zap and it’s Zap history but, they would not be able to edit any steps that use an app connection that hasn’t been shared. That said, if the Zap has apps like Formatter, Filter, Paths etc that don’t have an app connection then they’d still be able to edit those—though if they did publish a change to the Zap that broke something, with versions it would be possible to roll back to an earlier version where the Zap was still working.
Hope that helps. If you have any further questions or if there’s anything else we can help with do let us know!