Working with SharePoint?

SharePoint permissions, workflows or migration a mess? We fix it.

Most SharePoint tenants that reach us have been through several consultants, a half-finished migration, and a few workflows that stopped running one morning without warning. We untangle what is actually there and get the parts your staff use working properly.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

sharepoint.log

still failing

What it is

SharePoint at a glance

Microsoft SharePoint, first released in 2001, is a collaboration, document management and intranet platform. SharePoint Online is the cloud-hosted version that comes with Microsoft 365, while SharePoint Server (2016, 2019 and Subscription Edition) is the version organisations run on their own infrastructure.

The core building blocks are site collections, sites, lists, libraries, pages, permissions, workflows (now Power Automate) and web parts built with SPFx. Every Microsoft Team is backed by its own SharePoint site for files, which is why SharePoint quietly underpins far more day-to-day work than most staff realise. In Microsoft-centred workplaces it is the dominant intranet platform.

Type
Collaboration and content platform
First released
2001
License
Proprietary; included in Microsoft 365 or standalone / on-prem
Maintained by
Microsoft Corporation
Typically used for
intranets, document management, team sites, forms + workflows (via Power Automate), internal portals

The honest version

SharePoint pros and cons

No technology is all upside. This is where SharePoint earns its place and where it tends to cause trouble.

Where SharePoint is strong

  • Deep Microsoft 365 integrationIt plugs into Teams, OneDrive and Outlook without extra configuration, so the files behind a Team or a group live somewhere your staff can actually find.
  • Fine-grained permissions and versioningAccess can be set per site, library, folder or item, and every document keeps a full version history that you can roll back without pulling backups.
  • Workflow with Power AutomateApprovals, notifications and routine business processes can be built without writing code, reusing the accounts and groups you already have.
  • Hub sites and modern ListsHub sites give an intranet a navigable shape, and modern Lists are capable enough to replace a lot of small Access and Excel databases.
  • SPFx, search and complianceThe SharePoint Framework lets developers build custom web parts, search is decent across the tenant, and compliance features cover retention, eDiscovery and sensitivity labels.

Where SharePoint bites

  • Permissions break easily and are painful to auditInheritance gets snapped on a folder nobody remembers, and years later the wrong people have access to files nobody has reviewed.
  • Classic to modern migrations leave things behindCustom branding and old workflows rarely survive the move, and classic site collections with custom script often refuse to upgrade at all.
  • Old workflow engines are goneSharePoint 2010 workflows stopped in November 2020, SharePoint 2013 workflows have been retired on Microsoft 365, and InfoPath forms are long dead. Anything built on them must be rebuilt in Power Automate and Power Apps.
  • SPFx has a learning curveBuilding modern web parts means Node, TypeScript and a toolchain that changes often, which is a reach for teams used to classic server-side customisation.
  • Site and list sprawlOlder tenants accumulate abandoned sites, orphaned Teams and lists nobody owns. Without governance, external sharing policies default permissive and nobody notices for years.
  • OneDrive sync and on-prem baggageThe sync client chokes on long paths and odd characters in file names, and on-prem SharePoint Server (2016, 2019, Subscription Edition) still exists in plenty of places and is much harder to upgrade than the cloud version.

Sound familiar?

Common SharePoint problems we fix

The SharePoint problems that bring people to us, and what you have once each one is fixed.

You are not authorized to perform the current action

The wrong people have access

Broken permission inheritance, nested groups and legacy sharing links that nobody has reviewed. Fixing one site does not fix the pattern.

Permissions audited and inheritance restored

workflow status: suspended

Workflows stopped running

Processes built on SharePoint 2010 or 2013 workflows that Microsoft has since retired, and nobody rebuilt them in Power Automate.

Rebuilt in Power Automate and tested

migration stuck at 62%

The move from on-prem stalled

Half the content is on a SharePoint Server, half is in SharePoint Online, and the permissions do not line up between them.

Content and permissions moved cleanly

upgrade to modern blocked by custom script

Classic sites refuse to go modern

A classic site collection with custom script enabled, old master pages, or web parts that have no modern equivalent.

Modernised with the parts staff actually use

25TB storage cap reached

A site has hit its ceiling

Years of large files, versions and backups stored where nobody is pruning them, now blocking uploads.

Reduced, archived and alerted before it fills

InfoPath form retired

Forms broke when InfoPath went away

Business forms built in InfoPath that no longer render, with no supported upgrade path other than Power Apps.

Rebuilt in Power Apps

admin: unknown consultant

The previous consultant disappeared

Nobody holds the global admin account, the tenant is in someone else's name, and nothing is documented.

Ownership and documentation back with you

What we do

SharePoint help, from rescue to upkeep

Call us for one broken workflow, or hand us the whole tenant.

Migrations
On-prem SharePoint Server to SharePoint Online, tenant to tenant, or finishing a move that somebody else started.
Permissions
Auditing who can see what, restoring inheritance, and setting a pattern your staff can actually keep to.
Workflow replacement
Retired SharePoint 2010 and 2013 workflows rebuilt in Power Automate, InfoPath forms replaced with Power Apps.
Modernisation
Classic site collections moved to modern, with hub sites, modern pages and web parts built in SPFx.
Governance and clean-up
Abandoned sites, orphaned Teams and stale sharing links tidied up, with an external sharing policy that fits your business.
Managed Tech
Ongoing administration, monitoring and a team to call when something breaks.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running SharePoint alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

SharePoint questions

Something else? Call+1 737 727 7327

Can you migrate our on-premises SharePoint Server to SharePoint Online?

Yes. We inventory the site collections, lists and customisations first, work out which parts can move straight across and which need rebuilding, and run the migration in stages so staff keep working. Permissions and shared links are mapped across rather than left behind.

Can you replace retired SharePoint 2010 or 2013 workflows with Power Automate?

Yes. Those workflow engines have been retired, so there is no fix short of rebuilding. We document what each workflow actually does, rebuild it in Power Automate, test it against your real data, and then retire the old one.

Why are our SharePoint permissions giving the wrong people access?

Almost always it is broken inheritance, nested groups that grant more than anyone realised, and old sharing links that were never expired. We audit who can see what, restore inheritance where it is safe, and show you a pattern your staff can keep to.

Can you take over a SharePoint tenant from a previous consultant?

Yes. We recover global admin, document what is actually in the tenant, and move ownership and billing back into your name. You end up with the accounts, licences and knowledge you should have had from the start.

How do we clean up abandoned SharePoint sites and lists?

We identify sites that have had no activity, Teams with no owner, and lists nobody opens any more, then agree what to archive and what to delete. External sharing links are reviewed at the same time, because that is where most tenants leak.

How much does SharePoint help cost?

Estimates are free. Share the tenant name and the sites or lists giving you trouble, and we come back with a quote before anyone remotes into the admin centre.

Free estimate

SharePoint giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.