SharePoint for Records & the Modern Workplace
Section outline
-
This session sets the frame for the whole SharePoint day: SharePoint is not a place to dump files, it is the governed content backbone of the modern workplace where your organisation's records now live. It matters because the move to Microsoft 365 changes where your evidence sits and who controls it, and that value only lands when SharePoint is governed rather than left to grow on its own. - The modern workplace is work across devices, locations and teams, with content and conversation joined up in one cloud - Microsoft 365. SharePoint is the content-services layer underneath it. - Every Micro
-
This session is about the hardest step in getting to a governed SharePoint: moving your existing content off file shares, old SharePoint Server farms and personal drives into a destination that is designed, not just filled. The core message is simple - migration is a records event, not a copy job. Every move puts metadata, permissions, version history and retention posture at risk, and a migration is the best chance you will get to clean up, classify and bring records under control. Done badly, it multiplies the sprawl and breaks the audit trail. - **Assess and inventory first.** You cannot pl
-
Now that content lives in a governed SharePoint, the next question is what we can do with it automatically. This session introduces the **Power Platform** - Microsoft's low-code toolset that sits directly on SharePoint lists and libraries and lets non-developers build forms, dashboards and automated workflows. The promise is real: less repetitive work, faster approvals, automatic audit evidence. So is the risk: the same accessibility that empowers the business can spread ungoverned automation, leak data through unsanctioned connectors, and leave critical flows orphaned when their maker leaves.
-
This session is the compliance anchor of the SharePoint day. It turns the broad idea that "SharePoint should be secure" into a concrete set of controls you can point to and defend. Security in Microsoft 365 is not one setting - it is a stack of overlapping layers (identity, permissions, labels, DLP, retention, auditing) that only works when the layers are configured together and mapped to a real legal obligation. The through-line is the link between security and law. Every control in Microsoft Purview and Microsoft Entra ID exists to help meet a duty - most importantly, for South African organ
-
This session is about how modern SharePoint sites are actually built, and why that matters for records. Classic SharePoint pushed deep subsite trees and nested folders. Modern SharePoint is the opposite: flat structures, hubs that connect sites, metadata instead of folders, and search that works. The guiding idea is simple - **site design is records design**, because you can only manage, retain, protect or dispose of content that people can find. Use this handout as a reference when you sit at a site-design table in your own organisation. You do not need to build sites; you need to know enough
-
This closing session draws the whole SharePoint day together through two real South African public-sector records-management implementations, both delivered first-hand by the facilitator as a consultant on behalf of another vendor. The two took opposite routes: the Department of Human Settlements, which built its full file plan into SharePoint and automated around it, and the Gauteng Legislature, which decided a rigid file plan did not fit and used grouping and tagging instead. The point is not which is right, but why each fit its content - and what it cost. You will leave with a 90-day action
-
-
-
-