Developers and automation · Autessa Document Signing
Embedded signing
Embedded signing lets people sign inside an app you build on Autessa. Autessa apps ship a PdfSigner component that renders Autessa’s hosted signer inline: create and send the envelope as usual, resolve a signing token for the current user, and render the component, so the user signs without leaving your app or opening an email.
The problem it solves
Leaving your app to sign breaks the flow
A client portal, an onboarding app or an internal tool that sends people off to their inbox to sign loses them. Embedded signing keeps the whole experience in your product, with the same consent screen, checklist, signature pad and sealed PDF.
What you get
- Render the hosted signer inline with <PdfSigner token={signingToken} onComplete={handleSigned} />.
- The signer sees the same consent screen, field checklist, signature pad and attestation as an emailed signer.
- onComplete lets your app react the moment the signature lands.
- inbox.list powers a “documents awaiting your signature” panel inside your app.
- The App Builder copilot can read your envelopes (list and details) to build screens against real signing data; it cannot create, send or void them.
- Envelopes signed in an app are identical to any other: same audit trail, same sealed PDF.
How it works
Embedded signing, step by step
Create and send
From a script or the API, as usual.
Resolve a token
Get a signing token for the current user.
Render PdfSigner
Drop the component into your app’s page.
React to completion
Use onComplete to move the user on.
Every option
Embedded signing pieces
| Option | What it does |
|---|---|
| PdfSigner | App component that renders the hosted signer. |
| token | The signing token for the current user. |
| onComplete | Callback when signing finishes. |
| inbox.list | Envelopes awaiting the current user’s signature. |
| Copilot tools | Read-only envelope list and details for building screens. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| API key or script | Acts with the access of the person or key it runs as, inside your company only. |
| Template READ | Enough to create envelopes from a shared template from automation. |
| Envelope PUBLISH | Needed to remind, void or mark as executed from code, the same as in the app. |
| Company admin | Controls which roles can use Document Signing at all. |
Connected
How it connects to the rest of Document Signing
FAQ
Embedded signing: questions and answers
Can customers sign inside my own app?
Yes, in apps you build on Autessa. The PdfSigner component renders the hosted signer inline.
Is embedded signing less secure than email?
No. It uses the same signing flow, consent, attestation, audit trail and PAdES sealing.
What does the App Builder copilot do with envelopes?
It reads envelope lists and details so it can build screens on real signing data, and your app’s code does the sending.
100% customizable, code and all
Make Autessa Document Signing fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours