A monthly website maintenance checklist for a Dubai business
A monthly website maintenance checklist for a Dubai business: updates, backups, uptime, forms, security, performance and what to do when something breaks.
Read the articleA SharePoint intranet is genuinely good at document libraries with proper permissions and version history, company wide announcements and policy pages, and structured team sites that inherit or break away from a central set of access rules. For a Dubai business already paying for Microsoft 365, a SharePoint intranet is usually the simplest way to get all three in one place, because the platform is already licensed and the permissions model is already built. Where it struggles is anything that needs to look and feel like a modern app, or that needs to be public.
This guide sets out where a SharePoint intranet fits a Dubai business, where it does not, how permissions and document control actually work under the surface, and the mistakes that most often turn a new intranet into a page nobody opens after month two.
Key points
- A SharePoint intranet is strongest at document storage with real permissions, policy and HR content, and company announcements.
- It is a poor fit for a public facing website, a highly custom internal app, or a team that wants a chat first, lightweight tool.
- Permissions inherit down from the top site by default, and any site owner can break that inheritance at the site, library or single item level.
- Document version history is on by default in every library, and major and minor versioning or check out can be switched on for tighter control.
- Most failed SharePoint intranets fail on ownership and structure, not on the software itself.
What a SharePoint intranet does well for a Dubai business
The strongest case for a SharePoint intranet is a business that already runs on Microsoft 365 and needs somewhere for policies, HR forms, departmental documents and company news to live with real access control, rather than scattered across shared drives and email attachments. Because the licence is already in place for most Dubai companies on Microsoft 365, the marginal cost of a well built SharePoint intranet is largely the setup and structure, not new software.
A communication site works well as the front door: news posts, a company directory, links out to the departmental team sites, and a search box that actually finds documents rather than just page titles. Underneath it, team sites give each department its own document libraries, lists and pages, with permissions that can follow the main site or be set independently. This structure suits a Dubai business with several departments and a genuine need to keep HR, finance and legal documents visible only to the right people, while general policies stay open to everyone.
Where SharePoint intranets fall short
A SharePoint intranet is the wrong tool for a public website. It sits behind Microsoft 365 sign in, its templates are built for internal publishing rather than marketing pages or product catalogues, and it has no meaningful presence in public search results. A SharePoint intranet built for a Dubai audience should stay internal, with the public site handled on a platform designed for that job.
It also struggles as a substitute for a purpose built internal application. Out of the box, SharePoint gives lists, libraries, pages and a handful of web parts. That covers document management and basic workflow well, but a business process with complex logic, a real database schema or a need to integrate tightly with another system usually outgrows what a SharePoint site can comfortably do without custom development. And for a small, fast moving team that wants a single chat first workspace rather than a structured library of pages, a SharePoint intranet can feel heavier than what they actually need.
A SharePoint intranet earns its keep on documents and permissions. It is the wrong choice the moment the requirement is “build us an app”.
How permissions actually work in a SharePoint intranet
Permissions in SharePoint start at the top level site and inherit down through subsites, document libraries, folders and individual items, unless someone deliberately breaks that inheritance at a given level. According to Microsoft’s own guidance on permission levels in SharePoint, once a site owner sets unique permissions on a site, library or item, that object stops inheriting from its parent, which is exactly how a Dubai business keeps a general policy library open while locking a finance folder to a handful of people within the same site.
Three default groups do most of the work on a typical team site. Visitors get Read, which allows viewing and downloading without editing. Members get Edit, which covers adding, updating and deleting list items and documents. Owners get Full Control, the only group with the right to manage permissions and site structure themselves. These three default groups are enough for most SharePoint intranet builds a Dubai business runs, and finer grained levels such as Contribute, Design and Approve cover the cases where Edit or Read is either too broad or too narrow.
| Group | Permission level | What it covers |
|---|---|---|
| Visitors | Read | View and download items, no editing |
| Members | Edit | Add, update and delete list items and documents |
| Owners | Full Control | Everything, including managing permissions and site settings |
A sensible permission plan for a Dubai business intranet starts from these three groups and only adds unique permissions where there is a genuine reason, such as an HR or board level document library. Breaking inheritance on every second folder, instead of relying on the default structure, is the fastest way to end up with a permission model nobody fully understands a year later.
Document control: versions, check out and approval
Every document library in a SharePoint intranet keeps version history switched on by default, so a colleague who overwrites a file, or edits it badly, can be rolled back to an earlier saved version rather than the change being permanent. For libraries that need a tighter process, a site owner can turn on major and minor versioning, so a document moves through draft versions before being published as the current version everyone else sees, alongside check out, which stops two people editing the same file at once, and content approval, which requires a named approver to sign off a document before it becomes visible to everyone with Read access.
This matters most for policy documents, contracts and anything where an outdated version circulating by email has caused a real problem before. A properly configured document library removes the “which version is the current one” question almost entirely, because the library itself, not somebody’s inbox, is the single source of truth.
Common SharePoint intranet mistakes
The most common mistake is designing the permission structure and site hierarchy before anyone has actually mapped how the business organises its documents today. That produces a site that mirrors an org chart nobody follows in practice, rather than the way people actually search for and share files.
The second is treating launch as the finish line. A SharePoint intranet with no named owner, no plan for keeping news and policies current, and no review of unused sites after six months drifts back toward email and shared drives within a year, because the intranet stops being the easiest place to find something current. We see this pattern often enough in Dubai businesses that a SharePoint intranet launch plan should name an owner before the first site is built, not after.
The third is over engineering permissions from day one, breaking inheritance across dozens of folders “to be safe” rather than starting from the three default groups and adding unique permissions only where a genuine sensitivity exists. Every broken inheritance point is one more thing someone has to remember to update when a person joins, moves department or leaves.
Map the documents before touching SharePoint
List the document types the business actually holds, who needs to see each one, and who needs to edit it, before opening a single site template.
Start from the default groups
Build the structure around Visitors, Members and Owners, and only break inheritance where there is a specific, named reason.
Switch on the document control features that match the risk
Version history is already on. Add major and minor versioning, check out or approval only for libraries that genuinely need that level of control.
Name an owner before launch
Someone needs to be responsible for keeping the intranet current once it is live, or the same drift back to email and shared drives tends to repeat.
How Digital Marketing Dubai can help
We plan SharePoint intranet structures around how a Dubai business actually organises its documents, rather than a generic template, and our SharePoint development work covers permission planning, document library setup and the custom web parts a communication site needs once it goes beyond the out of the box options. For businesses working more broadly across Microsoft 365, our Microsoft 365 development service covers the wider platform, including integrations between SharePoint and the rest of the Microsoft 365 suite.
If your business is choosing between SharePoint and a different platform for internal or public facing work, our guide on how to choose a CMS for your UAE business works through that decision in more general terms, and our monthly website maintenance checklist covers the ongoing upkeep a live site or intranet both need.
