# Engineering Subconsultants: Standard, Private or Shared Channel?

Give subconsultants a dedicated project team or a shared channel. A private channel needs team membership first, which can expose your other projects.

Comparison · 2026-11-18 · Chrysis Networks · [chrysisnetworks.com/blog/engineering-subconsultant-drawing-access-standard-private-shared-teams-channel](<https://chrysisnetworks.com/blog/engineering-subconsultant-drawing-access-standard-private-shared-teams-channel>)

![Engineering Subconsultants: Standard, Private or Shared Channel?](<https://chrysisnetworks.com/resources/images/blog/engineering-subconsultant-drawing-access-standard-private-shared-teams-channel.jpg>)

## For a 60-person engineering firm, which Teams channel keeps subconsultants out of our other projects?

Use a dedicated Teams team for each project and put the subconsultant in it, or use a shared channel when their IT admin can set up cross-tenant access. A private channel alone doesn't wall anyone off, because Microsoft only lets guests into a private channel once they're members of the parent team, and team members see every standard channel in it. The channel type controls who sees the conversation; file permissions still need their own check.

Most engineering firms hit this question the first time a structural or MEP subconsultant needs the current drawing set. Somebody adds the outside engineer to whichever team already exists, and that team usually holds more than one project.

## How standard, private and shared channels compare for subconsultant access

Microsoft's documentation sets out what each channel type allows. Matching those rules to engineering project work is our reading of that documentation, not a Microsoft recommendation written for engineering firms.

- Standard channel fits when everyone in the project team, guests included, is allowed to see everything in it, which is easiest in a team built for a single project; avoid when the team holds several projects, because every team member can open every standard channel.
- Private channel fits when a smaller group inside a team needs its own space, and guests can join once they're already members of that team; avoid when admitting the subconsultant to the parent team would itself show them unrelated standard channels.
- Shared channel fits ongoing work with a partner whose IT admin can configure Microsoft Entra B2B direct connect on their side as well as yours, so the partner never joins your parent team; avoid when you're counting on an existing guest account or the partner can't complete the cross-tenant setup.

![One firm's project teams shown as separate walled rooms, with a single bridged channel connecting one room to a partner firm's building](<https://chrysisnetworks.com/resources/images/blog/engineering-subconsultant-drawing-access-standard-private-shared-teams-channel-1.jpg>)

## Our recommendation for a 60-person engineering firm

One team per project is the cleaner default. Add subconsultants to that team as guests and keep drawings in a standard channel that everyone on the team is allowed to see. Create a private channel inside the project team only when a smaller group, such as your own staff discussing fees, needs a space the subconsultant shouldn't reach. A private channel inside a broad, multi-project team should never be the confidentiality boundary for an outside firm.

One condition changes the answer: whether the subconsultant's IT admin can complete Microsoft Entra B2B direct connect with your tenant. When they can, and you work with that firm across several projects, a shared channel lets their people collaborate on one project without being added to the parent team at all. When they can't, the dedicated project team with guests is the route that works.

Leaving the setup to habit carries a real cost on live jobs. A subconsultant dropped into a multi-project team can read standard channels about clients they've never worked for. When access fails in the other direction, the project manager starts emailing drawing sets, and before long nobody can say which revision the subconsultant is marking up. Chrysis sets up the per-project pattern and runs the access tests for firms in exactly this spot, so you can [keep every subconsultant on the current drawings without exposing other projects](<https://chrysisnetworks.com/services/microsoft-365-workflow-automation>).

## Channel membership is not the whole file-access design

Private channel files live on their own SharePoint site, and Microsoft's private channels page (last updated 2026-10-01) says site permissions for a private channel site can't be managed independently through SharePoint. Membership is managed through Teams, so tightening access means changing the channel's members rather than editing the site.

Removing someone from a shared channel does not always end their file access. Microsoft's shared channels page (last updated 2026-02-20) states that when a user is granted access to a file, folder or notebook in a shared channel through SharePoint, removing the user from the team or shared channel won't remove that access. Choosing the right channel and removing members at closeout are two separate jobs, and the second one needs its own review.

## Five checks before live drawings go into the channel

1. Name one owner for the project team or shared channel, usually the project manager, and write down the allowed audience: your staff on the project plus the named people from each subconsultant.
2. For a shared channel, confirm with the subconsultant's IT admin that Microsoft Entra B2B direct connect is configured on both sides; Microsoft's shared channels page says each organization you share channels with must also complete that configuration.
3. Have one representative external participant sign in with their own account and open the exact drawing file you intend to share, and record the result.
4. Have someone who should not have access, such as a colleague on a different project, try the same file and confirm they're refused.
5. At project close, remove the external members, then review the files and folders for direct SharePoint grants, because removing someone from the team or shared channel doesn't remove access granted directly to a file or folder.

Until those checks pass, a manual route keeps the job moving. A named project manager keeps the drawing-transmittal register and sends the current revision through the firm's already-approved, access-controlled file route. An Anyone link is the wrong fallback for confidential drawings, because the link works for whoever holds it.

None of the cited pages announces a new feature or effective date. The private channels page was last updated 2026-10-01, the teams and channels overview 2026-08-07, and the shared channels page 2026-02-20. The pages also disagree on one detail: the private channels page says private channels now support channel meetings, while the overview's comparison table still marks scheduled meetings as unsupported there. Test meetings in your own tenant before relying on them, and don't pick a channel type on that basis.

## Frequently asked

### Can a guest join a private channel without joining the team?

No. Microsoft says anyone, including guests, can be added to a private channel as long as they're existing members of the team.

### Is a guest account enough for a subconsultant to join a shared channel?

Don't assume so. Shared channels with another organization depend on Microsoft Entra B2B direct connect, and both organizations have to configure it.

### Does removing a subconsultant from the channel end their file access?

Not always. Access granted to a file, folder or notebook through SharePoint stays after the person is removed from the team or shared channel, so review direct grants at closeout.

### Can we lock down a private channel's files directly in SharePoint?

No. Microsoft says private channel site permissions can't be managed independently through SharePoint; manage membership in Teams.

### What do we use while channel access is still being tested?

The project manager sends the current revision through your approved, access-controlled file route and logs it in the transmittal register, never through an Anyone link.

## Have a handoff that keeps slipping?

Tell us where work sits between people or systems in your business. We'll show you what it takes to make it move on its own, with what you already pay for where that's enough. [Describe the handoff](<https://chrysisnetworks.com/#contact>)

## Sources

- [Private channels in Microsoft Teams (Microsoft Learn)](<https://learn.microsoft.com/en-us/microsoftteams/private-channels>)
- [Overview of teams and channels in Microsoft Teams (Microsoft Learn)](<https://learn.microsoft.com/en-us/microsoftteams/teams-channels-overview>)
- [Shared channels in Microsoft Teams (Microsoft Learn)](<https://learn.microsoft.com/en-us/microsoftteams/shared-channels>)

## Related reading

- [Keep subconsultants on the current drawings without exposing other projects](<https://chrysisnetworks.com/services/microsoft-365-workflow-automation>)
