Currently, the E-Signature is designed for compliance with the U.S.'s Food and Drug Administration (FDA), and requires that the Learner enter either: Username and Password, or Username and PIN.
For us, and any customer using Single-Sign-On, this feature is utterly useless, because our Learners will not know any of those fields.
I wonder how many of Absorb's clients are regulated by the Food and Drug Administration. WE ARE NOT. Imagine instead, if this were configurable as an Admin setting choice:
Either simple click to Accept
Or, set as stricter and re-enter credentials, for FDA-only compliance
Rick
Can we change the fields from username to "email address" at least? We got people who remember their PIN but not familiar what username is.
Rick - there's another idea along the same lines. It's definitely a pain point for those of us who are using SSO. I have now started pre-emptively sending emails to new employees to inform them of their user ID and PIN so that they can use the eSign feature.
The way it is designed now is not a realistic use case from a Client perspective. We personally are encountering this internally. We only have 300 employees and when HR creates training for all users to take a course that includes an E-Signature, L&D has to manage all the Password reset requests. There should be an option for the User to reset their own PIN. They are able to reset their Passwords, so why would not provide the same functionality for the Pin? The reset Password option is on the Login page, which to me would have more security risks than an option to reset a Pin from the E-Signature page or Profile page. I appreciate your consideration in looking at this functionality.
Completely support this suggestion - as users set up a PIN when first logging into the system, and my not need it for months after it is setup. The issue is when they forget it - if they enter it incorrectly, they get an error message that states "You have entered an invalid username and/or PIN. Please try again." This warning message is useless because it doesn't give them any guidance. And currently the only way to fix this is for them to contact an Admin to reset their PIN, but they don't know that. So they basically get stuck in a loop. Changing it to recognize the SSO credentials completely eliminates the need for the PIN.
In addition, if you're going to require a PIN, why is there NOT a "Forgot PIN?" link like with password. This needs to be much easier for our users to do because we will be using the eSignature function for our compliance training, but it is causing issues at this time in trying to administer it. Good feature - just needs a couple major tweaks to be effective.
Using SSO existing credentials would be good.
Hi Paul Gheran,
Thanks, I'll try those as a workaround.
Rick
Hello Rick! Having a manual step is the best confirmation that the individual is in fact who they say they are and haven't just sat down at an unlocked PC. Have you tried leveraging the Terms and Conditions feature for a 'click to accept' experience? Alternatively there is a proctoring function available which can also act as an identity confirmation for Learners who can't complete the e-signature verification.
it would be much simpler if the e-signature used already existing SSO credentials instead of asking users to remember a second set of credentials just to e-sign something in a system that they've already been verified in.