Who sees what in the intranet, from group to guest.
Groups from Entra grant the rights, sharing links and guests follow fixed rules, labels protect documents, and Copilot sees only what the person is allowed to see.
noAccess through membership of the project, label Confidential
appliesPrivate site or private channel, links for specific people, label on the site
documented decisionShared channel or extranet site after a documented decision by the owner
documented decisionAfter a site access review, with document labels whose rights allow Copilot to read
Personal dataPersonnel files, salary round, health information
no
no
documented decisionOnly the team that processes the data, with a decision by the data protection officer and a dedicated label
no
documented decisionDecision by the data protection officer; Restricted Content Discovery on the site until then
External with partnersPlans, quotes and minutes of a joint project
noPartner content sits in the extranet site or the shared channel
documented decisionThe team involved and its management
applies
appliesGuests with an expiry date or external people in the shared channel, label for partner work
documented decisionAgents of the site for internal members only; guests get no Copilot answers from your tenant
Legend:appliesdocumented decisionno
As of October 2026, derived from the dated facts of this chapter and the Microsoft pages that back them. Our frame for the start, not legal advice; the decision per content class is taken with your data protection officer.
01
Rights hang on groups, not on people.
A new employee starts in the finance department. Your IT adds her to the Finance group, and on her first day she sees the Finance hub, the library with directives, the team in Teams and the news of her division; nobody has touched a single site. SharePoint knows the roles owners, members and visitors per site, and behind each one stands a group: the Microsoft 365 group of the team or a security group from Entra ID that doubles as an audience for news. Rights granted directly to people or on individual folders work on the day they are granted and then disappear from view; the site access review years later shows them as exceptions nobody can explain any more. That is why individual shares from folder trees end up in groups during a migration.
02
Sharing links follow a default per site.
When someone shares, SharePoint proposes a link, and that default decides more in daily work than any directive. The tenant sets the upper limit, from anyone with the link to people in your organisation only, and every site may be as open or tighter. For the intranet: links for specific people as the default, access for external people with a fixed expiry date, and anyone-with-the-link only where an owner deliberately enables it for a site. We set these levels once per kind of site and write them into the template, so that every new site starts with the same default and every change to the sharing settings is in the audit log.
03
Guests and partners work in separate rooms.
An engineering firm accompanies a construction project. Whoever works across the whole project joins the team as a guest through Entra B2B and sees its site; a partner firm that follows a single strand works in the shared channel with its own account, and both organisations set up their cross-tenant access settings for it. Suppliers, partners or members who need documents on an ongoing basis get an extranet site with guest access, kept apart from the internal intranet by label and sharing rule. Every guest access expires after the set period unless someone renews it, and Conditional Access applies to guests as it does to employees.
04
Sensitivity labels set the frame for site and document.
The label on a team or site sets privacy, guest access, external sharing and access from unmanaged devices; the owner picks it at creation, and a site labelled confidential can no longer be opened to the outside by accident. The documents inside do not inherit the label automatically: a label on the document encrypts it and decides through its rights who reads, edits or forwards, and whether Copilot may evaluate the content. Auto-labelling policies find personal data in libraries and apply or replace the label, even one a person applied. Which labels are on offer is set by a policy in Purview, and every change is in the audit log.
05
Copilot and agents see only what the person sees.
Copilot in SharePoint, Microsoft Search and every agent on a site answer with the rights of the person asking, and that is exactly why they find everything that is shared too widely: the folder with salary figures that someone shared with all employees turns up in the answer because the permission allows it. The reports in SharePoint Advanced Management show sites with many permission holders and items shared with everyone except external users; from the report your IT starts a site access review, and owners see the most widely shared items first. Sites whose permissions are being reviewed are taken out of organisation-wide search and Copilot answers by Restricted Content Discovery without any permission changing: whoever knows the site keeps working there as before.
06
Client data and personal data need rooms of their own.
A law firm creates one site per matter, with a label, its own group and a sharing level that rules out links to the outside; search finds matter documents only for the matter team, and the agent of the firm answers from the same circle. The salary round of the HR department sits on a site of its own under Restricted Content Discovery until the site access review is complete. The data protection officer approves guests, labels and the people directory and keeps the registers for them. Who sees what, per content class and audience, is in the sharing matrix above; ownership, lifecycle, data residency and backup belong to the chapter on governance and security.
What you decide.
Microsoft 365 groups or security groups for the rights?
Options
1Microsoft 365 groups per team and team site, security groups for audiences and cross-cutting rights
2Security groups from the directory only, maintained by IT
3Rights per person where things have to move fast
Our recommendation: Microsoft 365 groups for everything that is a team, because team site, channels, Planner and mailbox hang off them and the owner maintains the members; security groups for divisions, locations and functions, because they are fed from the directory or the HR system and double as audiences for news. Visitor rights on communication sites go to the group of all employees rather than the Everyone claim, so that guests stay out.
What we advise against: Rights to individual people or on deep folders because it has to be quick. Both disappear from view and return as exceptions in the next site access review.
Guest in the team, shared channel or an extranet site of its own?
Options
1Guest in the team for people who work across the whole project
2Shared channel for a partner firm on a single strand
3Extranet site for suppliers, partners or members with an ongoing need
Our recommendation: By duration and breadth of the collaboration: the guest in the team sees everything the team sees and fits the engineer who accompanies the whole project. The shared channel shows only its own files and fits a partner firm that works on one strand and does not belong in the whole team for it. The extranet site fits when many external people need current documents on an ongoing basis; label and sharing rule keep it apart from the intranet. In every case the access ends on its own, and the data protection officer knows the list of guests.
What we advise against: Guests in the management team or in sites with personal data because a room of their own is work. Those rooms stay internal.
How many sensitivity levels does the intranet need?
Options
1Three levels for sites, internal, confidential and strictly confidential, with one mapping per kind of site
2One level per division
3Labels on documents only, sites stay without
Our recommendation: So few that an owner picks the right one at creation without thinking, each with a clear effect: the intranet level allows all employees and no guests, the confidential level makes the site private and rules out external sharing, the strictest level lets unmanaged devices in through the browser only and takes the site out of search and Copilot. Document labels come on top where encryption or the reading right for Copilot has to be decided per file.
What we advise against: One level per division. The label describes the level of protection and not the organisation, otherwise every site is wrong after the next reorganisation.
Status and sources.
As of: October 2026
As of 7 May 2026
Labels protect whole teams and sites.
Sensitivity labels can be applied to teams, Microsoft 365 groups, SharePoint sites, Viva Engage communities and Loop workspaces. They set privacy, guest access, external sharing and access from unmanaged devices; the documents inside do not inherit the label automatically.
As soon as one person in the tenant holds a Microsoft Copilot licence, SharePoint administrators get the policies for ownership, inactivity and owner attestation, the sharing and permission reports and the site access review. A base plan such as Microsoft 365 E3 or E5 is required. Restricted site creation by apps still needs the SharePoint Advanced Management Plan 1 add-on.
Site access review: owners clean up their own sharing.
From the reports on sharing links, on content shared with all internal users and on site permissions, SharePoint administrators start a review for up to 100 sites at once. Owners see the most widely permissioned items first, adjust access and close the review with a comment. OneDrive is not included.
Shared channels admit external people through B2B direct connect.
Guest accounts cannot be added to a shared channel. People from other organisations take part with their own account through Microsoft Entra B2B direct connect, and both organisations configure their cross-tenant access settings for it. Each shared channel has its own SharePoint site, whose files only the channel's members can see.
Auto-labelling can replace labels in SharePoint and OneDrive.
Auto-labelling policies can remove a sensitivity label from files in SharePoint and OneDrive or override an existing lower-priority label, even one a person applied. Previously this was possible for emails only.
This is how we put it into practice: ownership, sharing and labels for sites and teams, tested with authorised and unauthorised accounts before Copilot starts. Microsoft 365 governance
Why does a person find documents in search that were not meant for them?
Because a permission allows it, usually an old share with everyone except external users or a link for the whole organisation. Search and Copilot show only what the person may open; they make an overly wide share visible but do not cause it. The site permissions report shows such items, and the site access review sends them to the owners.
May guests see the whole intranet?
No. Guests see the sites an owner invites them to, or the files of the shared channel they work in. The home site, the hubs and the communication sites belong to the group of all employees, and the label of a site can exclude guests entirely. What partners need on an ongoing basis sits in an extranet site.
What happens to a share when the person leaves the company?
Rights that hang on groups end with the departure from the group, usually automatically through the HR system. Sharing links that this person created remain; that is why links for external people carry an expiry date, and the site access review shows links without an owner. When a site owner leaves, the ownership policy flags the site so that someone steps in.
Does Restricted Content Discovery change the permissions of a site?
No. The setting takes the site out of organisation-wide search and Copilot answers and hides the Copilot entry points on the site. Whoever knows the site and is authorised keeps working there as before and still finds files they recently worked with. The setting bridges the time until the sharing of a site has been reviewed.
Who approves sensitivity labels, IT or the data protection officer?
Both, in their roles: the data protection officer sets the levels of protection and their effect, also for personal data and professional secrets, IT sets up the labels in Purview and publishes them to the owners through a policy. Owners choose from that list when creating a site; changing a label afterwards requires the right to do so.
How often do site owners review their access?
Owners of confidential sites confirm them on a fixed rhythm through the attestation policy, and a site access review starts as soon as the report shows a site with very wide sharing or before Copilot reaches the site. Guests appear in the same attestation, and whoever no longer takes part is removed there.
Next chapter · Chapter 6
How file servers and legacy systems move to SharePoint.
How do file servers and legacy systems move into the intranet, and what becomes of SharePoint Server?