Remote SupportSharePoint Information Architecture for Australian SMBs
Site structure that scales, permission models that work, and the common mistakes that turn SharePoint into a digital landfill. Built for Australian businesses between 20 and 250 staff.
Why information architecture matters
Most Australian SMBs we encounter have SharePoint set up like a shared drive from 2010. One big "Documents" library, no structure, permissions inherited from whoever created the site originally, and search that returns 847 versions of the same policy document.
Information architecture is not about making things look pretty. It is about how your staff find content, who can access what, and whether your SharePoint environment survives staff turnover without becoming a security risk.
Get it right and SharePoint becomes your single source of truth. Get it wrong and you have a digital landfill that staff work around using personal USB drives and unsecured email attachments.
Recommended site structure for SMBs
Modern SharePoint prefers flat hub sites over deep subsite hierarchies. This structure works for Australian businesses between 20 and 250 staff.
Company-wide hub (Intranet)
Communication site for policies, announcements, and company-wide resources.
Department sites (one per function)
Team sites for Finance, Operations, Sales, HR, IT. Each department owns their content.
Project sites (temporary or ongoing)
Cross-functional projects, client engagements, or time-bound initiatives.
Naming conventions that work
Permission models for Australian SMBs
Four roles cover 95 percent of scenarios. Keep it simple, document it, and review quarterly.
| Role | Access Level | Who | Responsibilities |
|---|---|---|---|
| Site Owner | Full control | 1-2 senior staff or IT manager |
|
| Site Member | Edit and contribute | Department team members |
|
| Site Visitor | Read only | Broader organisation or external parties |
|
| External Guest | Limited, time-bound | Contractors, clients, vendors |
|
External sharing controls
Australian businesses under the Privacy Act must control external sharing carefully. Set SharePoint external sharing to "Existing guests only" or "New and existing guests" with approval required. Never use "Anyone with the link" for business documents. Review external guest access quarterly and remove stale accounts.
Six mistakes that break SharePoint
We see these repeatedly in Australian SMBs. Each one is fixable but prevention is easier than cleanup.
Flat structure with no hierarchy
One massive "Documents" library with 10,000+ files. Search becomes useless, permissions are unmanageable, and nobody can find anything.
Too many subsites
Deep nesting of subsites creates navigation nightmares and broken permission inheritance. Modern SharePoint prefers flat hub sites.
Breaking permission inheritance everywhere
Unique permissions on every folder means nobody knows who can access what. Audit becomes impossible.
Using personal OneDrive for business files
Files leave with the employee. No version control, no collaboration, no backup. Common in Australian SMBs.
No naming conventions
"Final v2 UPDATED.docx" syndrome. Version history exists but nobody uses it because files are named inconsistently.
Syncing everything to desktop
OneDrive sync client set to mirror entire libraries. Local drives fill up, sync conflicts multiply, performance tanks.