Repository navigation
Agreement Management
Open Agreements to prepare documents and track work already sent. An agreement contains its content, recipient configuration, fields, status, and history.
| Starting point | Steps | Best suited to |
|---|---|---|
| Existing file | Choose Upload agreement, enter the title, select the file, add tags if needed, and save | Documents already prepared in another tool |
| New document | Choose Create agreement, write Markdown, check the preview, and save | Simple text agreements created in the browser |
| Template | Choose a template you can use, enter agreement details, and create the draft | Repeated document layouts |
Agreement titles are 2–255 characters. Descriptions can contain up to 1,000 characters. Markdown content is limited to 512 KB; agreement file uploads to 15 MB. The API validator accepts PDF, Word MIME types, Markdown, and plain text; the browser upload flow is oriented around PDF, DOCX, and Markdown. A type appearing in a filter does not guarantee it supports the same editor or sealing features as PDF.
Unlock password-protected files before uploading. Check the preview after any conversion. Keep the original source file if your organization requires it.
- Open an editable draft.
- Update its title, description, or document content.
- Add tags for discovery, such as
salesorrenewal. - Save and confirm your changes before requesting review or sending.
Tags are labels used to find agreements. Metadata is additional structured information attached to a record; integrations may store a folder label in metadata.folder. A folder label in metadata is not a separate filesystem directory.
Content editing is governed by status. Do not assume that a sent or completed agreement can be revised in place. If terms need changing, create an appropriate new draft and follow your organization's approval process.
- Select the relevant Agreements tab, including drafts, review work, or archived records.
- Enter a search term.
- Use advanced filters to narrow the results by the available date, file type, tag, author, or recipient options.
- Choose a sort order, such as date created or title.
- Save a filter preset if you often repeat the same search. Apply or remove presets through the filter controls.
If a record seems missing, clear filters and check the archived view and active workspace. Search results are limited by your access.
- History shows recorded document changes and workflow activity.
- Versions preserve the application's version records. A displayed version identifies a revision; it is not the same thing as a digital signature.
- Clone creates a separate agreement. Review the new copy's content, recipients, and fields before sending it.
Archive removes a record from ordinary active views while keeping it available in the archived view. Use Unarchive to return it. Deletion is a different action, controlled by your permissions and document state. Use archive when you only want to tidy your working list; check retention requirements before deleting records.
Use the agreement's download action. For completed agreements, the server prefers the saved signed or sealed PDF when available. A completed state does not by itself prove that a usable sealed PDF was generated. Open the downloaded file and verify it. The original filename or a .pdf extension alone is not proof of signing.
Platform administration does not automatically grant access to private agreement files; the file route specifically restricts the platform super-administrator role to metadata.
Next: Document Editor and Fields · Workflow Engine and Signer Portal.
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