Guide SharePoint Intranet · Chapter 2

    How hubs, sites and Teams structure an intranet.

    Hub sites bundle divisions, communication sites carry news and pages, Teams and Loop take on the project work. The storage finder says where content belongs.

    As of: October 2026 · Editor: Marcel Haas

    • Hub sites
    • Communication sites
    • Team sites
    • Teams channels
    • Microsoft Loop
    • Microsoft Lists

    Storage finder

    The questions that lead to the right place.

    Every answer points at one or two places. The place with the most hits is the starting point for the conversation with your owners; what to check there is listed below.

    1. 01

      Who works on it?

      • Me alone, until it is finishedleads toOneDrive
      • A team that works together in Teamsleads toTeams channelTeam site
      • An undertaking across departments, in fluxleads toLoop
      • An editorial team for many readersleads toCommunication site
    2. 02

      How long does it live?

      • Days or weeks, until the matter is doneleads toLoopTeams channel
      • Until it is published, then it movesleads toOneDrive
      • Years, with a version and a review dateleads toCommunication siteTeam site
    3. 03

      Who may see it?

      • Every employee or one audienceleads toCommunication site
      • The members of one teamleads toTeam siteTeams channel
      • Only me and the people I inviteleads toOneDriveLoop
      • Partners from another organisation tooleads toTeams channel
    4. 04

      Does it need an approval?

      • Yes, before it is published for readersleads toCommunication site
      • Yes, as a document with status and versionleads toTeam site
      • No, the work is in fluxleads toLoopTeams channel
      • Not yet, it is a draftleads toOneDrive
    5. 05

      Is it a record?

      • Yes, with a retention period and a reviewleads toTeam siteCommunication site
      • No, a working status that changes dailyleads toLoopTeams channel
      • No, a personal noteleads toOneDrive

    Where the answers lead.

    Communication site

    What that means: Pages, news and the library with directives and forms for many readers, no group behind it, maintained by an editorial team and assigned to a hub.

    What you check: Two owners, the audiences from Entra ID, page approval, the review date per page and the hub association.

    Open page

    Team site

    What that means: The working documents of one team in libraries with content type, columns and versions, behind a Microsoft 365 group that is also the team in Teams.

    What you check: The group and its owners, the libraries per document type, the required columns, the version limit and the site's sharing links.

    Open page

    Teams channel

    What that means: Files next to the conversation: one folder per standard channel in the team site's library, a site of its own for private and shared channels, partners through shared channels.

    What you check: The channel type, the policy for private and shared channels, guests and partners, archiving at project end and retention.

    Open page

    Loop

    What that means: Components in chat, mail and channel posts, workspaces with their own container for the status of an undertaking, content that travels along everywhere.

    What you check: The Cloud Policy for workspaces, the tenant setting for components, where the content is created and stays, and the owners of the workspace.

    Open page

    OneDrive

    What that means: One person's drafts and notes, synced to File Explorer, until the document is meant for the team and moves to a library.

    What you check: The division's filing rule, the retention period for a OneDrive after someone leaves and the folder backup for Desktop, Documents and Pictures.

    Open page
    01

    Hubs follow the areas of work, not today's org chart.

    An energy utility with grid, sales and administration at two locations builds its intranet with one home site and three hubs, one per directorate; the locations are sites under the administration hub. Every hub gives its sites the shared navigation, the design and a search scope of its own, and every site keeps its owners and permissions. When customer service moves from sales to administration, IT assigns its site to the other hub: address, links and documents stay, navigation and search follow the new area. That is why we cut hubs along areas of work that survive a reorganisation, and associate the hubs with the home site so that its search reaches across all of them. What rolls up on a hub is visible only to people who may open the source; a hub grants no rights.

    02

    Each kind of site carries one kind of content.

    The grid operations safety directive sits on a communication site, which informs many readers who write little: pages, news and the library with directives and forms, with no group behind it, maintained by an editorial team. The team site belongs to a Microsoft 365 group and therefore to a team in Teams; it carries the working documents that only members see, every channel has its folder in its library, and private and shared channels get a site of their own. Loop takes what is in flux: agenda items, decisions and the status of a project, as a component in a channel post or as a workspace with its own container. OneDrive holds one person's drafts until the document is meant for the team. For the intranet this means: pages on the communication site point to team sites, channels and workspaces and copy nothing from there, so that every version has one place.

    03

    Every level of navigation leads to the same destination.

    The employee in grid operations finds the safety directive through the home site menu, through the navigation of her hub or through the app bar that follows her onto every site. The global navigation of the home site condenses the whole intranet into a few entries, a mega menu arranges columns beneath them, the hub navigation shows the sites of the area, and the menu of the individual site leads to its pages and libraries. Every entry can be targeted to an audience, so grid operations sees the link to the shift plan and administration the one to expense claims. Entries are named after tasks, not after systems or codes: everyone finds Claim expenses, only insiders find Form F-17. Navigation changes no rights, which is why we show links to closed sites only to their members.

    04

    Metadata orders documents across folder boundaries.

    On the file server every project had its path, and whoever knew it found everything. In the library the documents carry that order as columns: project number, phase, document type, validity, with values from a shared term store. Views group the same collection by customer, by phase or by year, a filter shows the current version, and search finds by the same columns. Content types bundle required fields and a template per document type and apply alike in every site. We keep folders where they separate rights or where sync to File Explorer needs them, usually one level deep. Which columns a library needs is decided by the division that fills it; how libraries, versions and search work together is in the chapter on documents and knowledge.

    05

    Multilingual sites keep one page per language.

    The safety directive applies in Olten as in Yverdon, and every person sees it in the language of their profile. On a multilingual communication site the editors create the page in the default language, SharePoint creates one copy per target language in the site pages library and notifies the assigned translators; navigation, site title and footer carry translations of their own, and when the original changes, every language version receives a notice. The language comes from the profile in Entra ID or from the browser. Every language version is a page of its own with its own approval, so every language needs a person who translates and approves. A site with two maintained languages serves employees better than one with three, of which one is out of date.

    06

    A site starts from a template and ends in the archive.

    A project team requests its workspace through a short form; a workflow creates the team and its site from the template of the project type, with a naming rule, two owners, channels and folder structure, and records it in a register. The communication site of a new division starts from the site template with navigation, page templates and audiences, and IT assigns it to the hub. At the end it is archived, not deleted: an archived team stays readable, its site can be set read-only for members, owners keep editing, and a follow-up order reactivates it. Sites nobody edits any more but that have to stay move to Microsoft 365 Archive, a cold storage tier within SharePoint where search and eDiscovery still find them. Which policies flag inactive sites and who confirms the owners is in the chapter on governance and security.

    07

    Small structured data lives in lists.

    The vehicle register, the list of open audits, the sign-ups for a training: such data lives in the intranet as a list with columns of type person, date or choice, with views, a form and rules, edited in the browser, in Teams or in the Microsoft Lists app. The list inherits the rights of its site, records every change as a version and appears on a page as a web part. Once it needs relationships between tables, many thousands of entries or a workflow with several roles, Dataverse with a Power App is the next place; when that move pays off is shown by the Business Applications pages and the article on choosing between a list and Excel.

    What you decide.

    One hub per directorate, per location or per topic?

    Options

    1. 1One hub per directorate, the locations as sites beneath it
    2. 2One hub per location, the directorates as sites beneath it
    3. 3Hubs by topic such as HR, quality and projects, across the organisation

    Our recommendation: By what survives a reorganisation. An organisation with directorates that have stood for years takes one hub per directorate; an organisation whose employees identify with their location, with plants, hospitals or branches, takes one hub per location. Topics everyone needs, such as HR and quality, become sites under the home site with their own audience in the navigation. Hub-to-hub associations connect the hubs with the home site so that search reaches across all of them, and a site changes hub with one association, which is why the first cut carries no risk.

    What we advise against: One hub per department because every department wants one: the navigation becomes as wide as the org chart, and at the next reorganisation it no longer fits.

    A project as its own site, as a team with channels or as a channel in the existing team?

    Options

    1. 1A team with one channel per work package, from the template of the project type
    2. 2A channel in the division's team
    3. 3A communication site of its own for the project

    Our recommendation: A team from the template for every project with its own lead, its own budget and several work packages: the team site comes with it, files sit with the channel where they are discussed, Loop holds agenda items and decisions, Planner the tasks, and at the end it is archived. A channel in the division's team is enough for a small undertaking without external people and without rights of its own. A communication site is added when the project has to inform many readers, such as a construction project or an office move, as a site under the hub with audiences and a pointer to the team.

    What we advise against: Creating a site of its own for every undertaking and copying the documents into an intranet folder as well: search then finds two versions, and nobody knows which one applies.

    One multilingual site or one site per language?

    Options

    1. 1One multilingual communication site with one page per language
    2. 2A site of its own per language
    3. 3One language for pages and news, directives as a document per language

    Our recommendation: A multilingual communication site for home site and hubs when your employees work in two or three national languages, with a named translator per language and the rule that a page appears only once every version is approved. A site per language only when the content differs per language region, with its own directives and its own editors. A single-language site when a second language concerns few people; the translated directives then sit as documents in the library, and the navigation carries both languages.

    What we advise against: Promising a third language that nobody translates: an outdated version does more harm than a missing one.

    Status and sources.

    As of: October 2026

    • As of 1 October 2026

      An archived team can be reactivated, a deleted one only through its group.

      Archiving stops all activity in the team and also archives private channels with their sites; channels, files and chats stay readable. Administrators can make the SharePoint site read-only for members at the same time, while owners can still edit. A deleted team only comes back if its Microsoft 365 group is restored within 30 days.

      Source: Microsoft Learn: Archive or delete a team
    • As of 17 June 2026

      Loop workspaces in channels live in SharePoint Embedded.

      A shared Loop workspace in a Teams channel stores its content in its own SharePoint Embedded container, while Loop components in channel posts sit in the channel folder of the team's site. Both count towards your organisation's storage quota. Creating workspaces is controlled by a Cloud Policy, Loop components in chats and channels by a tenant-wide setting.

      Source: Microsoft Learn: Manage Loop in your organization
    • As of 14 May 2026

      Copilot Pages and My workspace share one container.

      Copilot Pages, Copilot Notebooks and My workspace in Loop live in the same personal SharePoint Embedded container, which appears in admin tools as the application «Loop». It is created as soon as either of the two Cloud Policies allows it; to prevent it, switch off both for the same person. Each shared workspace gets a container of its own.

      Source: Microsoft Learn: Overview of Loop storage

    Frequently asked questions.

    How many hubs does our intranet need?

    As many as there are areas with several sites and a shared navigation, usually a handful at the start: the directorates or the locations, plus the home site as the hub above all of them. An area with a single site needs no hub; its site hangs directly off the home site. Hubs are added when an area gets several sites, such as a plant with quality, maintenance and logistics, and they can be set up later without any address changing.

    Can we assign a site to another hub later?

    Yes, with an association in the SharePoint admin center or through PowerShell. The site's address, links, documents and permissions stay; navigation, design and search scope follow the new hub, and from then on the site's news appears on its start page. We check the audiences in the navigation after the move, because the new hub addresses other groups.

    Where do the files of a Teams channel live, and what happens with private channels?

    In the library of the team site, one folder per standard channel, created with the folder structure of the project type; the rights follow membership in the team. A private or shared channel gets a site of its own with its own library that only the channel's members see and that appears in the admin center as the channel's site. When the team is archived, private channels are archived with their sites.

    When does a list become an app?

    When the data needs relationships between several tables, when many thousands of entries accumulate, when different roles should see different fields, or when a workflow with review and approval outgrows the list. The data then moves to Dataverse, a Power App provides the form, and the list stays as a view in the intranet or is replaced. Until then the list is enough, with views, rules and a form, in Teams too.

    How does a page get into the second national language?

    On a multilingual communication site the editors write the page in the default language and pick the target languages; SharePoint creates one copy per language and notifies the assigned translators, who translate the text in the copy and approve it. Readers see the version in the language of their profile, falling back to the default language until the translation is done. When the original changes, every language version shows that it needs updating.

    Who may create new sites and teams?

    That is set in the admin center. We recommend a request through a short form from which a workflow creates the team or site from the matching template, with a naming rule, two owners and an entry in the register; free creation by every employee is switched off. That way every site starts the same, and your IT sees which workspaces are running, which are closed and where an owner is missing.

    Next chapter · Chapter 3

    What an editorial team needs for news and pages.

    How do news and pages come about, and who keeps them current?