How to Create a SharePoint Site: Step-by-Step Guide (Team vs Communication Site, Setup and Permissions)

How to Create a SharePoint Site: Step-by-Step Guide (Team vs Communication Site, Setup and Permissions)

Learn how to create a SharePoint site step by step: pick team or communication site, set privacy and owners, and configure permissions, navigation and hubs.

In this article

Let's Discuss your tech Solution

book a consultation now
November 20, 2026
Author Image
Sharjeel Hashmi
SharePoint & .NET Team Lead
Sharjeel Hashmi is a SharePoint & .NET Team Lead at Centric, with extensive experience in designing, developing, and leading enterprise-level solutions. He specializes in building scalable SharePoint platforms and robust .NET applications that align technology with business objectives. With a strong focus on collaboration, performance, and security, Sharjeel leads teams to deliver high-quality solutions while driving continuous improvement and best development practices. His expertise spans solution architecture, team leadership, and modern Microsoft technologies, enabling organizations to streamline processes and achieve long-term digital success.

Someone has asked you for a site for a team, a project or company news, and you need it set up correctly the first time. Here's how to create a SharePoint site in short: sign in to the SharePoint start page, select + Create site and choose a team site or a communication site. Then pick a template, name the site, set privacy and language, and add owners and members.

This guide is for Microsoft 365 admins, IT managers and business users with site-creation rights. It covers choosing the site type, the eight steps, the Teams and admin center routes, post-creation setup, mistakes to avoid, choosing a structure and when a partner makes sense.

Before the steps, you need to know which site type fits.

What a SharePoint Site Is and the Types You Can Create

What is a SharePoint site? It's a web-based workspace in Microsoft 365 that holds pages, document libraries, lists, news posts and its own permissions. Think of it as a shared building: the home page is the lobby, libraries and lists are the rooms, and permissions are the keycards that decide who gets into which room. If you need the wider context first, start with how Microsoft SharePoint works.

Technically, every modern site is its own site collection, which is the name the admin center used to give sites. If older documentation or scripts still use that term, here's what a site collection is.

There are two main types you'll create:

  • SharePoint team site: built for collaboration. It's connected to a Microsoft 365 group, so it comes with a shared mailbox, a calendar and the option to add Microsoft Teams. Most members edit content.
  • SharePoint communication site: built for broadcast. It isn't group-connected. A few authors publish to many readers.

A hub isn't a third type. It's a layer that connects existing team and communication sites with shared navigation, branding and search, and only a SharePoint admin can register one.

In one line: you choose between two types, and a team site also creates a Microsoft 365 group while a communication site doesn't. Here's how they compare, with hubs alongside:

 

Team site

Communication site

Hub site

Purpose

Collaboration on shared work

Publishing news and info to a wide audience

Connecting related sites

Audience

A defined group (team, project)

Department, division or whole company

All sites in a family (e.g. all HR sites)

Who edits / who reads

Most members edit

Few authors, many readers

Set per associated site

Default permissions

Microsoft 365 group owners and members

SharePoint Owners, Members and Visitors groups

Each site keeps its own permissions

Microsoft 365 Group

Yes

No

n/a (it is a setting, not a site type)

Teams connection

Can be connected to a team

No

No

Typical use

Project files, team docs, lists

Intranet home, HR policies, news

Department portal grouping several sites

Before You Start: Licensing, Rights and Tenant Settings

Check three things before you click anything, so you don't go looking for a button that isn't there.

  • Licence: each user needs a Microsoft 365 or SharePoint Online plan that includes SharePoint.
  • Rights: by default, users can create sites from the SharePoint start page. Users with at least SharePoint Administrator permissions can always create sites from the SharePoint admin center.
  • Tenant setting: your admin controls whether users can create sites. If you don't see + Create site, ask them.

These steps apply to SharePoint in Microsoft 365 (SharePoint Online). If your organization still runs on-premises servers, read how SharePoint Online and SharePoint Server differ, because the creation process isn't the same.

Need help setting up SharePoint?

Centric SharePoint consulting services cover licensing, tenant setup, site structure, and permissions.

Explore Our SharePoint Services

How to Create a SharePoint Site in 8 Steps?

To create a SharePoint site, sign in to Microsoft 365 and open the SharePoint start page. Select + Create site, choose Team site or Communication site, then pick a template and select Use template. Enter a name, description and address, set privacy and language, select Create site, add owners and members, and select Finish.

Here's the full click path to create a new SharePoint site from the start page:

  1. Sign in and open the SharePoint start page. Open the Microsoft 365 app launcher and select SharePoint.
  2. Select + Create site. If the button is missing, self-service creation is turned off in your tenant. See the section above.
  3. Choose Team site or Communication site. Use the table above if you're unsure.
  4. Pick a template and select Use template. Microsoft recommends the new site templates for all new sites. On communication sites, templates set the layout (for example, topic or showcase). On team sites, they add pre-built pages and lists.
  5. Enter the name, description and site address. Apart from letters and numbers, the address accepts only underscores, dashes, single quotes and periods, and it can't start or end with a period. Team sites also show the group email address, which you can edit. If the address is taken, SharePoint offers a modified one, such as /sites/marketing2. Decide the address now, because changing it later is an admin task.
  6. Set privacy and language. Privacy applies to team sites only: choose Private unless the whole organization should see the content. Pick the language carefully, because on classic templates it can't be changed once set.
  7. Select Create site, then add owners and members. Add at least one more owner besides yourself. Modern sites are typically ready to use within seconds.
  8. Select Finish. The site opens on its home page.

Because Microsoft uses targeted release to roll out changes gradually, a label or layout in your tenant may differ slightly from the steps above.

The start page isn't the only route. Two others are worth knowing, depending on whether a team already exists or an admin controls provisioning.

Create a Site from Microsoft Teams

When you create a team in Microsoft Teams, it automatically creates a group-connected team site. Files shared in standard channels (the Files tab) are stored in that site, while private and shared channels get sites of their own. The trade-off: you can't choose a communication site, and naming and privacy are set from Teams.

Create a Site from the SharePoint Admin Center

Admins provisioning sites for others go to Active sites > Create, then choose Team site, Communication site or Browse more sites. Pick a template, select Use template, enter the name, owner and language, and select Create site.

This route lets you assign a different primary owner, and classic templates live under Browse more sites. For bulk creation, PowerShell is the better tool. If the admin center is new to you, take a tour of the SharePoint admin center first.

Set Up Your New Site: Permissions, Navigation and Hubs

A created site isn't a ready site. Here's how to set up a SharePoint site so people can use it safely and actually find things, before you invite anyone.

Permissions come in three default levels. Owners have full control, Members can edit, and Visitors can read only. On team sites, Owners and Members map to the Microsoft 365 group, so adding someone to the group gives them site access.

Assign at least two owners. A single-owner site becomes orphaned the moment that person leaves or changes role, and someone in IT ends up untangling it.

Break permission inheritance only for a specific library or folder that needs tighter access, such as HR or finance documents. The how and when are covered in our full site permissions tutorial.

To build a SharePoint site people will use, edit the home page first: add news, quick links and a document library web part, and remove the sample content. Keep top-level navigation to 5-7 links. If your admin has registered a hub, associate the site with it from Site information in the settings menu.

Setup checklist before you invite users:

  • Site name and address follow your naming convention.
  • At least two owners are assigned.
  • Members and Visitors are added through groups, not individuals, where possible.
  • The home page has been edited and default placeholder content removed.
  • Navigation is set (5-7 links).
  • The site is associated with a hub, if one applies.
  • Sensitivity label and retention policy are applied, if your organization uses them.
  • External sharing is checked against policy.

Common Setup Mistakes to Avoid

These are the setups admins most often end up rebuilding:

  • One site for everything. Permissions and navigation become unmanageable as the site grows. Fix: one site per team or project, joined by a hub.
  • Breaking inheritance everywhere. It causes permission sprawl and access you can't audit. Fix: break it only at library or folder level, and only when you must.
  • No naming convention. You end up with duplicate, confusing addresses like marketing2 and marketing3. Fix: agree a prefix pattern (for example, dept-, proj-) before rollout.
  • Single-owner sites. They become orphaned. Fix: two owners minimum, with a regular ownership review.

Creating the site takes minutes. Choosing the structure is where setups go wrong.

How to Choose the Right Site Structure?

The table above shows what each type is. This section helps you decide which one fits, which route to create it from, whether to use a template and how many sites you actually need.

Team Site vs Communication Site: Decision Criteria

For most readers, the SharePoint team site vs communication site choice comes down to five questions:

  • Who authors and who reads? If most people contribute, choose a team site. If a few people publish to many, choose a communication site.
  • Do you need a mailbox, calendar or Teams team? If yes, choose a team site.
  • Is it collaboration or broadcast? Shared drafting and project work point to a team site. Announcements, policies and news point to a communication site.
  • How big is the audience? Department-wide or company-wide readership points to a communication site.
  • How should permissions work? If access must be managed separately from group membership, choose a communication site.

Can you change a team site to a communication site later? There's no simple switch between types for a modern group-connected team site, so pick the type before you create it. That's why the SharePoint communication site vs team site decision belongs before step 1, not after.

SharePoint vs Teams: Where Should the Site Start?

The SharePoint vs Teams question is less about storage than about where people work, because Teams files already live in a SharePoint team site. If the group chats and meets daily, create the team in Teams. If the site is mainly documents or pages with light chat, create it from SharePoint.

Best for, by route:

  • SharePoint start page: standalone sites.
  • Teams: when a team already exists or chat is central.
  • Admin center: governed, admin-controlled provisioning.

Either way, it helps to understand how Teams and SharePoint connect before you settle the Teams site vs SharePoint site question for your organization.

Use a Template or Start Blank?

A SharePoint site template gives you a faster start, with pre-built pages, lists and web parts. The cost is sample content to remove and a layout that may not fit your needs. Starting from the standard template gives you a clean structure but takes more setup time.

Use a template when one closely matches the use case, such as a department or project site. Start from the standard template when you're building your own structure. In both cases, choose from the new templates rather than the classic ones, as Microsoft recommends.

One Big Site or Many Connected Sites?

Create one site per team or project and join related sites with a hub. Split a site when audiences differ, when permissions differ, or when a library grows past the point where people can find things.

External access is a structural factor too. Keep externally shared content in its own site, so guest access never reaches internal libraries. The mechanics are covered in our guide to sharing a site with external users.

When the plan runs past five or six sites, settle the structure with whoever governs your tenant, or an outside advisor, before the first site goes live.

Out-of-the-Box Site or Custom Portal?

Standard sites go a long way, but not everywhere. An out-of-the-box site fits a single team, a project, or a simple communications hub with standard branding.

A custom portal or intranet fits when you need:

  • Many departments under one navigation.
  • Strict branding.
  • Integrations such as HR systems, CRM or Power BI.
  • Personalized content for different audiences.
  • Formal governance with defined owners and review cycles.

Timeframes depend on scope. At Centric, a single-purpose portal typically takes 4-8 weeks, and a ready-built SharePoint intranet portal deploys in 8 weeks or less.

Be honest with yourself about the limitation: a custom build needs ongoing ownership and maintenance. If no one will own it after launch, standard sites with a hub are the safer choice.

If your requirements go past what a template covers, here's when a partner makes sense.

When to Bring In a SharePoint Partner?

Most single sites never need outside help. These are the signs you need a partner, not a template:

  • Several hundred or more users.
  • Multi-site navigation, a hub structure or a branded intranet.
  • Complex permission requirements.
  • Migration from file shares or an older SharePoint version.
  • Custom web parts or Power Platform workflows.
  • Compliance requirements such as retention, sensitivity labels or audit.

A SharePoint consultant typically works in phases: discovery and information architecture, build, migration, governance, then training and adoption. Good SharePoint consulting services start with the architecture, because that's what every later phase depends on.

Partners split the work in two ways. SharePoint implementation services cover rollout and migration. SharePoint development services cover custom SharePoint portal builds and web parts.

Cost depends on scope: the number of sites and users, migration volume, integrations and custom development. Any honest figure comes from a scoping conversation, not a price list. Microsoft licensing is billed separately from partner fees.

Who should do the work?

  • In-house fits small, stable needs with SharePoint skills on staff.
  • A freelancer fits a single, well-defined build.
  • An agency fits multi-phase work that needs architecture, migration and support together.

A partner reduces four common risks. Permission sprawl is limited by a permission model designed before build. Orphaned sites are prevented by ownership rules set from day one. Lost metadata in migration is guarded against with mapping and test runs. Low adoption is addressed with training planned into the rollout rather than added afterwards. None of this promises an outcome, but it removes the usual causes of rework.

Setting up More Than a Single Site?

Tell us how many sites, users and integrations you have in mind, and Centric SharePoint team will scope the architecture, migration and governance with you.

Book a SharePoint Scoping Call

SharePoint Site FAQs

Is SharePoint still relevant in 2026?

Yes. SharePoint remains the document and content layer behind Teams files, OneDrive file sharing and Microsoft 365 intranets, so most Microsoft 365 organizations use it whether they open it directly or not.

How easy is it to learn SharePoint?

Creating a site takes minutes with the steps above. Structure, permissions and governance take longer to get right, and that's where most of the learning curve sits.

What are the two types of SharePoint sites?

Team sites, which are for collaboration and connected to a Microsoft 365 group, and communication sites, which are for broadcasting to a wide audience. Hubs connect both but aren't a third type.

Can you create a SharePoint site for free?

Site creation needs a Microsoft 365 or SharePoint plan that includes SharePoint. Check Microsoft's current plan options with your admin before you budget for it.

Key Takeaways: Creating a SharePoint Site

Pick the type first: a team site for collaboration, a communication site for broadcast. Then follow the eight steps, which is all it takes to learn how to create a SharePoint site from the start page. Before you invite anyone, set at least two owners, keep navigation tight and associate the site with a hub where one exists.

Structure matters more than clicks. A clear naming convention, one site per team or project and permissions you can audit will save far more time than any template. For deeper guides on permissions, sharing and the admin center, and for help when a setup grows into an intranet or migration, the Centric SharePoint team is a good next stop.

Contact_Us_Op_02
Contact us
-

Spanning 8 cities worldwide and with partners in 100 more, we're your local yet global agency.

Fancy a coffee, virtual or physical? It's on us – let's connect!

Contact us
-
smoke effect
smoke effect
smoke effect
smoke effect
smoke effect

Spanning 8 cities worldwide and with partners in 100 more, we're your local yet global agency.

Fancy a coffee, virtual or physical? It's on us – let's connect!