Strategy decks and project plans that live in OneDrive carry context the plan never sees. Vindaris summarizes the documents in a folder you connect and uses them to inform the risk narratives and reviews for the goal and everything aligned under it.
A goal usually has a document behind it somewhere, a strategy deck, a one-pager, a planning doc, and that document is where the intent lives. Vindaris reads the folder you bind so that intent reaches the goal instead of sitting in a drive nobody opens during a review.
You bind a specific OneDrive folder to a goal, project or strategy. Vindaris reads that folder and nothing else, so personal files stay out of scope.
Each document is reduced to a short summary of what it defines or decides. The summary is what informs the plan, so the file content is never copied into Vindaris wholesale.
A folder bound to a goal informs that goal and everything aligned under it, the same inheritance a bound Slack channel follows, so projects and tasks beneath inherit the document context.
A scheduled job re-reads the folder each day. A document that changes is re-summarized; one that is removed drops out of the context on the next pass.
The connection requests file read permission only. Vindaris never writes to, moves, or changes a document in your OneDrive.
OneDrive uses a consent separate from SharePoint and Excel, so the connections stay independent and one cannot disturb another.
The setup exists to put a document's intent in front of the goal it belongs to, so it is deliberately short.
Authorize read access to your OneDrive files. The consent is scoped to file reads and nothing more.
Browse your personal OneDrive and drop the folder onto the goal, project or strategy it belongs to.
Each file in the folder is read once and reduced to a short summary of what it defines, which becomes context on the bound item.
The daily job keeps the summaries fresh, so a changed plan reaches the review instead of a version from three quarters ago.
Binding happens on the canvas, next to the goal itself, so the document context sits where the strategy is mapped rather than in a separate settings screen.

When Vindaris explains why a goal is at risk, the summary of the bound document is part of what it reasons over, so the narrative reflects what the goal was actually meant to do.

Someone wrote the strategy deck. Someone drafted the one-pager that set the target and the scope. The work starts, the quarter moves, and that document goes quiet in a drive while the goal is reviewed on its status field alone, with none of the reasoning that produced it in the room.
Binding the folder keeps that reasoning attached to the goal without asking anyone to re-paste it. The summary travels down the alignment to the projects and tasks beneath, it refreshes when the document changes, and when Vindaris judges the goal at risk it can weigh what the goal was meant to achieve rather than the number alone.
No. You bind one folder at a time to a plan item, and Vindaris reads only the folders you bind. Everything else in your OneDrive stays out of scope.
No. Each file is reduced to a short summary of what it defines or decides, and that summary is what informs the plan. The full file content is not copied in wholesale.
They share the same engine and both feed document context. OneDrive reads folders in your personal drive, while SharePoint reads document libraries on shared team sites. You connect whichever holds the documents behind your goals.
No. The connection requests read access only, so no document is written, moved, renamed, or deleted. It is a one-way read for context.
Connect OneDrive in a couple of minutes. Free forever for goal management, two integrations included.
Connect OneDrive freeNo credit card | No migration | Nobody leaves OneDrive