How to Add a SharePoint List to Microsoft Teams (and Keep Permissions Safe)

Adding a SharePoint list to a Teams channel is straightforward. The part that catches people out is what the tab does not do: it does not move the list into Teams, create a second copy, or grant access to everyone who can see the tab.

The list remains a SharePoint list. SharePoint stores the data and enforces the permissions. Teams gives people a convenient way to open and work with that list inside a channel.

The short answer

On the Teams desktop or web app:

1. Open the team and channel where you want the list.
2. Select the + button in the channel tab bar.
3. Choose Lists.
4. Select Create a list or Add an existing list.
5. Choose the list, give the tab a clear name, and save it.
6. Test the tab as an ordinary member, not just as a site owner.

Microsoft documents the Lists app as available from the tab gallery in every team and channel. It can create a new list or pin an existing list from the same team or another SharePoint site the user can access.

That final access test matters. A tab is a signpost to a resource; it is not a permission grant.

Before you add the tab, decide which list you are using

There are three common cases.

1. Create a new list for this team

This is the simplest option when the data belongs to the team. You can start from a blank list, a Microsoft template, an existing list’s structure, or an Excel workbook where that import option is offered.

The new list is stored in the team’s SharePoint site. By default, its permissions inherit from that site.

2. Add a list that already belongs to the team

Use this when the list already lives in the team-connected SharePoint site. The tab exposes the same list; it does not duplicate the rows, views, rules or permissions.

3. Add a list from another SharePoint site

Microsoft says users can pin a list from a different SharePoint site if they already have access to it. This can be useful for a central risks, assets or requests list shared by several teams.

It also creates a governance dependency: the channel and the list now have different membership lifecycles. Someone can join the team yet still receive an access-denied message at the tab. Conversely, someone may retain direct SharePoint access after leaving the team.

Use an external list only when that separation is deliberate. For a list that should follow team membership, storing it in the connected site is usually easier to reason about.

Add an existing SharePoint list as a Teams tab

The labels can move as Teams evolves, but the supported route is the Lists or SharePoint tab—not a pasted list URL inside a generic website tab.

1. Open Teams on desktop or the web.
2. Open the destination channel.
3. Select + Add a tab.
4. Choose Lists. If it is missing, ask your Teams administrator to check whether the app is allowed.
5. Select Add an existing list.
6. Choose the list offered in the picker, or supply the SharePoint list link if the dialog provides that route.
7. Confirm the tab name and save it.

Microsoft also documents a broader SharePoint route for adding a SharePoint page, list or document library as a Teams tab. If one app is unavailable in your tenant, check the other supported tab experience rather than wrapping the page in a Website tab and assuming it will behave identically.

What happens to permissions?

SharePoint remains the authority.

Microsoft’s current Lists guidance says that permissions set in SharePoint apply to lists used in Teams and that lists inherit from their site by default. The Teams tab does not turn a reader into an editor and does not make a private list visible to a whole channel.

Before announcing the tab, test these roles:

• a normal team member who should edit items;
• a read-only user, if that role exists;
• a guest, if guests are in scope;
• a user who can see the channel but should not see the list;
• a site owner, to confirm the administrative path still works.

If the list uses unique permissions, document why. Unique permissions can be valid, but they create another access model to maintain. Avoid “fixing” a Teams access error by granting broad site access until you know which SharePoint group or item-level setting is actually responsible.

Teams membership and SharePoint list permissions are related, but not interchangeable

For a normal team-connected site, team membership commonly affects access to the connected SharePoint site. But Microsoft’s Lists documentation explicitly warns administrators not to treat the owner/member labels in Teams as a complete description of what people can do to a list. SharePoint permission levels, inheritance and direct sharing still matter.

For private and shared channels, file and site architecture differs from a standard channel. Review Microsoft’s Teams-connected sites and channel types before designing a list or permission model around channel membership.

Desktop, web and mobile: the current boundary

Lists has desktop, web and mobile experiences, but the setup path is not identical.

Microsoft currently states that users cannot create a new list or pin an existing list from the Teams mobile client. Create or add the tab in Teams desktop or web first; users can then view or edit the list on mobile, subject to their permissions and the features available in that client.

Do not promise pixel-for-pixel or feature-for-feature parity across clients. If mobile working matters, test the real list, its views, required columns, formatting and any customised form on the managed devices your users have.

Guests and people outside the team

Microsoft’s Lists admin guidance says guests cannot create or delete a list. They can work with items and list-item conversations where access allows.

That does not mean every guest automatically has access to every tab. Check:

• whether guest access is enabled for the team;
• whether the guest can open the underlying SharePoint site and list;
• whether the list inherits permissions or uses unique permissions;
• whether a sensitivity label, conditional-access rule or sharing policy blocks the journey;
• whether the list lives in a different site from the team.

Test with a real guest account. An owner’s successful view proves only that the owner can open it.

Forms, views, rules and automation

A Teams tab is useful for everyday list work, but it does not make every SharePoint design sensible.

Views

Create views around a task: My open requests, This month’s renewals, or Items needing approval. A well-scoped view is more valuable than dropping a wide administrative list into a small Teams canvas.

Views are presentation, not security. Hiding a row or command in a view does not remove the underlying permission.

Custom forms

Microsoft Lists can use forms customised with Power Apps. Treat the Teams client as a separate test surface: verify new, view and edit behaviour, required fields, attachments, validation and responsive layout before rollout. Do not assume that a form which works in a full browser will behave perfectly inside every Teams client.

Notifications

Microsoft’s published schedule says SharePoint Alerts are being removed starting in July 2026. For maintained notification scenarios, use a supported SharePoint rule or a deliberately owned Power Automate flow.

Choose the lightest tool that meets the requirement. A simple “notify me when this column changes” rule does not always need a large flow. For business-critical automation, define an owner, failure monitoring and a recovery path.

A safer rollout checklist

Use this before exposing a list to a busy channel:

1. Name the owner. Who owns the list structure, permissions and automation?
2. Confirm the source. Is this the correct list, site and environment?
3. Review access. Does it inherit from the site? If not, why not?
4. Create task-focused views. Do not make users decipher an admin view.
5. Check required fields and validation. Test new and edit operations.
6. Test desktop, web and required mobile devices. Record genuine limitations.
7. Test as a member and guest. Do not rely on the owner account.
8. Document automations. Include connections, owners and failure handling.
9. Announce the purpose. Tell the channel what belongs in the list and what does not.
10. Review after launch. Look for permission exceptions, unused views and duplicate trackers.

Troubleshooting a Lists tab in Teams

The Lists app is not in the tab gallery

Ask a Teams administrator to check the app in Teams apps > Manage apps and the policies assigned to the affected user. Lists is enabled by default, but an organisation can block it.

The tab opens for an owner but not for members

Open the underlying list in SharePoint as an affected member. Check site membership, list inheritance, direct sharing and any item-level restrictions. Do not delete and recreate the tab until you know whether the failure is navigation or permission-related.

The list is missing from the picker

Confirm that the user can open the exact list in SharePoint. Check that you are in the intended team and channel, and use the supported link option if the picker offers it. A list in another tenant or an inaccessible site will not become available because its URL is known.

Mobile users cannot create or add the list

This is a documented client limitation. Add the list from Teams desktop or web, then test viewing and editing from mobile.

A custom form behaves differently in Teams

Reproduce the issue with the default SharePoint form before changing production. Then check the customised form’s responsive design, formula errors, connectors and permissions. Keep a rollback path to the standard form.

Frequently asked questions

Does adding a SharePoint list to Teams copy the data?

No. The tab opens the existing SharePoint list. Its data, views and permissions remain in SharePoint.

Does everyone in the channel automatically get access?

No. The underlying SharePoint permissions still decide who can open or change the list.

Can I add a list from another SharePoint site?

Yes, Microsoft supports pinning an existing list from another SharePoint site when the user already has access. Plan for the separate membership lifecycle.

Can I create or add the tab from Teams mobile?

Microsoft currently says no. Create or pin the list from Teams desktop or web first; mobile users can then work with it where supported.

Should I use a Website tab for a SharePoint list?

Use the native Lists or SharePoint tab where possible. A Website tab is a generic web surface and should not be presented as equivalent to the supported list integration.

Keep the implementation current

Microsoft changes the clients, admin controls and service boundaries. A list that matters to a business process needs more than a one-off tab setup.

The Teams, SharePoint & Intranet Mastery Space brings current Microsoft changes, practical admin patterns and troubleshooting into one maintained place.

The durable rule is simple: Teams is the working surface; SharePoint remains the data and permission boundary.