Municipal Files in Microsoft 365: Make Sharing Easier to Manage

Start with the official copy

A familiar municipal problem begins with a simple question: which version is the one we should use? A board packet may exist in an email attachment, a staff member’s folder, and a shared drive. Microsoft 365 can help teams collaborate, but moving those copies into the cloud does not decide ownership or working practices. The office still needs an agreed place for the current document.

Choose a small workflow to organize first, such as preparing meeting packets or sharing project documents. Define where drafts live, who approves the final version, and where the approved material is published or stored. Keep the arrangement easy to explain. If staff need a diagram every time they save a file, the structure probably needs simplification.

Give shared work a shared owner

Department work should have an identified municipal owner and a planned location that remains usable when staff change. Ask your IT team which SharePoint or Teams structure fits the workflow and which personal working files belong in OneDrive. The choice should account for the people who need the material and the process used to maintain it.

For example, a clerk’s office may need a shared location for packet preparation with permissions for a small working group. A project team may need a separate area for contractor collaboration. Avoid giving everyone broad access simply because that is quicker to set up. Equally, avoid an elaborate folder tree that nobody can navigate. Agree on a few meaningful boundaries and review them with the people doing the work.

Choose the right kind of sharing link

Microsoft distinguishes links that work for anyone holding them from sharing with specific people. Its documentation also explains that organization-wide sharing settings place limits on what individual sites can allow. Ask your administrator to review those settings and propose sensible defaults for your municipality. The options should reflect the sensitivity of the material and the need to collaborate.

A document prepared with an engineering consultant may need a controlled external invitation. A published public notice belongs in the municipality’s established public publishing workflow. These are different tasks even if both involve the same platform. Teach staff which sharing choice to use for each common scenario and how to confirm who currently has access before sending a link.

Review access when work changes

Permissions deserve a review when a project finishes, a contractor changes, or an employee moves to another role. Identify who owns that review and what record is kept. Microsoft’s access-management guidance explains that access can come from a sharing link, a direct grant, or an inherited folder or site permission. Removing one link does not necessarily remove every route to the file.

Ask your IT team to help the owner check the complete access picture for a representative site. Work through a real example together: who should still see the project folder, who should edit it, and who no longer needs it? This gives staff a repeatable method and exposes situations where the structure is more complicated than anyone intended.

• Name an owner for each shared workspace.
• Define where drafts and approved documents belong.
• Use the approved sharing method for outside collaborators.
• Review all permission routes when staff or projects change.

Keep training tied to an actual task

Show staff how to find the current file, share it appropriately, and check access using a document from their own workflow. Explain what to do when a recipient cannot open it. That is more useful than a long tour of every platform feature. Write down the handful of conventions the team agrees to use, then make them part of onboarding.

Information ownership, retention requirements, and public release decisions remain municipal responsibilities. IT should implement the approved structure and help verify it. Michigan IT services are most useful when the technical configuration matches the way the office works. Start with one document process, make it clear, and use what you learn to organize the next area without disrupting the entire team.