Power Apps Project - HELP

[PowerAppsHelpCD]

I need to create an application where a user will click a button that will return a document to the user that must be electronically signed and stored in a data source. The user must be authenticated and their email should be in the database to return the document to sign. The document should have different versions for different users. How can I go about accomplishing this? Do I need premium licensing or admin controls to accomplish all of this?

Thanks

[FLMike]

Hi @PowerAppsHelpCD 

I cannot answer everything you need, but for it to be signed, all of the Connectors are Premium, that I am aware of.

Plus really I would suggest you hire a consultant for this. We aren't really here to completely replace resources.

If you like my answer, I would really appreciate if you please Mark it as Resolved, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[Kirkby]

Hi.

You can implement this idea using a third-party connector provided by Adobe or DocuSign for e-signatures. These connectors offer functions for sending documents with e-signature requests to designated signers, utilizing signer information from your database, updating the signature progress status when signers complete their tasks, and creating event triggers when there is a change.

1. Premium connector for e-Signature

Adobe and DocuSign provide a secure cloud environment where signers can complete the required actions. Signers do not directly interact with a Power Apps screen for signing; instead, they access the e-signature screen through a link in the email sent by Adobe or DocuSign(Both provide reasonable prices and 1 license is required). When a signer completes the signature, the connector recognizes the status in real-time, retrieves the signed document, and saves it to your repository, such as SharePoint Online.

2. Power Apps per user or app (In addition to 1)

If you implement Power Automate to send the request and independently check the signing process's status through event triggers from the connector, you only need one Power Apps per user (or app). Power Apps will serve as the user interface to save sign requests and signer information to your data source, manage and update request history for the requester's confirmation of the signing progress. However, if you want Power Apps to directly interact with Power Automate for sending requests and monitoring signing progress, Microsoft recognizes that the premium connector is used by all users, so you will need either Power Apps per user or per app for all the users.

DocuSign - Connectors | Microsoft Learn   

DocuSign eSignature for Microsoft Power Automate

I hope it will help.