Skip to main content
C
carminem0002
November 23, 2025
Question

Docusign embedded sign and code grant authorization

  • November 23, 2025
  • 3 replies
  • 0 views

We are trying to integrate with docusign embedded component in appian. 

I used a code grant authorization with a connected system, with a single user. 

When the token is not valid i go to the connected system and click on authorize.

And like that i can even sign embedded in appian or with the url generated.

The problem is that we have a requirements to provide signing with docusign for two distincted users,

That user are not administrator or designer(like me) so cant click the authorize button everytime.

And i see that in the connected system are not a user reference to pass. 

So how can i authorize two different user with codegrant?

I have to use two different connected system with a different secret keys?

Use an a!authorizationLink?

3 replies

davidj137213
davidj137213
November 24, 2025

In Appian, you can use OAuth 2.0 Authorization Code Grant to authenticate on behalf of individual users.


The access token represents the logged-in user, not just the application.

Appian tracks users through its own platform login, but each user must authorize the integration at least once.

You configure a Connected System in Appian with OAuth 2.0 using Authorization Code Grant.
This includes setting the authorization URL, token URL, client ID/secret, and required scopes.

Appian can store user-scoped tokens (access and refresh tokens) for each individual user.
When a user calls the integration, Appian checks for a valid token first.
If none exists, the user is redirected to the OAuth provider to login and consent.

After authorization, Appian exchanges the code for tokens and stores them for that user.
This allows integrations to execute API calls in the context of each specific user rather than a shared service account.


Regards

    J
    jessek855119
    November 25, 2025

    Fundamentally, if you use OAuth 2.0 Authorization Code Grant for 2 different users to do something with a document in Docusign, each user must have the appropriate permissions in Docusign to be able to execute whatever it is (create envelopes, documents, signing, etc).

    An Appian user does not have to have an elevated permission in Appian (Admin / designer / etc) in order to fulfill the requirements for Authorization Code Grant's use, but the user does need "View" permission on the relevant Connected System object(s). It does appear that a!authorizationLink() is the correct method to allow the code grant authorization to happen under specific conditions, but doesn't always need to appear. 

    Docusign will usually provide a sandbox environment so you can test this out yourself in lower environments if you get in touch with your Docusign account rep.

      C
      carminem0002Author
      November 25, 2025

      In the end, I approached a similar solution using OAuth 2 and an authorization link. I have a list of attachments and need to allow either single or bulk signing, embedded. Which approach would you use? Once the token is obtained through the authorization link, would you use a dedicated process for signing (with the issue of potentially closing the task), or would you do everything in the interface without dedicated processes, except for those that handle the creation and sending of the envelope and then retrieve the signing link to use in the interface?

      Terms & ConditionsAccessibility statement