Chaos in Teams and SharePoint? How to restore order

Teams and SharePoint are designed so that anyone can create a team with just a few clicks, which is precisely why, after one or two years of operation, companies discover they have dozens of teams without a clear owner, files scattered in places where no one looks for them, and sharing links where no one knows who has access. For the company, this means a double risk: time is lost searching for the correct file version among copies and attachments, and at the same time, no one can reliably state who currently has access to sensitive data and why.

How Chaos Typically Arises

No one sets it up intentionally. It develops gradually. A project team creates a Teams group for a single job and no one deletes it once the job is finished. Another team handles similar work in their own, parallel team because they are unaware that something similar already exists. Files that should be in SharePoint are sent as email attachments because sending an attachment is faster than finding the correct link. And when an exception to permissions is set up for "this folder only", a year later no one knows why it is there or whether it can be removed.

A structure that pays off

It works best when each team has a clear owner responsible for who is inside and whether the team is still active, and when teams are created following a simple naming convention rather than randomly. A few principles worth implementing from the start:

• Naming conventions (e.g., department-project-year) instead of random names.
• Template for a new team with pre-prepared channel and library structure.
• A clear owner for each team, not just a founder who will forget about it in a year.
• Approval step when setting up a new team to avoid duplicates.

Rights: why avoid tailor-made exceptions

The easiest pitfall is setting permissions tailored to individual folders and files: "this folder only for accountants", "this document only for management". It sounds logical for a single file, but after dozens of such exceptions, no one knows who can actually see what, and access inspection becomes practically impossible. It works better to stick to levels across the entire website or library, owners, members, visitors, and separate sensitive items into a separate website with a clearly defined group of people, not as an exception within a shared structure. The fewer exceptions the environment has, the faster it can be verified at any time who can actually see what.

External sharing under control

A "anyone with the link" sharing option is the fastest way to share files, but also the hardest to control, as it can be forwarded without restriction. It is safer to share with specific individuals by email, set an expiry date for links (e.g., 30 days), and use sensitivity labels for more sensitive documents to restrict what can be done with the file after sending, such as blocking download or print. External sharing should be reviewed periodically to check what remains active and whether it is still necessary.

Guests and external collaboration in Teams

Inviting an external partner or client directly into Teams is more convenient than endlessly forwarding attachments, but guest access must be controlled just like any other access. Guests should have access only to a specific channel or team, not the entire environment, and their membership should be checked during regular inspections along with other accesses, external collaboration often has a clear end because the job will eventually finish, but access does not automatically end with it.

Lifecycle management, not just setup

A team or website that has not been accessed for a year should be archived rather than remaining with the same access rights as active projects. Regular, for example, semi-annual, inspections of who has access to what and whether a given team still exists keep the environment clear in the long term and save the work that would otherwise be required for retrospective cleanup after years of neglect. This discipline goes hand in hand with how a company handles employee departures and who generally has access to what Order in one area will not last long without order in the other.