Back to Docusign.com
Here are some of the latest popular questions that developers asked on Docusign Community in the month of July 2025.
Thread: Is there a way to realign transformed PDF fields based on original PDF alignment?
Summary: The developer is using PDF form field transformation to convert PDF AcroForm fields into Docusign tabs. They’ve noticed that the text in these new tabs is always left-aligned, while some of the tabs on the original PDF were center-aligned. They want to know if it’s possible to realign these new tabs to match the alignment in the original document.
Answer: Docusign eSignature always left-aligns all tabs and fields. Currently, there's no option to change their alignment to right or center, whether they were added manually or transformed. If you want to change where the text in a tab appears, you would need to reposition the tab itself.
Thread: RecipientAuthenticationStatus blank in Legacy data format
Summary: The developer is using Docusign Connect to monitor recipient authentication status. They’re seeing the results they expect when the recipient is required to authenticate with knowledge-based authentication (KBA), but when the recipient uses SMS authentication, the response is an empty object.
Answer: This is happening because the developer is using the legacy Connect model, which doesn’t support SMS authentication. They will need to create a new Connect configuration and choose REST v2.1: JSON as the event format. After they’ve done this, they’ll receive a message like the following when SMS authentication is used:
{
"recipientAuthenticationStatus": {
"smsAuthResult": {
"status": "Passed",
"eventTimestamp": "2025-07-02T02:53:01.42Z"
}
}
The good news is that Connect configurations can work in parallel, so the developer can use a new configuration alongside their legacy configuration if they prefer to do so.
Thread: Docusign JWT OAuth Consent: Is it Permanent or Does it Expire?
Summary: The developer is implementing JSON Web Token (JWT) Grant authentication. They are obtaining consent and they want to know whether consent is valid indefinitely, or if they will need to grant consent again when the token expires.
Answer: User consent is independent of token expiration, and after it is granted once, it will not need to be granted again. Although you will need to refresh the JWT periodically, you will not need to ask for consent again at that time.