The Strategic Edge of Intranets and Document Management

An intranet and a document management system do different jobs, but in Microsoft 365 they run on the same platform, SharePoint, and they work better when they are planned together. The intranet is where people find news, policies and the way into everything else, and document management is how files are stored, versioned, secured and kept for the right length of time. If people can't find a policy from the intranet, or find three copies of it, both have failed.

What is the difference between an intranet and document management?

An intranet is mostly about communication. It carries company news, announcements, policies, guides and links to the systems people use, and it is read far more than it is edited. In SharePoint it is usually built from communication sites joined together with a hub and a home site.

Document management is about the files people work on every day: contracts, reports, procedures, drawings and so on. In SharePoint that means team sites and document libraries, with permissions, version history, metadata and retention rules applied to them. The two overlap all the time, because a policy published on the intranet is also a controlled document that someone owns and has to review.

Why plan the intranet and document management together?

When they are planned separately you tend to get an intranet full of links to documents that have moved, or been replaced, or that only half the organisation can open. Planning them together means you decide once where each type of content lives, who owns it and how people get to it.

The decisions worth making up front are:

• which documents are published on the intranet and which stay in team sites
• who owns each policy or procedure, and how often it is reviewed
• what metadata you need so search and filtered views work, kept to a few columns people will fill in
• how permissions are set at site level so you aren't managing access file by file
• how long different types of content are kept, and what happens at the end of that period

None of this is complicated, but it is much harder to retrofit once there are thousands of files in the wrong place. Our SharePoint governance work usually starts with exactly these questions.

What document management features does SharePoint include?

SharePoint document libraries come with the features you would expect from a document management system, without a separate product:

• Version history. Every save creates a version you can view or restore. New libraries keep up to 500 major versions by default, and administrators can change that limit or switch to automatic limits that thin out older versions over time to save storage.
• Co-authoring. Several people can edit the same Word, Excel or PowerPoint file at once, which removes the need to email copies around.
• Permissions. Access is controlled at site, library, folder or file level, ideally using groups at site level so it stays manageable.
• Metadata and views. Columns such as document type, owner or review date let people filter and sort rather than relying on folder structures.
• Search. Content across sites is searchable, and results respect permissions, so people only see what they already have access to.

How does SharePoint handle security and compliance?

For organisations with compliance requirements, Microsoft Purview adds controls on top of SharePoint. Sensitivity labels classify documents and can apply encryption, and a document library can be given a default sensitivity label so new files are labelled automatically. Retention policies and labels keep content for a set period and stop it being deleted early. The Microsoft 365 audit log records activity such as labels being applied, changed or removed, which helps when you need to show who did what.

The licensing for these features varies by plan, so check what your Microsoft 365 subscription includes before designing around them. What they give you, used properly, is a defensible way to show that sensitive information is classified, retained and accessed appropriately, which matters under UK GDPR.

How does an intranet help with knowledge management?

A lot of useful knowledge sits in people's heads, in email threads and in documents only one team knows about. An intranet gives that knowledge a home: how-to guides, FAQs, process pages and a people directory so staff can find who knows what. The intranet pages link to the controlled documents behind them, so the guidance and the source document stay in step.

It also makes AI tools more useful. Microsoft Copilot works from the content a person already has access to, so a well organised intranet and document store, with old content removed and permissions tidied up, gives better answers than a tenant full of duplicates and out-of-date files. Our guide to designing an engaging SharePoint intranet covers the communication side in more detail.

Frequently asked questions

Can SharePoint replace a dedicated document management system?

For many organisations, yes. SharePoint includes version history, co-authoring, permissions, metadata, search, and with Microsoft Purview, sensitivity and retention labels. Some regulated sectors need specialist features, such as formal records declaration or industry-specific workflows, so it is worth listing your requirements before deciding.

How many versions does SharePoint keep?

By default, new document libraries keep 500 major versions with no expiry. Administrators can set a count between 100 and 50,000, add an expiry period, or use automatic limits that keep recent versions and thin out older ones.

What does it cost to move documents into SharePoint?

A SharePoint migration from file shares or another platform typically costs between £20,000 and £50,000, depending on the volume of content, how much restructuring is needed and how many sites are involved. See our SharePoint migration services for how we approach it.

Should the intranet and team document sites be separate?

Usually, yes. Communication sites suit published content that many people read, and team sites suit working documents that a smaller group edits. Hubs and navigation join them up so people can move between the two without needing to know where things are stored.

If you are planning an intranet, a document management project or both, get in touch to talk it through, or read more about our intranet services.