The proposal is in a Teams chat. The pricing sheet is on somebody’s OneDrive. The approved version is attached to an email, and three people are editing different copies.
This is usually an ownership problem before it is a storage problem. A simple rule about where working files belong can save a great deal of confusion.
Start with the lifetime of the information
Ask who should own the file and who will need it six months from now. If it supports an ongoing department or project, it should not depend on one employee remembering to share a personal working folder.
Use these starting points:
- Individual working material: a person’s OneDrive, with deliberate sharing where needed.
- Shared department or project records: an appropriately configured SharePoint library.
- Team discussion around shared work: Teams channels connected to the underlying files.
OneDrive can support collaboration. The reason to move enduring team records into shared storage is to make their ownership and access easier to manage.
Understand what Teams stores where
Teams is a collaboration interface that uses other Microsoft services for file storage. Channel files are stored in SharePoint; files uploaded to chats are stored in the uploader’s OneDrive and shared with participants. See Microsoft’s explanation of file storage in Teams.
Standard channels use the team’s parent SharePoint site. Private and shared channels have separate SharePoint sites, so access and information management need to account for that structure. Read about Teams and SharePoint integration.
This is why a file appearing in Teams does not automatically mean it has the same ownership or permissions as every other file in that team.
Define a few everyday scenarios
An employee drafting an early idea can start in OneDrive. Once the draft becomes a shared project deliverable, place it in the agreed project library and circulate the link.
A department procedure should live in the department’s shared location, with a named owner responsible for keeping it current. A client document needs an approved sharing location and an explicit decision about who outside the organisation can access it.
These are operating conventions, not rigid product limitations. Adapt them to the team’s work, then write them down in plain language.
Share links with the right audience
Where practical, circulate a link to the agreed file instead of attaching another copy. Before sending, confirm who can access the link and whether recipients should view or edit.
Avoid solving access problems by continually widening permissions. If a colleague cannot open a document, investigate the intended membership and sharing settings.
Give external access an owner and review point. A collaboration that was useful last year may no longer justify access today.
Clean up gradually
Choose one department or project as a pilot. Inventory important files, identify the authoritative versions, and agree the destination structure with the people doing the work.
Test permissions and key workflows before moving large volumes. Existing links, integrations, and synchronisation behaviour may need attention, so agree a migration method and communicate the change.
Archive or remove duplicates only after ownership, retention, and recovery needs have been checked.
Make handovers routine
Assign primary and backup owners to shared workspaces. Review access when people join, change roles, or leave. Include ownership of OneDrive working material in the offboarding process.
Measure success with practical questions: can a new employee find the current procedure, can a colleague cover an absence, and does the project team know which document is approved?
Guava’s Microsoft product collection is a starting point for equipping your team. Explore the available products, then pair the tools with a clear approach to ownership and collaboration.
Cover illustration: Creative Minds Factory / Unsplash.
