Hi @ByrneReese 

I have joined the beta and testing the features, one request I would like to add to the workflow is to include an indicator workflow showing an active workflow. 

@vincent-s Great feedback. We show an indication of whether a workflow is active through the toggle displayed in the list of workflows as shown below. 

I am curious - is this what you mean? Or are you looking for an indicator elsewhere?

I am thinking to have the visual indicator outside of the workflow screen, like the out-of-office or the work-flow icon

 

@vincent-s Interesting. I like this idea. Our UX team has very strict guidelines about how these types of indicators are used to ensure consistency across all products. That being said, and exact implementation aside, this is really interesting. 

Wondering what an admin might see though - as they manage automations across the whole organization. Thoughts? 

And if you don’t mind - tell me more about how this is helpful to you so I can share with the UX team. The number of active automations is not likely to change every often, right?

Hi @ByrneReese 

I am thinking of users setting up after hours SMS reply then moving to new schedule or team forgetting to update the workflow with the new schedule. 

Also, if we have more than one SMS auto reply it would be great to be able to update the name since you can create multiple replies depending on the word found on the SMS received. 

@ByrneReese - how do we control which users in our organization have access to the Workflow Builder functionality? As well as which users are allowed to create workflows for themselves vs for the company or another user/extension? 

@themphill Thank you so much for the question and welcome to the beta! Right now all users have access to Workflow Builder, but by default they can only create personal workflows. Super Admins on the other hand have the exclusive ability to create workflows on behalf of others, and to create workflows for non-user extensions. Our recently updated Admin Guide covers these entitlements in more detail. 

In the future we plan to add permissions that will prevent users from being able to access Workflow Builder all together, but personally that is not something I would encourage, any more than I would want to prevent my employees from using email routing rules in Microsoft Outlook or Office. We see a great deal of potential in empowering individual users being able to automate simple mundane and personal communication tasks.