Skip to main content

Workaround for triggering an Esign task via a self-service flow

  • January 8, 2024
  • 8 replies
  • 692 views
R
Bobber

In this case, when you have a flow that triggers an eSign form, that user must have the permission to trigger that form on themselves. This is why the system isn't triggering the eSigns because the employee doesn't have that permission.

 

To allow this, you will have to create a custom permission group for your employees and give the users access to trigger eSign signatures by enabling some permissions.

In the access rights, you want to put email same as viewer and then give them access to request eSign signatures.
This will do it but it will let them trigger any eSign on themselves.

These are the screenshots for your reference of the permissions needed (refer to the attached screenshots for permissions needed).

 

Please note:
This has a caveat that enables the employees to trigger any form or document for a signature to themselves.
However, after implementing these permissions, the users should be able to complete the flow and the system will trigger the eSign forms as well.

 

    8 replies

    O

    Thank you for this - I’m sorry if it’s a silly question, but what is the implication of ‘This has a caveat that enables the employees to trigger any form or document for a signature to themselves.’

      Johnny Barnett

      Thank you for this - I’m sorry if it’s a silly question, but what is the implication of ‘This has a caveat that enables the employees to trigger any form or document for a signature to themselves.’

      The employee would be able to request a signature (for themselves) on any form you’ve got saved in the e-signatures section. I was looking at having a self-service referral letter generated, but this means they would also be able to self-request any other letter you might have set up. The implications are entirely dependent on what other use cases you might have for the e-signature function.

      https://www.linkedin.com/in/johnnyrbarnett/
        M

        Hello 

        Is it possible to add this as a Request for Improvement?

        We want the flow to generate a medical form for employees, but because they don’t have eSignature permissions, the process fails. However, if we grant them this permission, they gain access to all eSignature templates, which is not acceptable for us.

        It would be great if you limit eSignature permissions to specific templates. 

          S

          yeah would be great if you could categorise the esigns like the workflows and  give access to certain esigns not all of them, would solve many niggles we have certainly 

            Jessica Lane
            Bobber

            Hi ​@Mariia Kulikova , ​@Sophie Hawes 👋🏻

            I will be happy to share this feedback with the team for consideration!😊

             

            Jess
              Tomas Desiderioscioli

              Hi team! 👋

              We’d love to see improvements in how e-Sign permissions are handled.

              Our main request:
              We want employees to be able to trigger a workflow (e.g. through a self-service action), where one step involves an e-Sign request, and they can sign the document assigned to them — without having access to all e-Sign templates in the system.

              Right now, if we give employees e-sign permissions, they can self-initiate any template, which isn’t ideal and prevents us from enabling this capability.

              A possible solution could be:

              • Letting employees sign documents assigned via Tasks.

              • While restricting template access so they can't browse or self-initiate unrelated forms.

              This would allow us to open up powerful self-service flows, while keeping control over sensitive templates.
              Thanks for considering it!

                S

                Hi team! 👋

                We’d love to see improvements in how e-Sign permissions are handled.

                Our main request:
                We want employees to be able to trigger a workflow (e.g. through a self-service action), where one step involves an e-Sign request, and they can sign the document assigned to them — without having access to all e-Sign templates in the system.

                Right now, if we give employees e-sign permissions, they can self-initiate any template, which isn’t ideal and prevents us from enabling this capability.

                A possible solution could be:

                • Letting employees sign documents assigned via Tasks.

                • While restricting template access so they can't browse or self-initiate unrelated forms.

                This would allow us to open up powerful self-service flows, while keeping control over sensitive templates.
                Thanks for considering it!

                Agree with these suggested improvement. This would be a big improvement in our workflows. 

                  Harshil Boparai
                  Bobber

                  Thanks so much for sharing your feedback and feature ideas. We appreciate your insights! The best next step would be to share this directly with your CSM. They’ll ensure the full context is captured and keep you informed as things develop. ​@Tomas Desiderioscioli, ​@Siobhan Williams 

                  Terms & ConditionsAccessibility statement