The right files,
for the right people
We build intranets, document libraries and Microsoft Teams apps on Microsoft SharePoint, set who can open what for each team, and move your files in from where they live today, so people find what they need, and only that.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
You’re in good company
A few of the companies we’ve worked with.
When every team kept its own copy
In many companies, SharePoint and Teams grew one team at a time. Each team made its own sites, a site being the place for a team’s pages and files, and files were copied between folders and chats as the work moved along.
To save time, links often went to everyone in the company and some sites were opened to all. As people moved on, some sites were left without an owner.
So people aren’t always sure which copy is current, and no one has a full list of who can open what. And some customizations stopped working this year, when Microsoft retired the older ways they were built.
What we build
Intranets, document libraries, Teams apps and integrations on Microsoft 365, each site open to the people who need it and built on parts Microsoft supports, so people find the current version in one place.
Intranets people use
Communication sites for news and updates, hub sites that tie related sites together under one navigation, and a home page people start their day from, planned with the people who use them.
Document libraries built for how you work
A library is a site’s store of files. Columns for the details people search by, a content type for each kind of document, views for each team, and version history, so the current version is the one in the library.
Access set for each team
Sites made for an audience, access given to groups rather than to one person at a time, inheritance kept wherever it can be, sharing set to the narrowest kind of link the work allows, and guests only where the work needs them.
Moves into SharePoint
From file shares, from SharePoint Server and from other platforms, with Microsoft’s own migration tools, and who can open what planned before any file moves.
Web parts and extensions
Built with the SharePoint Framework (SPFx), Microsoft’s main way to extend SharePoint, and tested before release. A web part is a block on a page; an extension changes how pages, lists or libraries look or work. Replacements for retired add-ins included.
Teams apps
Tabs, bots and message extensions for the work your teams do in Teams, built with Microsoft’s current tools for Teams and Microsoft 365 apps.
Integrations through Microsoft Graph
Your product and systems reading and writing files, lists and sites through Microsoft Graph, Microsoft’s API for Microsoft 365. Each integration signs in with its own app registration, its identity in Microsoft Entra ID, and selected permissions give it only the sites it needs.
Rebuilding what Microsoft retired
Add-ins rebuilt with SPFx, 2013 workflows as Microsoft Power Automate flows, alerts as flows or SharePoint rules, and Microsoft InfoPath forms as Microsoft Power Apps or Microsoft Forms, as below.
Ready for Copilot and agents
Access reviewed before Microsoft Copilot reaches your people, since it answers each person from what they can at least view. With a Copilot license in your organization, SharePoint admins also get SharePoint Advanced Management features for this. And agents that answer from your SharePoint content, or assistants of your own that reach it through Microsoft Graph, each with only the access it’s given.
- Connecting any of your systems:Systems & API Integration
- Automation across your tools:Workflow Automation
- Care once it’s live:Support & Maintenance
- Apps and flows on the same tenant:Low-code development, for Microsoft Power Platform apps
- Developers in your own team:Hire developers for SharePoint sites
Each person sees only what they can open
In SharePoint, a site’s libraries, folders and files take their permissions from the site, unless that inheritance is broken for one of them. Inheritance means each one follows the site’s access until it’s given access of its own.
Sharing adds access one item at a time, with a link for specific people, for people in your organization or, where it’s allowed, for anyone. Microsoft notes that even a link anyone can use doesn’t, on its own, put a file into search results or Copilot’s answers: it has to be opened first.
Microsoft Copilot answers each person only from what they can at least view. So a file opened to everyone in the company some time ago, to save time, can come up in an answer to anyone who asks.
So each site is made for its audience, access goes to groups rather than to one person at a time, links are reviewed, and a site holding the most sensitive files can be kept out of search and Copilot with Restricted Content Discovery while its access is put right.
Site
Finance
Library
Plans
- Budget planOpen to the Finance teamCan openCan’t open
- Pay reviewOpened, some time ago, to everyone in the companyCan openCan’t open
Assistant
What’s in next year’s plans?
{{ shAs }}
Two files in Finance: Budget plan and Pay review.
One file: Pay review, open to everyone in the company.
Nothing here I can show you.
An assistant answers from what each person can open, so who can open what is set first.
{{ shStatus }}
When older parts are switched off
This year, Microsoft retired several older ways SharePoint was extended in Microsoft 365. Add-ins and SharePoint 2013 workflows stopped on April 2. Legacy sign-in for scripts and tools was blocked by default from February 16 and for good from May 1. InfoPath Forms Services was removed after July 14, and alerts stopped working in July.
Each has a supported replacement. The SharePoint Framework takes the place of add-ins, with Microsoft Entra ID for the access an app needs. Scripts and tools sign in with modern authentication. Workflows move to Power Automate, alerts to Power Automate or SharePoint rules, and InfoPath forms to Power Apps, Power Automate or Microsoft Forms.
On a company’s own servers, SharePoint Server 2016 and 2019 reached the end of extended support on July 14, 2026. A farm, the servers SharePoint runs on, keeps running after that date, without Microsoft’s support, and SharePoint Server Subscription Edition is the supported version.
So what stopped is rebuilt on those parts, starting with what the business relies on, and a farm still on 2016 or 2019 moves to Subscription Edition or to SharePoint in Microsoft 365 in planned steps, set from the dates Microsoft publishes.
Start with a map of your sites
The map covers your sites and hubs, who owns each and which have lost their owners; who can open what, by group, with the places inheritance is broken, the guests and the sites open to everyone in the company; your libraries, their columns and versions, and where copies of the same file live; your customizations, from SPFx solutions to anything left from add-ins, 2013 workflows, InfoPath forms or alerts, and what replaced each; each integration, what it reads and writes, how it signs in and which sites it can reach; your Teams apps; any SharePoint Server farm, its version and where it stands on Microsoft’s dates; and which features need which licenses.
The first step is one site the business relies on: its access set by group, its links reviewed and its files in one library, so the way is proven before the next site follows.
You get a written map and a proposal for the first step.
Questions worth asking
Something in SharePoint stopped working this year. Why?
Most likely it was built on one of the older parts Microsoft retired in SharePoint in Microsoft 365: add-ins and SharePoint 2013 workflows on April 2, legacy sign-in for scripts and tools from May 1, InfoPath Forms Services after July 14 and alerts in July. Each has a supported replacement, so we find what it was built on and rebuild it on that.
We still run SharePoint Server 2016 or 2019. What are our options?
Both reached the end of extended support on July 14, 2026, as Microsoft Lifecycle lists them, so they no longer get Microsoft’s support. You can move to SharePoint Server Subscription Edition, the supported version for your own servers, or to SharePoint in Microsoft 365. Either way the move goes in planned steps, starting with what the business relies on.
Will Copilot show people files they shouldn’t see?
Copilot answers each person only from what they can at least view, so it follows the access you’ve set. What matters is that the access is right: a file open to everyone in the company can come up for anyone. So we review access first, and Restricted Content Discovery, one of the SharePoint Advanced Management features that come with Copilot licenses, can keep a site out of search and Copilot while its access is put right.
Can you move our files from network drives or another platform?
Yes, with Microsoft’s own migration tools, once who can open what is planned in SharePoint, so files land in sites made for their audience instead of being copied across as they are.
Should this be a SharePoint site, a Teams team, or both?
It depends on the work. Each team in Teams keeps its files in a SharePoint site, so the two work together. A team suits people who work together every day; a communication site suits news and information many people read. Many companies have both, linked to each other.
Can you replace our old add-ins with something supported?
Yes. Microsoft’s recommended replacement is the SharePoint Framework: web parts for what an add-in showed on a page, and for an add-in that ran outside SharePoint, an app of your own that gets its access through Microsoft Entra ID. We rebuild the ones the business still needs and retire the rest.
Can our product or systems work with our SharePoint files?
Yes, through Microsoft Graph. Each integration gets its own app registration, and with selected permissions it reaches only the sites, lists or files it’s given: until a site is assigned to it, it can’t open any.
Can you rebuild our InfoPath forms and old workflows?
Yes, as Microsoft recommends: forms as Power Apps or Microsoft Forms, and workflows as Power Automate flows, keeping the steps your teams rely on.
Can you help people find things?
Yes. Navigation that follows how people look for things, columns for the details they search by, and one current version of each file in its library, so what people find is the version they need.
Do we need more Microsoft licenses for this?
Sometimes. Some features need particular licenses: SharePoint Advanced Management’s features for Copilot, for example, come with Copilot licenses. We say which features the work needs, and which licenses they need, before anything is bought.
Can you take over our existing intranet?
Yes. The map shows what each site does, who owns it, how it’s built and who can open what. Then we keep what works, fix what needs fixing, and look after it from there.
How do you keep our files secure?
Each site is made for its audience, access goes to groups, sharing is set to the narrowest kind of link the work allows, guests come in only where they’re needed, and sign-in stays with Microsoft Entra ID, the one your organization already uses. Code we add is reviewed before release, so problems are found early.
What does it cost?
It depends on the work: the sites, libraries, apps and integrations involved, and whether they’re new, moved or rebuilt. Before any work starts, you get a written proposal with the scope, the price or rate, and how you pay.
Can we hire SharePoint developers for our own team?
Yes. Tell us about your sites and the work ahead, and within 48 hours we’ll introduce SharePoint developers who fit it, each working in your time zone. You meet them and decide who joins.
Microsoft, InfoPath, Microsoft 365, Microsoft Entra, Microsoft Teams, Power Apps, Power Automate, Power Platform and SharePoint are trademarks of the Microsoft group of companies, and the other Microsoft product names on this page, such as Copilot, Microsoft Forms, Microsoft Graph and SharePoint Advanced Management, may be too. Webair is independent of Microsoft, and isn’t sponsored by, endorsed by or affiliated with it.
Let’s build it better
Tell us which sites and files your teams rely on, and who can open them today. A short call is enough to see where to start.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}