From reading the error at the start of this thread, it looks like the issue is Content Security Policies (CSP) https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy)

CSP’s do as the name says and ensures that only allowed content is loaded onto the website, it is a new web standard that was created to help prevent cross site scripting attacks (XSS), code injection and other client-side attacks, and are not regarded as best practice and also highly recommended by many government sites.

Found this article from Salesforce about CSP’s: https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/csp_trusted_sites.htm

Possible Solution:

From what we understand the entity will need to add ‘https://sucessteam.workflowcloud.com/’ as a Trusted Site and this should fix the problem as described here: https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/csp_trusted_sites.htm

Thank you very much for posting your feedback for our review. At this time, we will not be adding this request to the near-term backlog, due to low votes and as we are focused on other enhancements such as Regional Settings, Advanced Scheduling, etc. However, we reevaluate requests every quarter and will reach out if priorities change. Please keep the feedback coming as it is critical for our longer-term planning.

Thank you for the suggestion. Unfortunately we will not be proceeding with this suggestion as this is not how single sign on operates.

The sign out is of the application and the application’s active session is unique to the application you’re signing into and out out of. i.e. for any application that you configure SSO for, the sign out action taken on one application is specific to the application.

Thank you very much for posting your feedback on separate publishing slots for dev and prod workflows for our review. At this time, we will not be adding this request to the near-term backlog. However, we reevaluate requests every quarter and will reach out if priorities change. Please keep the feedback coming as it is critical for our longer-term planning.

Thank you very much for posting your feedback. At this time, we will not be adding this request to the near-term backlog.

Thanks for the idea however currently we have other near term priorities however we re-evaluate requests every quarter and will reach out if priorities change.

This is not technically possible based on the method we are using to send email. 

Hi,

Thanks for reaching out. I have referred you to our support team who will be able to wrap up any subscriptions you have.

Regards,
Kate

We are currently reviewing the information shown in the onboarding emails however we don't currently have a plan to allow you to disable it. 

Thank you very much for posting your feedback on Azure SSO for our review.

At this time, we will not be adding this request to the near-term backlog. However, we reevaluate requests every quarter and any additional detail you can supply on this request would help. 

Please keep the feedback coming as it is critical for our longer-term planning.

Thank you for your feedback. As this was not an official tool, we will not be adding this request to the near-term backlog at this time. However, we reevaluate requests every quarter and will reach out if priorities change. Please keep the feedback coming as it is critical for our longer-term planning. 

Thanks for your feedback. The alternative and better solution for this use case is to use the Nintex Gateway and RPA to pass variables to other systems.  CSV and email are much more problomatic and not robust for business critical operations.

Thanks for the idea however we currently we have other near term priorities however we re-evaluate requests every quarter and will reach out if priorities change.

Thanks for your feedback.  The conversion action, coming soon, would provide the maximum flexbility and customization for you. There are also other alternetive solution as posted here.

Thanks for the idea for which we've already logged in our backlog.

Currently we have other near term priorities however we re-evaluate requests every quarter and will reach out if priorities change.

Thank you very much for posting your feedback for our review. At this time, we will not be adding this request to the near-term backlog, as we are focused on Styling, Accessibility, Advanced features, etc., that are obviously critical and more important. However, we reevaluate requests every quarter and will reach out if priorities change. Please keep the feedback coming as it is critical for our longer-term planning.

Per Fernando, please submit bugs and feature requests here or the community.