# Application Features The calling application can pass the following parameters to create a comprehensive signing experience: **Adding Document Fields** Add document controls such as Name, Email, Textboxes, Date Controls and much more **Adding Signature Placeholders based on Search Text or Coordinates** emSigner provides the ability to send signature placeholders for various participants in the workflow either using coordinates or using search text (this will automatically place the placeholder based on text on the document) **Adding Signatories** Add list of users to pre-populate the list of signatories or reviewers. If you don't pass them, emSigner allows the originator to dynamically add list of signatories or reviewers by dragging controls **Co-branding** Co-brand the entire page with your logo, colors etc. This can be done by having your administrator login to emSigner Admin portal to set this up **Setting Reminders** Set reminders for participants and pass these as parameters in the API to ensure participants get reminded when they need to sign on a document **Protecting PDF's** Protect PDF's and limit printing, copying etc once the final workflow is completed **Setting Watermark** Optionally set a watermark on the PDF **Using eStamping** Enable eStamping for certain regions such as India or Indonesia by using this setting. This allows for dynamic placement of stamp papers as part of the document signing journey including payment of stamp duty **Using Webhooks** The embedded signing flows can be extended by using Webhooks which notify source applications of event triggers. Please refer to section on Using Webhooks for configuring webhooks as part of your application --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://support.emsigner.com/apis/embedded-signing/how-tos/application-features.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.