An editorial team plans news by audience, page templates keep the look consistent, approvals and review dates keep content current, in every national language.
An editorial model spreads the work across many shoulders.
In a care provider with five locations, the communications team does not write alone. An editorial lead at head office sets priorities and approves the start page, one editor per location and per specialist area writes news and maintains the pages of their area, and an editorial plan records who publishes what in which week; annual dates such as the pay round, the flu vaccination and the year-end close are in it from January. The roles are groups in Entra ID: editors are members of their site, not owners, ownership stays with two named people, and the approval separates writing from publishing. After handover this editorial team runs the intranet itself: it creates areas, pages and navigation entries, maintains templates and audiences and reads the page analytics. That keeps the start page alive even when the communications team is on holiday for a week.
02
Audiences decide who gets to see a news post.
The editor of the Olten location writes the news post on the new duty roster and picks the location's group as the audience; the news web parts of the home site, the hub and the SharePoint app in Teams show the post to these employees, and everyone else keeps seeing their own news. An audience steers attention and protects nothing: whoever knows the link opens the page, and confidential content belongs on a site with its own permissions. Organisation news from the home site comes before divisional news; a post everyone has to read is lifted to the top by the editorial lead for a set period, and a mailed summary brings the week's posts to employees who rarely visit the intranet. After publishing, page analytics show readers per day and channel and the share of the audience that opened the post; if it stays low, the post goes out a second time into the location channels in Teams.
03
Page templates and web parts hold the look together.
The editor of the Olten location creates a new page and picks the template for location pages; sections, web parts and design are already in place, and she only fills in text, image, quick links, events, people and documents. The editorial team maintains one such template per kind of page: the directive page with owner, validity and document, the location page with team, events and news, the news post with image, lead and contact. Logo, colours and header are set once per hub by your IT, the associated sites inherit them, and an editor cannot change them by accident. We build custom web parts with the SharePoint Framework only where a standard web part is missing, for example for data from a business system; every custom web part then needs someone who maintains it through the platform's updates.
04
Approval and review date keep content valid.
The care editor sends the page on the new medication handout for approval; the specialist in charge receives the request in Teams, checks text, audience and the linked document and approves, and only then does the page appear for readers. The approval runs as a flow on the site pages library, the approvers sit in a group rather than as names in the flow, the responses land in the Approvals app, and every approval is recorded with person and time in the page's version history. A review date as a column of the library reminds the owner after a year whether the content still holds; a scheduled flow sends the reminder and reports overdue pages to the editorial lead. News expires: the post on the flu vaccination disappears from the web parts after the date and stays findable. Which sites need an approval and which publish directly is under What you decide.
05
The conversation runs in the comments, in Viva Engage and in Teams.
Under the news post on the duty roster a nurse from the night shift asks about handover times, and the head of nursing answers in the comments; the location's community in Viva Engage carries the conversation on, with storylines per person and questions with a marked best answer, and the management writes along in its storyline. Communities are open or private, posts are subject to retention and eDiscovery in Purview like Teams messages, and who moderates and what gets reported is settled by communications before the start. Comments and reactions on pages are switched on or off by the editors per site. The channels in Teams remain the place for the work of one team, Viva Engage the place for the conversation across areas, and the editors steer questions to where someone answers them.
06
The editors write for the phone and for search.
Most employees of the care provider work without a desk and open the intranet in the SharePoint app in Teams on their phone: a dashboard with cards for the duty roster and the payslip, news by audience, the resources from the global navigation. The editors therefore write for the narrow screen: a title that fits on one line, a landscape image, a lead that says in one sentence what applies, links with names. Web parts that sit side by side on the desktop stack on the phone, which is why the editors check every template in the mobile preview. The same craft applies to search: the title carries the word people search for, so Expenses and not just the number of the policy, the page description appears in the results, and columns such as area, validity and document type make a directive filterable.
What you decide.
One central editorial team or divisional editors?
Options
1One central editorial team in communications writes all content
2Divisional editors write, communications approves the start page and organisation news
3Every site owner publishes alone, without approval
Our recommendation: Divisional editors with an editorial lead in communications: every location and every specialist area writes its news and maintains its pages, communications approves what appears on the home site and as organisation news, and a shared editorial plan shows what comes when. The roles are groups in Entra ID, every editor has a deputy, and the editorial handbook records templates, audiences and review dates. A central editorial team suits an organisation with one location and a handful of topics that one person can oversee.
What we advise against: A central editorial team that writes every divisional page itself: it becomes the bottleneck, and the divisions stop reporting content.
Approval for every page or only for the start page?
Options
1Page approval on home site, hubs and directive pages, divisional sites publish directly
2Page approval on every site
3No approval, correction after publishing
Our recommendation: Page approval where many people read or something applies: on the home site, on the hubs and on pages that carry directives, with a group of approvers, a deadline and the deputy in the flow. Divisional sites publish directly, with a second pair of eyes within the divisional editorial team and the review date per page. Directives themselves go through the content approval of their library rather than page approval, so that the page points to the current version.
What we advise against: An approval for every page, including the canteen menu: the approvers become a queue, and the editors fall back on Teams posts.
Switch on Viva Engage or leave the conversation in Teams?
Options
1Comments on news and the channels in Teams, no Viva Engage
2Viva Engage with communities per location and topic, moderated
3Everything open, without moderation
Our recommendation: Start with comments on news and the channels in Teams that exist anyway. Viva Engage is added when questions are asked across areas, when the management wants to run a storyline and when one person per community is named to moderate and answer. Communities appear in Teams as long as your IT does not switch the feature off; where the conversation runs is set by communications, so that questions do not stay unanswered in three places.
What we advise against: Switching on Viva Engage without moderation and without anyone from the management writing along: communities without answers fall silent within weeks.
Copilot in the editorial team: drafts from documents or everything by hand?
Options
1Copilot in SharePoint drafts pages and news from approved documents, the editors approve
2Only text suggestions while writing
3No AI in the editorial team
Our recommendation: Copilot in SharePoint for the editors who hold a Copilot licence: from an approved document the draft of a page or news post takes shape in the chosen template, the editors cut, order and publish through the same approval as every other page. Copilot drafts only from files the author may open, and the approval stays with people. For the second national language it delivers a rough draft that the translator checks before the language version is approved.
What we advise against: Publishing Copilot drafts unread: the source may be out of date, and the responsibility stays with the editors.
Status and sources.
As of: October 2026
As of 3 June 2026
Viva Engage in Teams: storylines available, communities in preview.
Storylines and communities from Viva Engage appear in Teams and are switched on by default; each of the two can be switched off separately in the messaging settings of the Teams admin center. Storylines in Teams are generally available, communities in Teams run as a public preview. Creating communities and assigning leaders still happens only in Viva Engage itself.
The Approvals app stores in Dataverse and logs in Purview.
Requests from the Approvals app in Teams are stored in the default Dataverse environment; according to Microsoft, this environment does not currently support backups. Approving, rejecting, reassigning and signature steps appear in the Microsoft Purview audit log. Signature requests through Adobe Sign or DocuSign are stored in that provider's cloud and need its licence.
Copilot in SharePoint is generally available from 30 September 2026.
Copilot answers questions from SharePoint content and creates pages, sites, files and simple approvals. Everyday use is included in the Microsoft Copilot licence; large-scale work such as reviewing whole libraries is billed in Copilot Credits.
Viva Connections is now the SharePoint app in Teams.
The home page in Teams continues to run on the SharePoint home site, now under the name SharePoint app in Teams. Administrators create home sites directly in the SharePoint admin center, and the Announcements web part no longer needs an extra Viva licence. The change rolled out from May to the end of June 2026.
This is how we put it into practice: editorial model, templates and approvals built with your communications team and handed over so that your editors create pages, news and navigation themselves. SharePoint intranets & portals
An editorial lead in communications and, per location or specialist area, one person with a deputy, each with a fixed slot in the calendar. The divisional editor writes a few news posts a month and checks their pages against the review date, the lead runs the plan, approves and reads the analytics. It takes no more people than that once templates and approval paths are in place; a lack of time is a more common reason for a silent intranet than a lack of people.
Can a news post go to several audiences at once?
Yes. A post carries one or more groups from Entra ID and appears to everyone who is in at least one of them. Without an audience, everyone who may open the site sees it. The groups are maintained by your IT or the HR system, not by the editors, which is why we settle at the start which groups serve as audiences: locations, areas, managers, apprentices.
What does a person see who belongs to no audience?
Everything published without an audience, that is the organisation news and the pages of the sites they may open. Audiences show things, they do not lock them: a post with an audience also opens for someone outside it as soon as they receive the link. Whoever must not see something belongs outside the site's permissions; that is covered in the chapter on permissions and sharing.
Can employees suggest news themselves?
Yes, through a form or a Suggest news list on the home site that feeds the editorial plan; the divisional editor writes the post from it or passes the suggestion on to the location. For short messages from one team the channel in Teams is the right place, for personal posts the storyline in Viva Engage. That keeps the start page edited, and the message from the shop floor still gets through.
How long may a news post be so that it gets read on the phone?
Long enough for the title to fit on one line and for the lead to say in one sentence what applies and from when. The rest follows in short sections with subheadings, plus a landscape image, and at the end the link to the directive and the contact person. Page analytics show how many readers come through Teams and the phone, and the editors check every template in the mobile preview before releasing it.
What happens to a page whose review date passes?
A scheduled flow reminds the person in charge in Teams before the date and reports the page to the editorial lead once it has passed; the page stays visible and carries the status until someone confirms, revises or withdraws it. Withdrawn pages move to an archive area of the site or are deleted after the retention period. News needs no review date: it carries an expiry date and disappears from the web parts afterwards.
What does Copilot in SharePoint change for the editors?
Anyone with a Copilot licence has the draft of a page or news post created from a document in the chosen template, then cuts, orders and publishes through the usual approval. Copilot drafts only from files the author may open, and everyday use is part of the licence. Without a licence the editors write as before; the pages Copilot later answers from are the same, which is why title, lead and metadata count twice.
Next chapter · Chapter 4
Documents and knowledge: store, find, use with Copilot.
How are documents stored, found and used by Copilot?