Forms, Workflows & Notifications Feature Requests

Problem: English Department should not be able to edit a form that is only relevant to quantitative subjects. Solution: Restrict users access to forms based on their roles.

It looks like in the course of some recent updates, that the ability to actually delete a approval workflow is not available anymore.

So I think what we need to do to update the app/help center is as follows: 1) Create a full story like modal that will allow the user to send an email ( support@coursedog.com which will be routed to Freshdesk), product webinar (an article in Freshdesk that links out to external webinar) or Feature Request (Canny). The reason I think it makes sense for us to build our own modal is that freshchat does not support hrefing to external locations (Canny) and is mainly built for live chat. We will also change the “Help Center” button at the top so that it opens up this modal so that the user sees the type of help that they can get.

We ran into an interesting situation where a couple of users did not receive a password or the original password did not work. The desire is to have a process by which (in non-integrated environments) to force a user to reset their password or force an additional e-mail to notify them of their account creation.

Relates to refactoring how we present active requests to users. The queue would be all requests users might have to approve in the future, but the request is not at their step yet.