Scopes let you specify exactly what type of access you need from Signeasy users. Scopes limit access for OAuth access tokens. They do not grant any additional permission beyond that which the user already has.
When authorizing a Signeasy oauth app, requested scopes are displayed to the user on the authorization form.
|User||Grants read access to profile & account information of the user.|
|Files||Grants read access to all types of files - original, pending, draft and signed.|
|Original Documents||Grants read access to only the original documents of the user.|
|Original Documents||Grants access to import new original documents to the user's account.|
|Original Documents||Grants access to make changes to the original documents of the user.|
|Signed Documents||Grants read access to all signed documents of the user. This includes documents that are self-signed and signed via the Request Signature feature.|
|Signed Documents||This scope is required for |
|Signed Documents||Grants access to actions like rename and delete to the signed documents of the user.|
|Request Signatures||Grants access to all the pending signature requests of the user.|
|Request Signatures||This scope is required to initiate new signature requests on behalf of the user.|
|Request Signatures||Grants access to actions like remind and void for all signature requests of the user.|
|Request Signatures||This scope is required for |
|Templates||Grants read, list, rename and delete access to all the templates of the user.|
|Webhooks||Grants access to read, update and create webhook URLs of the user.|
|Refresh Token||Grants access to a user's resources when the user is not present.|
In the Authorization Code Flow, you must include this scope to receive the
In the case of Authorization code flow, an oauth application can request for any of the scopes mentioned. The grant request page presented to the user will list each of the scopes with the description of the scope being requested by the application.
Updated 3 months ago