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
Both internally and externally-facing versions.
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, and only on one path
Choosing to connect an existing site means Azure prompts your administrator for full control across SharePoint sites. That is what Microsoft requires to list your sites so you can pick 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.
The other two paths skip that prompt entirely: AeroSpark can create a dedicated site of its own, or your admin can grant access to a single site themselves, with no delegated permission ever.
All consent goes to a dedicated AeroSpark SharePoint Connector app. The AeroSpark Teams app itself requests no SharePoint permissions at all, so your organization only ever sees SharePoint prompts if you choose to adopt the integration.
Narrow access, permanently
Every path ends in the same place. AeroSpark holds Sites.Selected: write access to the one site connected, and nothing else in your tenant.
That is the permission every upload actually uses.
Strict-security organizations can take the manual path: your admin grants AeroSpark write access to a single site with one PowerShell command, and no delegated permission is ever requested. Google Drive and plain email submission remain alternatives.
Setting it up
An administrator connects SharePoint from the admin menu and picks one of three paths: let AeroSpark create a dedicated contracts site, sign in with Microsoft and pick an existing site and library, or grant access manually with a single PowerShell command.
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.