Contracts belong in SharePoint, so that is where they go.
Approved and signed contracts are filed into your own document library, organised by counterparty and document type. Where legal looks, where retention applies, where they will still be in five years.
AeroSpark writes contracts to SharePoint rather than holding them hostage.
If your company runs on Microsoft, that is where legal looks, where retention policies apply, and where the document will still be in five years.
What gets filed
per counterparty, per document typeAs submitted
The document exactly as it arrived.
AI-marked-up
If one was produced for a negotiation draft.
The approved final
The version a person actually signed off.
The executed copy
Added once it is signed, so the library matches reality.
It fits the Microsoft way of working. The marked-up document is a normal DOCX with real tracked changes, so a reviewer can open it straight from SharePoint in Word Online, make edits, and version history behaves exactly as it does for every other document. No proprietary viewer in the middle.
Setup and everyday running use different permissions
Broad access, briefly
Azure will prompt an administrator for full control across SharePoint sites. That is what Microsoft requires to list your sites so you can choose one and grant AeroSpark rights on it.
The token is the administrator's own, lives in memory for the length of the setup session, is never written to disk, and is discarded as soon as you save.
Narrow access, permanently
After setup, AeroSpark holds Sites.Selected: access to the one site you granted, and nothing else in your tenant.
That is the permission every upload actually uses.
If the broad setup prompt is not acceptable to your administrator, Google Drive works the same way without it, and so does plain email submission.
Setting it up
An administrator connects SharePoint through Microsoft Graph from the admin menu and picks the target site and library.
Folder names are sanitised on the way in. Counterparty names routinely contain characters SharePoint rejects, and a filing step that fails on a trailing period is not much use.