I have sheet s with 10 or more flows, would be nice to enable/disable them all at once for data migration or fixes needed.
Sign in to see the current vote count, add your own vote, or leave a comment.
We have hundreds of project sheets created and archived every year and when archiving, we have a process of turning off all automation workflows so that they are not triggered once the project is completed.
Some of the sheets have +10 automations on them. It would be great if there was a toggle button that would turn off all automations with one click rather than toggling each automation off individually.
We collaborate with a lot of people. Not uncommon to see 30+ automations. Working on large projects, we make changes to log sheets for time to time when the need arises. These changes will often trigger many automations. It would be very helpful to pause all automations, make sheet changes, then reactivate the automations.
A pause feature would be great. It is a pain point to go in an edit all automations to inactive when making changes. Especially for those of us that sometimes forget to turn them back active.
I totally agree with this suggestion. Turning off all automations en masse would be really helpful and a great time saver.
I have a workflow with nearly 40 automations, half of which are email-based requests for updates with various sets of triggers. While I know the automations work, due to months of testing, when our system went live to the institution, I became very worried that the automations wouldn't run and I'd have no idea whether or…
Hi, I am part of a very large organization where hundreds will have Admin access to hundreds of Workspaces in order for them to contribute and make full use of Smartsheet features. Currently All Smartsheet workspace Admins receive Workspace access email alerts. Which means hundreds of team members will effectively be…
It would be useful if users who clicked a Dynamic View link (that they were not previously added to) could "request access" to the Dynamic View, and provide a reason, so that the admin can easily grant that access. The use case for me would be to avoid having to pre-populate and then maintain a user group of viewers, but…