51ºÚÁϲ»´òìÈ

Transcript

Hi there everyone and welcome to our latest Acrobat Sign webinar about our latest improvements all around Acrobat Sign and electronic signatures here for you. We have a couple more people joining but we’ll be starting momentarily.

Now to get us all started let me just introduce to you the team around this webinar.

So besides myself, Jonas Tussar, Senior Product Manager here for Acrobat Sign, we have a couple of my colleagues right in the background to help with any questions and facilitate the meeting with myself. First of all, I’d like to introduce Dafna. Dafna is the Principal Product Manager here mainly focusing around all our user experiences so you’ll see her answering most of those questions in that area. Andrea Valle here, also Principal Product Manager. His focus is largely around trust and identity compliance and security. He’s also known for speaking regularly at global conferences and participating and leading in some of the industry standard developments. So all the questions around trust and identity compliance and security are likely to be taken up by him. Dafna here, our Group Product Manager. His focus is all around product strategy so your feedback is very important to us. Please keep that in mind. We’ll be having a couple of polls and surveys in the end to help us make sure we hear you and we can develop a product in the right direction. And lastly, from our engineering team, we have Reetam also on the call. He’s an engineering lead and especially for program management so you’ll be chiming in and helping out to address all those questions that might come up.

Now, we have a vibrant variety of people from today. We had a lot of registrations from around the world asking and participating in this webinar. So what we’re going to do today is we have a mix of different agenda items here, some of which we’ve announced as part of the webinar such as our latest features around PDFA, around WhatsApp and so on. But we also wanted to take a bit of a deeper dive on some of the areas that were really popular from one of our last webinars. So following my introduction here, we’ll be diving into the area of trust and compliance for e-signatures. This will start with a bit of a overview around identity assurance and digital signatures. One of the more complex areas around e-signatures, so we’ll be explaining a couple of things around there and help inform you also about improvements that we made over the last months.

PDFA for long time archiving, a very recent addition to the product feature set, we’ll be going into detail there and also show a quick demo and, of course, even notification via WhatsApp, another very popular feature that’s made it into the product. I’ll be demonstrating that as well. The second big bucket that we’ll try to cover today here is all around protecting sensitive agreements. We have about three different features that help our customers protect their agreements. So what we’ll do is I’ll give an overview of all of them and then try to explain and recommend which ones to use when. And afterwards, we’ll have a Q&A section where we’ll be going into some of the most popular questions we’ve seen along the way.

Just to give you a bit of an overview in terms of what we and how we expect questions to come in, if this is your first time joining this type of webinar, we’ve disabled the chat because we’re using the Q&A functionality in Teams to really manage the questions and answers more structured. So if you look at your screen, you should have a Q&A button right up there. You see that here on the right-hand side of the screen, on the top screenshot. And that will allow you to ask a question. Once you ask that question, it’ll basically fall into a funnel of things to answer. And once we’ve looked at it and answered it, it will show up in the published area of questions. You can also use the filter. You just filter on all questions or only my questions. So there are a couple of things you can highlight. Very importantly, please do vote on things that interest you as well. So as much as you upvote, we try to prioritize the ones that are outvoted so we can get to them first and foremost. We also have a couple of polls and a survey at the end of the webinar. This is really to learn more about you and how you use the product. So to kick us off here, I’m going to kick off the first poll just to give us a bit of a starter. I mentioned we had a lot of people register from all over the world. Now it’s time. Let’s find out from all of those attending. Where are you joining us from today? You’ll be seeing that poll come up just now in front of your screen. If we can get a bit of an overview there, that’ll help us inform. I see. There we go. North America is taking the lead here, followed by Europe. But I can see votes coming in for all different areas. So thank you very much for joining today. It means a lot to us and it just shows how global our audience is. So we’ll take that into account as we now go into the webinar and explore some of the areas I’ve just touched upon. Good. To get us started, let’s review 51ºÚÁϲ»´òìÈ Acrobat Sign and really our focus areas in terms of our product and product strategy. Acrobat Sign is 51ºÚÁϲ»´òìÈ’s global signature platform. And with that, we are really developing the product according to the needs of our global enterprise customers. What that means is we are essentially focusing on four key areas that we believe have the highest impact on all of our customers around the world. Now, the first one is about effortless signing and management experiences. So this is the area of user experience. If you’re a sender, if you’re an admin, or if you’re a receiver, there are different user experiences that really lead to getting a document signed. So this first area here, first and foremost, is focusing solely on that. The second area then is all around compliance and trustworthiness. This includes our area of trust and identity, our area of compliance with industry standards, but also with local regulations. So it’s a broad spectrum that we’ll be exploring a bit today in the webinar. So keep posted for that. The third area here on the bottom left is what we call connecting people and the apps they use every day. So this specifically focuses on our turnkey integrations. There are dozens, if not hundreds of them out there where you can simply integrate Acrobat Sign with some of the most common enterprise tools like Salesforce, Microsoft Teams, Workday, and many, many others. There’s no developer needed essentially to connect to an API. It’s just a matter of configuration to get that done. So it’s another area we see a lot of impact for our customers and where we continue to invest in. The fourth area then here is coming towards automation. And that’s what we’re seeing a lot more in the recent days for our customers who really build end-to-end automation for document lifecycle and workflows. So 51ºÚÁϲ»´òìÈ is a big, big provider for document processes. So really from the automated creation of PDFs, building them out, setting up a signature using Acrobat Sign, and then also extracting relevant metadata via API to a system of records. A lot is possible not just with our integrations with Power Automate or Zapier as some low-key platform, but also directly via the APIs. So it’s a big area where we see more and more interest. So, of course, this is our fourth area here that we continue to focus on. Now for anyone who might have missed some of our releases, this year we had three major releases. A major release is what we call essentially a release that holds a lot of the new features. There might be minor releases in between. We had a couple of them this year where some small things might be enhanced and some things are fixed. But really, when we talk about new features coming into the product, they mainly stick to the major releases. So for this year, we had the April release, the July release, and the October release that’s just coming up. Obviously, for today, our focus will be on what has been released. And then for October, we’ll have another webinar to get you all up to speed. And if you missed any of that, here’s just a quick overview of what we’ve been releasing. As you can see, there are dozens of new features that made it into the product. I can only recommend checking out our release notes in case you missed that. There’s a huge documentation around what’s new. And, of course, for today, we’ll be going into some of the highlights of the July release. So without further ado, let’s jump right in. Trust and compliance. So here, let’s first focus around identity issuance and digital signatures.

And to get everyone bored and set the stage for this area, what we mean when we think about compliance and trust with this here is really the only thing that’s more important than getting your documents signed is being sure they’re signed securely and meeting the right compliance regulations and other areas of focus. So if you’re thinking about your e-signature processes, there might be some areas where you need authentication for the signers to really make sure the right person is signing agreement. Now, HowaboutSign has a huge choice of different methods, starting from simple setting a password or a phone authentication going up to really identity verification methods or digital signatures where a signer certificate is attached as well. So it’s a huge range of options that can feel overwhelming, but they all have their place within this area because it really depends on your use case that you’re using and what you’re trying to get signed, what you might want to use. Secondly, what kind of plays into this, not all e-signatures are equal. So what that means is really the default e-signature and HowaboutSign is the simple electronic signature. However, in some cases, especially when you’re working in some more regulated countries or industries, it might require actually a different kind of signature that will include some authentication methods or even include a digital signing certificate. So it really depends where you’re trying to go and what you’re achieving there. That’s also why we’ve been quite busy in providing some legal guidance for different countries. You can find that all on our adobe.com webpage. There’s a bit of a global overview, but also one is specifically for the EU where we have a lot of EIDAS regulation on the topic. So we won’t be going into detail during today’s call on these. It’s a huge area. It really depends on which country you’re looking to really get documents signed in, but there’s a lot of resources to help you by that. Not at last but not least your 51ºÚÁϲ»´òìÈ account team who will help you out there. Let’s explore a little bit around the signature categories that I just mentioned. We from 51ºÚÁϲ»´òìÈ, we try to differentiate here between three different types of signatures. This is really to accommodate the international different laws because different terms are used whenever you’re looking at different countries’ regulations. The first one I mentioned, the simple electronic signature, actually sits here in the basic signature frame in the first bucket. The verified signature then is the next level where you will have a signer who was identified by a trusted third party where often the signer identity report is also attached. So you’ll have a much higher level of assurance which is the key word here, which essentially is the level of trust that you’re putting into that this person is really the person they claim to be. And the last and final section is our digital signatures. So this is where a signer was identified by a trusted service provider and a digital certificate is additionally applied for the signer as well, proving their identity. Now depending on which signature you choose you will see that with increased trust there comes also increasing cost. Yes, identity verification methods do have an additional fee often with the providers who kind of basically service this. And you’ll see more friction because we’re challenging the identity of the signer. So it’s a mix of really understanding what is needed for your use case and also what’s the effect on the user experience that then you’ll likely want to discuss with your form of signature. Now let’s go and click down here and re-understand what are the different methods that Acrobat Sign provides for the different signature types.

For basic, really it starts with the basic email authentication where you receive a link to your email inbox and click on it. So that’s what we would call a simple authentication. Then there is a series of two-factor authentication methods that we have in product.

Phone authentication, like setting a password, these are typical two-factor authentications that would still for us sit in the basic bucket. For the next level of verified signatures, here we differentiate really between identification and electronic ID.

Identification is everything where I might need my passport or other credentials where a live check authentication is made. KBA is also part of this bucket for everyone who doesn’t know what KBA is. That’s specifically for the US knowledge-based identity method that is then checked with the government to basically identify the user who they claim to be. Electronic ID then is something more up and coming and in some countries really the standard. So things like bank ID, especially in the Nordic areas, is kind of a standard where the banks are issuing digital ID to the bank account holder and with that they can identify themselves against different services including Acrobat Sign. Other EID forms are really around the globe and they vary. So there are many many different forms. Most of them we offer through what we call the digital identity gateway. That’s something you can set up in Acrobat Sign to match that EID with the different service provider that basically facilitates the whole process. However, there are also service providers that will do the identification really from the start without any existing ID. So they will basically go through an IDV verification where the user needs to go through a process, show their passport and take a selfie in some cases. So there’s a wide variety of methods out there. Now coming to the last bucket, digital signatures. These really are exclusively with these come exclusively with digital certificates. So essentially what happens here is you have a check the identity of the person. So that’s step one. There’s an identity verification that’s part of this. That identity verification in some cases can be an electronic ID. In some cases it’s going to be a full passport check and selfie. But what they’re adding on top essentially is they’re issuing a digital signer certificate and that signer certificate will be attached to the final agreement that is coming out of Acrobat Sign. So once the document is signed, essentially the TSP sends us that digital certificate and we’ll attach it. In some cases really that process is historically been more manual. So there is an option for digital signatures to basically download the agreement and attach this digital certificate from a trusted provider manually in Acrobat, which is then again uploaded to Acrobat Sign. But really the new method here is using the fully digital experience and what we call cloud signatures where the certificate is simply transferred to us from a cloud service of the trust service provider. Now that’s been a little bit of input here. So let me just sum up again the main differences and to avoid any confusion really let’s focus on verified and digital signatures because these are the more high level of assurance methods. Both will include an identity verification check. It might be with an EID, it might be from the get-go with a passport or driving license. However, the big difference is with the verified signatures you will have a signer identity report but only with a digital signature. You will have a signer certificate attached to the document. Now that can be very important when you’re dealing with regulations, for instance in Germany where the local regulation says that you need a qualified electronic signature. So that would only be achieved with a digital signature. So again, it really depends on the country you’re operating in, on the region that those laws and sometimes the industry you’re in, which type of signature is needed. But these are all the different methods that Acrobat Sign offers to you. Now let’s get into one of our more recent upgrades in this space, especially for verified and digital signatures. We’ve released the identity check policy that you see here that has made its way into the product. It might not be enabled for you right now by your admins but this is something to check. Now why is this interesting? Essentially, when you send a document to someone who you believe their name is Jonas Dussard and this document is then going through any type of identity verification. Let’s say it’s an EID through bank ID where I just need to log into my bank and this will basically get me through the check.

What this setting here does essentially, it will double check that you actually have Jonas Dussard signing the document and that’s done by retrieving the name that was checked by that third party, by that identity provider. In this case, that’s coming back from the bank on my account. If that’s matching with the name you provided us. If you know I am Jonas Dussard and that bank account is also saying, hey, someone just logged into the bank and their name is Jonas Dussard, then we know it’s matching. But there are some cases where it might not be matching and you’ll get into an error. With this setting, you can basically avoid someone else signing for another person. It’s very often the case in married couples who are kind of doing transactions for each other in their busy lives. But in some cases, really you do want to enforce that the right person is signing it with the right identity. So without further ado, let’s jump into a demo here to show you this a bit more hands-on. We’ll go the full way from setting up the agreement and kind of highlighting different methods to you and go about it. So what you see here essentially is our customer onboarding form set up. We have a couple of standard selections for agreement settings. And now we’ll start by looking into the multi-factor authentications. Now, as I mentioned, there is a wide variety and depending what has been configured for your user group, you will see different methods as options. Here I have a lot of options activated so it looks like a very long list that’s not typically the case but can be. So really our recommendation is to understand what the user group needs in terms of authentications and then enable those that are relevant. So here you really see everything from password, phone, email OTP, even the WhatsApp authentication, which is new. We’ll have to take a look into that. And then we’re going into the area of digital identity gateway. So this is where I mentioned there are different service providers, they have different methods. Again, there are regional differences, some are for the US, others are for the UK. So you’ll see a wide variety. ID Now, for instance, is more like a global IDV method. So it really depends on what kind of service you’re drawn towards and what the use case needs.

Now what you see here in the next screen really is about the identity check. So you’ll see I kind of explained name matching, but the same is true for email matching. So also the email can be matched if you’d like this to be. And you have additional controls here to basically allow partial name matching. So perhaps that was a typo in the name you put in here as the sender. In that case, it would not necessarily be unchecked. So partial name matching is also supported as part of this one check. What you’ll see here now is just an example of how setting up a phone authentication works. In this case, I’m just sending it to a random number in the UK before sending it off. So we have this process now set up, one with the digital identity gateway with an IDV check and the other one with phone authentication. So again, if you’re not seeing any of these options in your user experience, it’s likely you need to talk to your admin, why that’s not the case and work backwards essentially.

Good. Again, just a quick reminder, if you do have any questions, just pop them in the chat. My colleagues will get to them. But let’s move forward here with the next area.

Right. So now that we’ve configured the transaction, we’re jumping into the authoring mode. And the authoring mode is again another place where you can reinforce the digital signature. So I mentioned there are different type of signatures. And especially the digital signature is one that you would enforce here at this level directly in the template. So as easy as it is to add a signature, it’s just as easy to basically specify if this is an e-signature, so basic or verify signature or a digital signature. Because that will change the whole way users sign, digital signatures are then basically double checked and verified at the process. So we’ll look into that now when we are stepping into the recipient experience for that.

So right here, let’s have a look. So now we’re stepping into the the foots of the recipient. We set up for this video here, this demo will show essentially two things. One, there is an authentication challenge via phone authentication where the user will need basically to verify that that phone number belongs to them and they get the phone OTP and they need to enter it so they get access to the agreement. And that is true for all authentication methods including the digital identity gateway methods. The challenge will basically arrive before the user is able to see the document. Digital signatures happen afterwards. So that’s essentially digital signatures will challenge the identity of the signer when they’re trying to sign. So they typically have access to the agreement first. And in this case, they need to go to the authentication challenge to get access to the agreement and then again go through a higher level of friction and of authenticity to then move forward and digitally sign the agreement. So we’re starting from the email that we’ve received and this will then bring up the Acrobat sign signing page. And here you’ll see we have the phone verification where we’re now requesting a phone OTP to the phone. And as I’m receiving that on the phone, I’m just entering it here in the code space and once that passes, I will get access to the agreement. So that’s exactly what we’re seeing here.

Now there might be some mandatory fields that I need to fill in. That’s all normal. We’ll jump the optional fields here and really focus on the digital signature. So this is the key difference between a normal e-signature. This will challenge the user to identify themselves. And here’s a list of the different TSPs, trust service providers, that I mentioned. For this demo, we’re going with ZL ID, which is an EU TSP and ZL ID. Basically, I’m a user there in this use case already. I had to identify myself using a password to basically set up my account with ZL ID. And now I need to scan the QR code that was displayed and that’s what I’m doing here on the app. And I’m also basically proving my identity here with a fingerprint check. And once that’s done, I have basically proved my identity. Now with cloud signatures, there’s a second step. There’s always two checks here. One is the identification and the other one is the authorization. So now I am authorizing the signatures with ZL ID and applying the digital signature certificate. So again, I need to scan that QR code just very quickly and authorize it again with a fingerprint check to complete the signing. So you see it’s a lot more friction to enforce that digital signature and really comply with the regulations there that the EUEI status law is putting forward. So that’s the general experience that you’ve just seen around verification methods and digital signatures. And there are many, many different varieties. So as you saw, I just basically showed you phone authentication, digital signatures from one of the TSPs. They all vary slightly, but essentially the legal outcome is what counts here. So make sure as you explore new use cases to keep that in mind, double check with legal departments if you are uncertain about what kind of e-signature you can use in that case. Good. I’m sure there have been a lot of questions already coming in and my colleagues are getting to that. But before we’re jumping into the next area, I just wanted to take a step back here around long-term archiving. So long-term archiving, to give a bit of context, what this means is really when documents are optimized for long-term archiving, it means that we’re ensuring that agreements can be viewed the same way in 10, 20 or 100 years, regardless of any software operating system changes. And the solution that 51ºÚÁϲ»´òìÈ has spearheaded here was the creation of the PDF-A format. So this is different to the PDF format because it restricts PDF features to those that can really guarantee consistent rendering over time. So one, it again, it restricts, that means less PDF features are normally supported in there. But we’re doing that to make sure that document can be viewed in many, many years time. Use cases, so why would you want to use that? Really, in some cases, government prescriptions and regulations coming in for certain types of documents or preferences, but also financial regulators and especially the insurance industry, they can enforce this and they have a preference on that. So again, it really depends on the region you’re operating in and the surrounding laws and regulations if you need this. However, it’s never a wrong decision to make sure documents are long-term, archivable. So even if it’s just a preference from your organization, that feature is there to help you because as part of the July release, the PDF-A format 2B is now supported. And that is for accepting, validating and maintaining documents in the PDF-A 2B format. Now, what we’re doing next in the next release, really, which is coming very, very soon, we’re going to allow you to not just accept documents that are already PDFs and keep that format going forward, but we’re also going to convert non-PDF-A formats into the PDF-A format, normalize them so that what comes out of the process is always according to the standard. So that’s very exciting because it really helps with the user experience. We’ll go into a demo and you’ll see what I mean shortly. But just to kind of reinvent for any admins on the call, this feature sits behind a setting. And essentially, that setting can be configured on account or group level. If done on group level, that means every sender sending out a document will basically enable this PDF-A workflow. And then in that case, for the moment, I’m talking about the July release, it will require senders to only upload matching PDF-A formats, specifically to the 2B format. So, if you have any pressing PDF-A workflows that really need to be sent, it would mean you need to make sure the document you’re uploading is a PDF-A 2B.

Let’s see how that looks like in the demo that we’ve prepared for you here.

So, again, we’ll just quickly enable that PDF-A workflow for a specific group. What you see here is the user uploads a normal PDF. And as I explained, this is currently not yet supported, coming soon. So, in this case, the user needs to upload the right format, which is the PDF-A 2B. And then we’re jumping into the authoring area where the sender here is a signature field. And to be specific, a digital signature field to make sure this document is signed in the right way with the right level of trust. In this case, we’re using the QE Trust Service Provider Trust Pro. It’s a slightly different process, as you can see here. There is an authentication password and an OTP that is received by SMS. With Zeal ID, I had the QR code scanned. So, you’ll see there are different kinds of services and user experience depending on the TSPA you’re using. Now, what’s really interesting here is what’s coming out, as you can see in Acrobat, the PDF-A was verified right there. And it’s also part of the audit report that will highlight that this document, this whole workflow is to PDF-A 2B compliant. So, it helps you manage that and make sure those events are correctly captured.

Great. Let’s move to the last feature of this area, Trust and Compliance, Communicating with Trust. This is all about our agreement notifications via WhatsApp. And what you’ll see here is, and why we’re including this in the Trust area, really is communication here is coming from a verified origin. So, especially it’s coming from the 51ºÚÁϲ»´òìÈ Acrobat sign verified business account, which means this is more likely to be trusted by the users. And while WhatsApp might not be the favorite B2B communication tools in Europe, another country is quite common. So, for instance, in Brazil, organizations using WhatsApp for business for communicating, especially with consumers is quite common. So, again, depending on where you are active in some regions, this feature is very, very popular and actually might be preferred by your users. And also, in some areas, receiving an SMS might not be that easy because that network doesn’t reach the area. So, WhatsApp to deliver that message if email should not be used. So, what you see here is essentially just a quick demo of how the document is being signed and received in an Acrobat sign. So, there are three different notifications, one to request, one the signature, a reminder, and then, of course, the completion. All these you see in the screenshot here on the left.

Good. Now, let’s jump to the sender perspective just to quickly demonstrate how this is set up for senders. Essentially, what you’ll see here is there is a drop-down bar if enabled to choose from different delivery methods. So, here in this case, we’re choosing WhatsApp as the delivery method and we need to provide a phone number. So, this will be sent to the WhatsApp method. Now, an email can be sent in addition, but in some cases, you might not have the email of the user actually. So, you can untick the email and only send this via WhatsApp to make sure it can be sent out. So, this is cool because you might not have the email address or in the region there might be a preference or in the region you’re sending to the users unable to receive a text message, which is another option, right? The SMS option to send the DSA agreement notification. So, WhatsApp is really there to round up our portfolio of delivery methods and help you really get those agreements signed in whatever use case or region you are trying to.

Good. Now, as we have explored now all around trust and compliance, I’d like to just kick start a little another poll to understand a little bit more about how you are using it today. Just going to share that today. And really, what we’d love to know is how do you authenticate with your designers today? So, give it a shot. This is a multi-signature. In some cases, you might be using different forms. So, we’ll be collecting some insights here from you as we go.

Okay, I’ll let this run while we move forward. And now to our second bucket, protecting sensitive agreements. As I mentioned, there are three big features I wanted to highlight today for protecting sensitive agreements. The first one I’m highlighting here is an enhancement we’ve made in the July release for account sharing. Now, anyone that never heard about account sharing, what that means is a user or a user group can basically share their accounts and their agreements they’re sending and receiving with another user or another group. So, this is especially helpful for collaboration. If you’re thinking about, let’s say, an HR department, that is, and you have three colleagues working through all the HR onboarding documents using Acrobat sign, then really checking on the status of if someone has signed or not can be quite helpful in collaboration. So, this is where account sharing comes in. Now, we’ve done a and managed if users should share all the agreements that are sent or should actually share sent and received. Now, why is that important? This is especially important if you are working in an area where actually the collaboration that’s happening is only on agreements sent. So, if I’m part of the HR department and I’m sending agreements, my colleague Andrea should be able to see what’s the status of that sent agreement. But on the other hand, I might be receiving an agreement that is only for my eyes. Let’s say I’m getting a salary increase and I need to sign that document that’s sent through Acrobat sign. And in theory, Andrea might be able to see that. This is not what I want. This is not what many organizations want. So, this is essentially a little trigger here to prevent that. So, if this is sent on share-on agreements that are sent by my group, things that are received will not be shared in account sharing.

Now, let’s move to the second feature. This is what we call restricted agreement policy. And this takes the problem from a different side because here might be the HR person sending a sensitive document. Again, a salary increase letter. But I want to protect it from my end because I’m not sure what kind of sharing is set up on someone else’s account. This is tough to say. What we’ve added here essentially is a setting. And again, this can be enabled by admins and given the right authority for senders to basically decide if this should be part of account sharing or should actually be restricted. So, how that works is it takes into account this setting and basically protects the sent document from being viewed by another person, account sharing or delegation. So, I have a quick demonstration here just on the sender side to help you understand how that works. So, again, take it from the perspective of the HR person sending a sensitive agreement and sending that to Jonas. And what you’ll see here is there is a new option under the agreement settings, which is called restricted agreement access, which I can enable or disable. And I can do that because the admin allows me to. In some cases, they might be enforcing this. So, it really depends again on your user group, on the use case you’re doing, and how you’re structuring the Acrobat sign account. What makes sense here? But essentially, we’re putting power into the hands of the sender to make sure sensitive documents are not viewed by someone else. Great. Let’s move to the third topic. And this is about enhanced content protection. We’ve released that actually a while back, but I wanted to bring it up because it fits perfectly into that area because it’s also about protecting sensitive content. And what this does, it ensures there is a multi-factor authentication for signed agreements. So, there’s a difference when you set up phone authentication, when you’re sending out an agreement, that authentication is only happening to basically prove that and protect this signature. But what happens to the document afterwards is a whole different matter. So, that’s why content protection here comes into the play to allow you to basically ensure there’s multi-factor authentication for signed agreements if they are accessed and hosted on the Acrobat sign server. So, of course, someone don’t have a PDF and there is no further protection on it, then that will not work. So, this is especially for the use case where you are storing and keeping the documents on Acrobat sign. And what comes out in the end in the completion email is a link to that document that is hosted on the Acrobat sign server. So, in that case, we will challenge the user to authenticate again.

Now, as I understand, these are similar but different features. So, again, here’s a little table just to help you differentiate and see what it means. I went through the benefits, just went through all the different features, but also there is a difference in visibility. So, for restricted agreement policies specifically, the document will not appear in what we call waiting for me, waiting for my signature in the manage tab until it signs and then it will basically move in the completed area. And that’s intentionally. So, users should not be surprised that if they’re looking for a document that they need to sign is not there because that’s just how the feature basically protects the document. Now, a couple of suggestions here for the different features. And I think with that, we’re getting into the Q&A area next. One, for enhanced account sharing, really, from our perspective, enable it by default and disable for groups that collaborate even on agreements received. This is what we think is the best here in this case. For restricted agreement policy, enable by default for users and groups that send sensitive documents to signature HR, legal, and other departments. So, again, it might not be something for everyone, but for the groups that typically send sensitive documents. Enhanced content protection really should be enabled by default if documents are stored in Acrobat Sign. Some companies decide to basically retrieve all the signed documents from our service and delete them. So, in that case, the feature will not help much. Or if the documents are always just attached as a PDF, of course, in that case, the user doesn’t really have a link to that. So, there’s no multi-factor authentication. So, that’s where this feature comes in. So, generally, as we close this area, again, understanding your use case, the sensitivity of documents is key, and then configuring the right feature or maybe even two features to make sure documents are protected in the right way is where we would stand here.

Perfect. With that, let’s jump to our last poll of the day and then go into questions.

And for this poll, we’d really just love to hear from you what the most relevant feature was for you from today’s check. Give it a thought. There were a lot of different factors and areas.

And there’s a second question. Don’t miss it if you click on. That’s a bit of a freeform area. So, we’d love to hear what you’re most excited about in the space of e-signatures.

Is that any kind of regulations? Is it AI? What is it that really gets you excited? What you would love to see coming to Acrobat Sign? You can give us some idea here. That would really help.

Okay, I’ll give everyone a minute here to complete that.

Okay, I’m seeing a lot of entries here for multi-factor authentication, but also digital and cloud signatures.

Yeah, I think we have a pretty good extension. Enhanced account sharing is also a big one for many. It is a very popular feature, so we’ll see. In terms of the most excited space, I think we’re seeing AI as the top one at the moment. There are a couple of other ones. Faster authentication methods, drafting templates, less steps, so a little bit about user experience.

Fantastic. Okay, thank you for that. I’ll let this run. There are a couple of people that haven’t responded yet, but in any case, let’s jump into our Q&A.

So, I’ll be looking at the most upvoted ones and go on to that. So, the first question I have here is about the organization of templates. Here, the ability essentially to create directories for specific templates for X instead of all lists on one page. And this is one that I think is a common one we’re hearing, and thanks for the feedback here. As we think about future development and user experience, this would be a good candidate for us to get into.

I think then we got another one for having a recycle bin for deleted templates in case there was an accidentally deleted template.

So, I think there are ways to quickly recreate the deleted template. So, you can go to the manage page, find an agreement that is based on the template, and then select create template. So, that should help you restore that. I think that has made sense for a couple of ones.

Let me look at another one.

A lot of questions around templates. Let me pick a different one just to change things up a little bit. Here we go. There is a use case around merging documents after they have been signed.

And in fact, what we do after a document is completed is we apply an electronic seal to basically protect the document from any unwanted changes. And that’s the reason why it can’t be merged. So, that’s the answer here. An alternative would be not sealing the document. Again, it depends here a bit on what type of signature you are using. Is it a basic signature, a verified or a digital one? And can that be lifted? So, I think that’s one to explain. Let me go further. Let me share the next one. Is it possible to have dynamic uneditable scroll after document is signed? Example is a field form does not have enough space today. You cannot see anything outside the field.

Yeah, I think that’s one where, of course, number one, you want to make sure there’s enough space for whatever input you’re expecting to be filled in. So, that is a bit of a scroller.

And then the multi-line feature allows really also for a better reflow of the content because users are able to basically enter input in multi-lines and it will also provide more space.

But, of course, whenever there’s so much input that the text field is not able to see it and the kind of size you’re providing, it will create a problem and be not seen past that section. So, we’ll take that feedback in and have a look at it. Maybe there’s something we can do in the future.

All right, one more question here. How do we remove date and time of signature? We just want the signature. Okay, so as Andrea here answered, again, it depends on the signature type, but the signature appearance is generally configurable with different options.

So, I think we would need to understand a little bit more. If our support team cannot help out or professional services team, we can get that, but please utilize those first. Should be able to help you find the right setting. Let me look at another one.

Right, there’s a good one around phone authentication with one-time passcode. Are there any specific requirements to be taken care of from licensing or setup if we’re sending all onto countries? So, essentially, once OTP is set up, we’re supporting it around the world. So, these documents are sent up. There’s just a few countries where I think there are some limitations, but generally this is supported.

Let me see.

Ah, there’s another question around missing the signature block. Here in the new experience, which seems to be the preference for a use case, that is there when you place an e-signal field and you change it to the signature block. We will also make some improvements here in October on authoring to have all the different signature types right on authoring. So, you don’t need to do two steps, but just pick the right type of signature and place it on the document. So, it’s another good update here from Daphna.

All right. I think there was one clarification on PDFA. That should be clear. So, again, this is to avoid any misunderstanding for PDFA. We’re releasing in phases. The first phase was just accepting PDFAs, which in turn would not accept Microsoft Word, but with the conversion of regular PDF and Word files to PDFAs. So, that should not be an issue at all.

Very good.

Find one last one here.

Is it possible to have multiple signers that cannot view the information that does not pertain to them? Yes, there’s a feature called limited document visibility that would do that. It just requires a bit of configuration, but that’s about it. Okay. Just to wrap things up here, I’d love for everyone just to take a minute and help us improve this format of the webinars. We’re planning many more, but to do so perfectly, I’ve just provided a little link to a survey, which we would greatly appreciate if you could fill in and help us pick the next topic, really. We’d love to hear what you’re interested about. I think we got your input around what are you most excited about? So, we’ll be taking that feedback in and look at it, but this survey goes a bit further, so we’d love your feedback on it. You could take a minute or two just to fill it in. That would really help.

Okay.

Looks good. I see there’s still questions coming in. I’m just going to keep picking up until the top of the hour, so we’ll get there.

Here’s a question specifically on how 51ºÚÁϲ»´òìÈ Acro Cloud Sign-In integrates with SAP SuccessFactors recruitment for automating upper-letter signing collaboration. I think this is one we need to take offline. We won’t be able to answer that in the webinar, but there is an integration with SAP SuccessFactors. Work with your account team, first and foremost, or support team. They’ll be able to guide you more and provide some help. I think we can send you also the HelpX link, get you started there to make sure that works and you’ll have some guidance around how it works.

Oh, there’s one interesting question here. I’m required to obtain the same three signatures for all customer agreements. Is there a way to set this up as a default without having to add each name every time? Yeah, one method here is templates. And then, of course, the other one, if you want to go a bit further, would be workflows, actually, custom workflows. If you have the same process, so that would be another one.

Can we get a copy of the training slides for future reference? We will be sharing the recording for everyone. This will be sent automatically from Microsoft Teams webinar. So, you’ll all have that. And we will also be hosting these on our Experience League. Okay, let me see if we had any further questions here.

My colleagues are still busy answering stuff, but I’ll take a look if I can find one more for us here at the top of the hour.

This one is a good one. Is there a possibility to have 51ºÚÁϲ»´òìÈ Sign More flexible to be able to adjust the group of field sizes at the same time, not one by one? There are actually, especially in the new authoring experience, if you haven’t checked this one out, there are a couple of adjustment tools where you can select one or more fields and basically align them on the same lines.

Okay, with that being said, I think we’re at the top of the hour. Again, thank you so much for participating and spending time with us. I hope this was insightful. As always, we have lots more to cover. So, we’re looking forward to the next webinar. Please fill in that survey and we’ll make sure to cover some of the other topics of interest for you in the near future.

Thank you so much. Have a great day.