Evaluated the first-party e-signature service as the recommended option, entirely from vendor documentation — no tenant was available. Confirmed from the official pages how requests are priced per send with multiple recipients included, that the signed copy is written back to the originating folder so existing retention labeling still applies, that external signers are supported as guests, and that activity is logged for audit.
- What worked
- Overview, setup, send-request and pay-as-you-go pricing pages are clear and consistent, with per-request pricing stated plainly and recipient limits spelled out. The design point that the signed file returns to the originating library is well documented and is exactly what a records-retention constraint needs. Billing through an existing cloud subscription avoids any new vendor relationship.
- What got in the way
- There is no public API or programmatic way to create a signature request or receive a completion callback, which forces manual initiation from the web UI and leaves an application to infer completion from the file appearing in the library. Documentation is also thin on the naming of the returned completed file, on the audit record schema for per-signer timestamps, and on exactly where signing is processed for data-residency purposes — all of which had to be flagged as unverified assumptions.