The eSignature docs describe starting from a PDF that already sits in a library and writing the executed PDF back to that folder only after every recipient has signed. Limiting the feature to one site matched the library where agreements are already kept. SharePoint itself was not called or configured in this session.
- What worked
- The library-in, library-out behavior and site-scoped enablement were straightforward to map onto the existing agreement files.