Hello
We have an enterprise license with 30 seats for the creative team. We need to be able to take creative work requests from the full organisation via a form submission. The form submitters will only have view-only seats due to cost.
When a view-only person submits a form and a task is created, they are able to add comments to that task by replying to the email that is received when a form is completed. However, as they are view-only members, they are not able to interact with the task in any other way, aside from replying to this first original email.
My goal is to enable view-only members to be able to approve or give feedback on the work produced when their task has been completed by the person assigned (who is a full member).
I haven’t been able to get the Approvals feature to work in this workflow unless the form submitter is a full member.
I have tried a workaround, creating a rule to email the form submitter that a task has status Ready for Review, and including in the text a link to a second form called “Amends requested” - but this means that we’ll be drowning in duplicate tasks as there doesn’t seem to be a way to automatically merge duplicate tasks, and I don’t want to rely on users to manually follow naming conventions (can you dynamically auto-fill part of a form?).
Another thought I had was to create a rule to email the form submitter that a task has status Ready for Review, and in that email, include the replyto email link they would have had access to when replying to the submission received email - but I can’t find a way to make this easy for the user besides asking them to search their own inbox. Do the replyto email addresses for each task follow any specific pattern?
Context: We have a huge org, and to pay for a license with seats for everyone who might only need access once a year isn’t really viable.
Our org is also in the public sector and it’s very difficult to get add ins and extensions approved.
Grateful for any suggestions