Loading page
SharePoint Document Filing
by TechnoVision · Odoo App
Attachments land in SharePoint. Your filestore stops growing.
Odoo puts every attachment in its filestore, which is fine until it is not: the backup takes an hour, the disk fills up, and the documents your business cares about sit in a directory nobody can browse, search or share without going through Odoo. Meanwhile your company already has a document system.
One-off licence per Odoo instance. The store bills in its own base currency, so checkout may differ by a few cents.
- Odoo 18
- Community & Enterprise
- Depends on base only
- Version 18.0.1.0.1 · 2026-09-07
Security Center
Live82
Score
1.2k
Events / 24h
3
Alerts
Export volume · 14 days
Unusual export detected
res.partner · 4,812 rows · outside business hours
Illustrative UI. Product screenshots to be dropped into this frame.
What it does
Filed automatically, and never the only copy
Filed as they arrive
One rule per model, with a folder template - Odoo/{model}/{year}/{record} - so a contract can be found a year later by somebody who knows nothing about Odoo.
Asynchronous, deliberately
Calling Microsoft while saving a record would mean saving an invoice fails when SharePoint is slow. Files are queued and a scheduled job sends them.
Reclaims the filestore, carefully
The Odoo copy is deleted only when Microsoft has returned an item id and a link - never on a call that merely did not error. Off by default.
A log of everything that left
The file, the record, who attached it, the folder, the link, the size, the error if there was one, and whether the Odoo copy still exists.
Nothing filed on install
No rule, no filing. A module that started shipping a customer’s documents to a third party on the strength of being installed would be an accident.
Try it with no app registration
The simulated transport records exactly which files would be sent and where each would land, and sends nothing. Evaluate it before asking IT for anything.
Screenshots
Product gallery
4 captures of the shipped product: where every document went, a filing rule, one filing, the tenant.
Where every document went
A filing rule
One filing
The tenant
How it works
Installed in minutes, useful the same day
- 1
Install and stay simulated
Set up your rules against the simulated transport and look at what would be sent.
- 2
Register an app in Entra
Files.ReadWrite.All or Sites.ReadWrite.All, admin-consented. Client credentials, so the nightly job does not need anybody signed in.
- 3
Pick a library
Odoo asks Microsoft which libraries the app can see, so nobody has to go and find a drive id.
- 4
Watch the log
Every filing, with the folder it landed in. Turn on copy removal per rule once you trust it.
FAQ
Questions we get asked
Only if you tick Remove the Odoo copy, per rule, and only after Microsoft confirms the file with an item id and a link. It is off by default.
Nothing visible. Files stay queued and the next run of the scheduled job sends them. Nobody saving a record ever waits on Microsoft.
No. It files documents into SharePoint. Changes made there do not come back.
Graph requires an upload session above that size, which is a different protocol. A truncated file in a document system is worse than a refused one, so it is refused with an explanation.
Get SharePoint Document Filing
Install from Odoo Apps, or talk to us about a guided rollout across multiple companies.