Works where your projects already live.
AEC firms run on Microsoft 365 — project files in SharePoint and OneDrive. Nudgy connects to that: pick the spec and each drawing revision straight from where they live, instead of exporting and re-uploading.
- Access
- Read-only
- Graph scope
- 1, listed below
- Setup
- Sign in · pick files
- Findings
- In the app
The model
Pick files, not a platform migration
At setup you pick the project spec from OneDrive or SharePoint — indexed once, re-indexed when addenda are issued. Then each drawing revision is picked the same way when it's ready to audit. That is the entire integration surface.
No exporting, no re-uploading
Project files stay where your firm already keeps them. When a revision is ready to audit, pick it from OneDrive or SharePoint inside Nudgy — including across multiple Microsoft accounts, if you work in several clients' tenants. The copy Nudgy reads becomes part of the audit record, so every finding stays traceable to the exact document version.
Setup, honestly described
Sign in with a Microsoft account. Pick the spec. Pick a drawing and run the audit. That is the whole procedure — minutes, not a deployment project. The sign-in token stays in your browser session and expires on its own; Nudgy's servers never store your Microsoft credentials.
Permissions
Read-only, spelled out
This is the section your IT department will read. The Microsoft Graph access Nudgy requests, and what it is for:
Files.Read.All
Lets you browse and pick files when adding a spec or drawing. Nudgy retrieves only the files you select — it never writes, moves, or deletes.
openid · profile
Standard Microsoft sign-in identity for the person connecting the account. Authentication happens on Microsoft's side.
What Nudgy cannot do
- ✕Write to, move, rename, or delete any file
- ✕Retrieve files you haven't explicitly picked
- ✕See user passwords — authentication happens on Microsoft's side
- ✕Share or re-permission anything in your tenant
Microsoft 365 is the supported platform. On the roadmap, clearly labeled as such: watched folders — where each revision saved to a designated folder triggers its audit automatically — and Teams notifications. They ship when they can be supported to the same read-only standard, not before. Other storage platforms follow the same rule.
