Repository navigation
Send Your First Agreement
This walkthrough is for the person preparing and sending a document. Use a harmless sample document for your first practice run. Sending an invitation starts a real workflow and can notify recipients.
- Sign in and open Agreements.
- Choose Upload agreement for an existing file, Create agreement to write a document, or the template option to reuse a published template.
- Give the agreement a clear title, such as “Service agreement — October”. Add a description and useful tags if appropriate.
- For an upload, select your file and save it. For a new document, write the Markdown content and check the preview before saving.
The agreement upload validator limits files to 15 MB. The upload flow supports PDF, Word, and Markdown; convert Word files to PDF when you need predictable page placement. Password-protected documents must be unlocked before upload. See Agreement Management.
Expected result: a draft appears in Agreements. Saving a draft does not send it to anyone.
- Open the draft's document editor.
- Add the people who will complete the document. Use their names and check their email addresses carefully.
- Select a recipient, then place that person's signature field on the document.
- Add any required initials, dates, text, or choices. Assign every field to the correct recipient.
- Mark fields required where they must be completed. Configure choice options and validation where needed.
- Save the document fields. Reopen the draft and check the layout, assignment, and page placement.
Expected result: each signer has the fields they need. See Document Editor and Fields.
- Choose Submit for Review on an eligible draft.
- Select the intended reviewer and add a brief note explaining what needs checking.
- Submit the request and wait for the review decision.
- If rejected, read the comments, update the draft, and submit it again.
Review is a separate step from a recipient signing. Your role and workflow determine whether review is required or available.
- Choose the send action on an eligible agreement.
- Check the recipient list and field assignments.
- Choose Parallel if signers can act independently, or Sequential if they must act in order. For sequential routing, set the intended order.
- Set an expiry date if needed and add an optional message.
- Confirm the send action.
Expected result: the agreement moves into its sent workflow and recipients receive their invitations, subject to the deployment's email configuration. Check notification history if someone reports a missing email.
- Return to Agreements and check the status and recipient progress.
- Use a reminder for an outstanding recipient when appropriate.
- When the agreement is completed, download its completed document.
- Check the document's authenticity using its verification link or the public verification page.
- Retain the completed file and supporting records according to your organization's policy.
Completion and successful cryptographic sealing are related but separate facts. If the completed PDF or verification record is unavailable, contact your administrator; see Feature Availability.
Next: Workflow Engine and Signer Portal · Cryptographic Signing and Verification.
Documentation home · Getting started · Troubleshooting · Feature availability
Reviewed 3 October 2026.
graphsign.ink
Using the application
Account and administration
Developer documentation
- API quick start
- REST API reference
- Agreement and workflow API
- Template API
- Account and organization API
- Search API
- Certificates and signing API
- Webhooks and integrations
- Feature availability
Help