With custom permissions, you can now set precise access levels for each of your team members or admins. In addition to the previous permissions of viewing metadata, editing, and deleting documents, you can now also grant permissions for downloading documents, downloading audit trails, and viewing documents.
You can now specify a preferred language for all communication, including email and the application’s user interface. In addition to the previously supported languages of English, Spanish, French, German, and Romanian, we’ve added 9 new languages: Bulgarian, Italian, Danish, Polish, Portuguese, Czech, Dutch, Swedish, and Russian.
Now, you can customize the user interface contents of embedded document creation, embedded template creation, and editing embedded templates to display in any one of the following languages: English, German, Spanish, Norwegian, and French. This allows you to match the language of your application and provide a seamless experience for your users when creating and editing documents or templates.
Support to send API signature requests on behalf of another user who doesn’t have a BoldSign account by creating and verifying the sender identities was provided earlier, and it was in beta. Now it is marked as stable.
Two-step authentication support is added now while signing in to your BoldSign account. 2FA is a security method that requires two different forms of authentication to verify the identity of the user. BoldSign supports the authenticator app, text messaging, and recovery email as additional authentication methods. An option is also provided to enforce this authentication to your users.
Learn more about two-factor authentication.
The edit embedded template API allows the users to edit the existing templates on your pages using an iFrame, popup window, or a new tab.
Support has been added for hyperlink, image, and attachment form fields in text tag creation now. API users can use text tags in the document’s content. BoldSign will then automatically add the necessary fields when the document is uploaded for signing.
Now, the conditional logic rule can be applied to the dropdown form field. Previously it was provided for checkbox and radio button form fields. The user can create a conditional rule that decides which form fields should display dynamically based on the selected dropdown option while the signer is signing the document.
You can specify a preferred language for signers and then all communication like email and application’s user interface text will be displayed in that language. Currently, you can choose between English, Spanish, French, German, Romanian, and Norwegian. More languages will be added soon.
It is now possible for the signer to change the language of the signer page. The signer can choose between English, Spanish, French, German, Romanian, and Norwegian languages.
Now you can reorder the options of the dropdown form field in the configure fields page.
Learn more about the dropdown field.
The data sync support is provided for Image, Checkbox, Editable Date, and Dropdown fields now. Your signers will be able to enter data into a field once, and then the data will be automatically synced to all the linked fields.
Learn more about data sync support.
Users can now add default values for textbox, image, checkbox, radio buttons, and editable date fields. Also, it can be marked as a read-only field.
It is now possible to locate the specified text from the document and automatically place the selected form field in all the occurrences of that text. It helps the users from dragging and dropping the same field multiple times and positioning it.
Now, the user can create a conditional rule that decides which form field should display dynamically based on the selected checkbox or radio button while the signer is signing the document.
Starter plan users can now create two API keys for only sandbox mode to authenticate BoldSign’s API services.
Now, you can set the expiry date of the document in days, hours, or a specific date and time value.
Learn more about expiry date.
BoldSign now generates signatures using SHA-256 hash-based message authentication code (HMAC) and includes them in the event headers. The authenticity of the webhook events can now be confirmed as being sent by BoldSign and not by an unauthorized party.
You can now enable the sliding expiration mode when configuring OAuth Apps. With the use of a refresh token with sliding, you can obtain a new access token and extend the expiry by another 30 days as long as your current refresh token has not expired.
Learn more about dropdown form field.
You can now embed the template creation process within your application using our Template creation API. Your app users will now be able to upload a document and then add the required form fields within your app itself.
It is now possible to download attachments using the API.
Learn more about syncing form fields.
Now you can get the labels and tag details in the webhook event data.
You can now extend the expiry date of the document using API.
Now, you have the choice of sending finished documents to recipients as an email attachment or as a link in the email. This can be configured from the branding page.
Sender identity webhook’s JSON payload is now improved to get both document and sender identity payload in same object.
Learn more about adding branding in audit trail document.
It is now possible to merge multiple templates and send the combined document for signature. This will greatly help with reducing the number of templates that need to be created separately. A common use case would be for sending our real estate contracts.
Learn more about merge templates.
Click here to sign up for a free BoldSign account on the European data center.
We can now automatically detect form fields present in your PDF document, and place corresponding BoldSign form fields. This feature saves a lot of time when compared to manually creating the equivalent BoldSign form fields.
Learn more about auto-detect form fields.
An example of usage would be a HR SAAS software company integrating BoldSign’s APIs. Now, all the HR company’s customers would be able to send contracts out for signature under their own identity. This is a unique feature that is not offered by any other vendor on the market.
Learn more about sending document with hyperlink field.
Learn more about adding authentication and removing authentication.
Learn more about sending signature request with editable date field.
Learn more about setting different time zone.
It is now possible to create and manage multiple brands using API.
Now, you can categorize documents by using tags via API. Tags can also be used for logical partitioning; you can label each sent document with your tenant IDs or any unique ID to make it easy to fetch or list documents based on tenants or users.
BoldSign API now allows you to create or invite new users, update the user details, resend, or cancel the invitation, list the user, and get details of the user.
BoldSign API now allows you to create, update, list and delete teams in your organization.
BoldSign user can now use the Noto sans font for all the text-based fields like label, text box, date field etc.
Changing recipient for an already sent document is now available. Please note that change is only possible as long as no one has signed the document.
Now, the European date format like “dd.MM.yyyy” are available.
Learn more about customizing the date format.
Now, you can use tags to organize your documents. It is even possible to add multiple tags to a single document.
Learn more about organizing and managing documents using tags.
BoldSign now provides support for sending signature request emails and other workflow emails from your own sub-domain.
Learn more about configuring custom email domain.
Now, signers having an option to sign once in a document and have that signature appear in all the signature fields. This is applicable to both signature and initial fields.
This option can be enabled for you signer from the business profile settings page.
Learn more about changing recipient after sending.
Users can now use Single Sign-On access to log in to the BoldSign account. You may create new users and implement safe access control for all your corporate applications using single sign-on.
Learn more about configuring Single Sign-On.
Now, administrators can quickly invite multiple users by importing the users list from a CSV file. This can be configured from the users page.
Now, you can import all your contacts into BoldSign account from a CSV file. This can be configured from the contacts page.
Learn more about importing bulk contacts.
Learn more about requesting images from your signers.
Now, the developers can track webhook request status and resolve any possible webhook failures.
Now, the sender can decide to split or combine the audit trail and signed document. This can be configured from the branding page.
Learn more about combining the signed and audit trail documents.
Learn more about cloning a template.
Learn more about requesting attachment from your signer.
Learn more about changing account email address.
Now, you can send the document to signing group, and anyone in the group can open and sign the document. Signing groups can be created from the user’s section.
Now, you can make the signer agree to your own legal terms along with BoldSign legal terms before signing the document This can be configured in the branding page.
Learn more about custom legal terms and how to configure it.
It is now possible to specify if a signer can delegate signing to others.
API users can now configure to listen to account level webhooks. This can be configured from the API webhooks page.
It is now possible to transfer documents to another user before deleting a user from BoldSign.
Learn more about extending the eSignature document’s expiration date.
API users can now upload a document using public document URL.
API users can now embed the entire document sending workflow into your application.
Now, users can hide the document ID shown on the signer page and the signed PDF document. This can be configured in the business profile page.
Learn more about hiding the document ID.