My main use case for Adobe Sign internally from an organization perspective is that I have set up a customer registration form, which has streamlined processing new customer information internally so that we can add the customer data and information into our financial system. When we meet with a new customer and need to onboard them into our system, we normally send them a registration link built using Adobe Sign with the web forms feature. Once the customer receives the link to the web form, they have the ability to fill in all of their organizational details, including their organization entity name, their classification, and additional information such as their tax number, their banking details, and their accounting contact. The web form also gives them the ability to upload tax documentation, customer registration documentation, and banking details. Once that has been filled in and signed by the customer, it is routed to an internal Learning Curve approval process where an admin person reviews the registration form. Once the admin person is satisfied with all of the information, the internal administrator approves the registration form, captures the information into our financial system, and thereafter it is routed to a financial manager for final approval. The financial manager reviews the information inputted into the financial system and provides any specific, special payment term arrangements for that specific customer. Once approved, all three parties—the customer and the two internal approvers—receive a signed copy of the Adobe Sign customer registration document.
My use cases for Adobe Sign include working in NNE until April, where I played as an Adobe Enterprise Admin for global NNE. I acted as a middleman between Adobe Enterprise Support and Adobe Enterprise Admin in NNE, bringing new features and being the first point of contact to communicate with Adobe Enterprise Support to implement them in NNE. I am very experienced in adding users' accounts, creating users' accounts, and creating products for users. I used the Advanced Sharing method extensively in Adobe Sign for our seven major projects in NNE, creating different groups for different projects to see each other's agreements and track their statuses. If someone goes on holiday or is sick, the agreement won't get delayed due to the Advanced Sharing method, allowing us to switch over to the user's account and track the agreement. I also helped people in NNE significantly to use the Advanced Sharing method, and we utilized reports in Adobe Sign to track how many agreements were in progress, canceled, and specifically related to projects. Last year we were informed that the integration between SharePoint and Adobe Sign was expiring in July 2024, prompting us to create a Power Automate flow to automate agreements in Adobe Sign using Power App and Power Automate flow inbuilt with the SharePoint site, which made work much easier. Before that integration, we often faced issues where signed documents would not return and be stored in the SharePoint site, but after the flow was created, we didn't receive any issues with receiving signed documents. We heavily relied on Adobe Sign for signature workflows, Advanced Sharing method, tracking reports, creating products, and assigning accounts to new users.
It's a diverse range of customers we cater to, including universities, commercial and American institutes, and government departments. Our services cater to various needs, ranging from student registrations in universities to signing legal agreements in government, and electronically signing contracts in the commercial space, especially for organizations operating remotely without access to printing facilities or standard office functionality.
Adobe Sign is a reliable and user-friendly digital signature solution that offers a range of customization options and robust security features and allows users to sign, send, and manage documents online. It's a cloud-based service that streamlines the signature process and reduces the need for physical paperwork.
Based on user reviews, Adobe Sign is highly regarded for its ease of use and integration with other Adobe products. Users appreciate the intuitive interface, which makes...
My main use case for Adobe Sign internally from an organization perspective is that I have set up a customer registration form, which has streamlined processing new customer information internally so that we can add the customer data and information into our financial system. When we meet with a new customer and need to onboard them into our system, we normally send them a registration link built using Adobe Sign with the web forms feature. Once the customer receives the link to the web form, they have the ability to fill in all of their organizational details, including their organization entity name, their classification, and additional information such as their tax number, their banking details, and their accounting contact. The web form also gives them the ability to upload tax documentation, customer registration documentation, and banking details. Once that has been filled in and signed by the customer, it is routed to an internal Learning Curve approval process where an admin person reviews the registration form. Once the admin person is satisfied with all of the information, the internal administrator approves the registration form, captures the information into our financial system, and thereafter it is routed to a financial manager for final approval. The financial manager reviews the information inputted into the financial system and provides any specific, special payment term arrangements for that specific customer. Once approved, all three parties—the customer and the two internal approvers—receive a signed copy of the Adobe Sign customer registration document.
My use cases for Adobe Sign include working in NNE until April, where I played as an Adobe Enterprise Admin for global NNE. I acted as a middleman between Adobe Enterprise Support and Adobe Enterprise Admin in NNE, bringing new features and being the first point of contact to communicate with Adobe Enterprise Support to implement them in NNE. I am very experienced in adding users' accounts, creating users' accounts, and creating products for users. I used the Advanced Sharing method extensively in Adobe Sign for our seven major projects in NNE, creating different groups for different projects to see each other's agreements and track their statuses. If someone goes on holiday or is sick, the agreement won't get delayed due to the Advanced Sharing method, allowing us to switch over to the user's account and track the agreement. I also helped people in NNE significantly to use the Advanced Sharing method, and we utilized reports in Adobe Sign to track how many agreements were in progress, canceled, and specifically related to projects. Last year we were informed that the integration between SharePoint and Adobe Sign was expiring in July 2024, prompting us to create a Power Automate flow to automate agreements in Adobe Sign using Power App and Power Automate flow inbuilt with the SharePoint site, which made work much easier. Before that integration, we often faced issues where signed documents would not return and be stored in the SharePoint site, but after the flow was created, we didn't receive any issues with receiving signed documents. We heavily relied on Adobe Sign for signature workflows, Advanced Sharing method, tracking reports, creating products, and assigning accounts to new users.
I used the solution to sign my W8 form. I used it to sign forms of all sorts. The company sent me a document via Adobe, and I simply signed it.
I use Adobe Sign for basic things only. My main job does not require me to use it. Usually, I just use it for signing in PDF files.
It's a diverse range of customers we cater to, including universities, commercial and American institutes, and government departments. Our services cater to various needs, ranging from student registrations in universities to signing legal agreements in government, and electronically signing contracts in the commercial space, especially for organizations operating remotely without access to printing facilities or standard office functionality.