Services · Custom software and business systems · SharePoint development

An intranet and document system your staff will actually open every morning.

SharePoint development for UAE organisations that already pay for Microsoft 365 and want more from it: a working intranet, a document library people trust, and approvals that no longer live in email. We build in SharePoint Online in English and Arabic, with Power Platform automation where it saves real time.
Built for
Mid sized and large UAE organisations on Microsoft 365 that need an intranet, controlled document libraries or approval workflows in English and Arabic.
Typical timeline
A tenant review and information plan in two to three weeks. A first intranet or document area live in roughly six to ten weeks.
What you own
Every site, library, flow and custom web part sits in your Microsoft 365 tenant, with the source code in your repository.
Rated
4.7 / 5 from 23 Google reviews

In short

Most companies in Dubai and Abu Dhabi that run on Microsoft 365 already own SharePoint, often without knowing it. Files sit in personal OneDrive folders and shared drives, policies get emailed as attachments, and nobody is sure which version of a contract is the current one. A problem we often see is a SharePoint tenant that grew on its own, with hundreds of sites created through Teams and no structure behind them. The work usually starts with tidying that up before anything new is built.

Arabic matters more here than many vendors admit. SharePoint Online supports Arabic sites that render right to left, and communication sites can carry translated versions of each page. We set up the language settings, navigation and page templates so the Arabic intranet is a proper site rather than an afterthought, and we test layouts with real Arabic content, since mixed Arabic and English titles break in ways that placeholder text never shows.

Document management is where SharePoint earns its keep in UAE businesses. Trade licences, Emirates ID copies, tenancy contracts, visa files and supplier agreements all have expiry dates and need controlled access. We build libraries with metadata, retention and permission groups, then use Power Automate to send renewal reminders and route approvals, so the right people see the right file and a renewal is not missed.

Data location and access are real questions for regulated sectors. Microsoft operates cloud regions in the UAE, and many organisations here ask for their data to stay in country. We review your tenant settings with your IT team, apply sensitivity labels and sharing rules, and suggest confirming specific requirements under UAE PDPL or your sector regulator with your compliance lead, since the rules differ between a free zone entity and a government supplier.

Decisions made in the first two weeks shape everything that follows. The biggest one is whether to organise around departments or around work. A department structure looks tidy on an org chart but breaks the moment a project involves finance, legal and operations together, which in UAE companies with lean head offices is most of the time. We usually recommend a small number of hubs by function, with project and client sites hanging off them, and a naming rule that stops five sites all called Finance from appearing within a month.

It also helps to prepare a few things before we start. A list of the documents people search for most, the names of one owner per department who can make decisions, and an honest view of which shared drives are still in use will save weeks. If you have a separate HR, ERP or CRM system, tell us early, because the most useful intranets in this market pull leave balances, policy acknowledgements or customer files from those systems rather than asking staff to open three different tools.

Codeeo builds SharePoint from Dubai Silicon Oasis, with a team that knows both the Microsoft 365 admin centre and the way UAE offices actually share files. We can run workshops at your office with department heads, then keep the build moving on Teams calls and WhatsApp between sessions.

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What you get

The parts of SharePoint that make a difference to daily work.

SharePoint is broad, and most of its value comes from a handful of things done properly: a clear site structure, libraries with sensible metadata, permissions people understand, and automation for the approvals that slow everyone down. We focus there first, and only write custom code where the standard features fall short.
Explain your project
  • Intranet and communication sites

    A home site with news, policies, people search and department hubs, designed for your brand and set up in English and Arabic. We plan it so the home page answers the questions staff ask most in their first week.

    Staff have one place to start the day instead of a dozen email threads.

  • Document management

    Libraries with content types, metadata, versioning and retention, built around the documents your teams really handle, from contracts to visa files. Search filters by metadata mean nobody needs to remember which folder a file was saved in.

    People find the current version of a file without asking a colleague.

  • Permissions and governance

    A site and permission model based on groups rather than individuals, with rules for who can create sites and share externally. Owners for every site are named and reviewed, so access does not grow quietly over time.

    Access is predictable, and leavers lose it the day they go.

  • Approvals with Power Automate

    Leave, purchase, contract and document approvals moved out of email into flows that log every decision. Each flow keeps a record of who approved what and when, useful when auditors ask.

    Approvals move faster and leave an audit trail.

  • Microsoft 365 and Teams integration

    SharePoint wired into Teams channels, Outlook and OneDrive so files live in one place however people open them. We also set rules for when a Team should create a new site and when it should use an existing one.

    One copy of each file across every app your staff use.

  • Custom web parts

    SharePoint Framework web parts in React and TypeScript for things the standard parts cannot do, such as live dashboards or a staff directory with Arabic names. Each web part is documented and kept in your own source repository.

    The intranet does what your business needs, not only what the template offers.

  • Migration from file shares and older SharePoint

    Content moved from network drives, Dropbox or SharePoint Server into SharePoint Online, with folder clean up and permission mapping planned first. Old versions and abandoned folders are archived rather than copied across blindly.

    You arrive in the new system without carrying the old mess with you.

  • Arabic and right to left setup

    Arabic site language, translated pages, right to left layouts and fonts checked on real content. Date formats and the Hijri calendar display are considered where your users expect them.

    Arabic speaking staff get a site that reads naturally.

Who this is for

Three SharePoint situations we are asked to sort out.

SharePoint projects in the UAE usually begin with one of three pains: a tenant nobody controls, an intranet nobody visits, or documents spread across too many places. This is how we approach each.
01

Teams created hundreds of sites and nobody knows what is where

Every new Team quietly creates a SharePoint site. We audit what exists, archive the dead ones, agree naming and ownership rules, and set a hub structure so new sites land in the right place.

Govern before you build.

02

You have an intranet, but staff ignore it

Usually the content is stale and the home page answers nobody's question. We rebuild around the tasks people come for, such as forms, policies, people and news, and give each department an owner who keeps it current.

Built around tasks, not departments.

03

Licences, contracts and HR files are scattered

We bring them into libraries with expiry metadata, restricted access and automatic reminders, so a lapsed trade licence or visa is flagged weeks ahead rather than found by accident.

Expiry dates tracked, not remembered.

Four steps, with the information plan agreed before any site is built.

  1. 01ReviewYour tenant, existing sites, file shares, licences and how each team really works with documents. We also interview a few staff from each department about where they lose time today.
  2. 02PlanSite structure, metadata, permissions and the Arabic and English approach, signed off by the people who will own it. Naming rules and site ownership are written down so the structure survives staff changes.
  3. 03BuildSites, libraries, flows and any custom web parts, tested with real content and real users. Pilot users from two or three departments test it before the wider rollout.
  4. 04AdoptMigration, training for owners and staff, and a short period of support while habits change. We hand over a short governance guide that site owners actually read.

Technology

What we build this with.

We stay inside Microsoft 365 wherever we can, and write custom code only where it earns its place.

01Microsoft

  • Azure
  • Power Platform

02Custom web parts

  • React
  • TypeScript
  • Node.js

Questions people ask before a SharePoint project.

Often not, since SharePoint Online comes with most business plans.

Most Microsoft 365 business and enterprise plans include SharePoint Online and Power Automate with standard connectors. Premium connectors, advanced compliance features and some Power Apps scenarios need extra licences. We check your current plan first and tell you plainly what you already have and what, if anything, would need to change.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews