Book a demo
To see exactly how we can help you drive your company in the right direction, book a demo with an expert.
Book a demo
Collaboration Integration
CMap + Microsoft Teams
Every project gets its Team, its channel and its files.
Created in your own Microsoft 365 tenant, named your way, with the project team already inside.
Linked straight back to the project in CMap.
Projects & delivery
Confirm on save
Teams & channels
Right people, added automatically
Document folders ready
Teams & SharePoint
Workspaces ready
What syncs
Teams, channels, owners & members, and SharePoint document folders
How it runs
On project save, when you confirm you want a Teams channel. One-way, through the Microsoft Graph API
Works with
Your own Microsoft 365 tenant. Org-wide admin approval, no per-user sign-ins
Included in
CMap Consulting & AEC editions, as a core integration
What the integrations does
Confirm once. Get the whole workspace.
Save a project in CMap and the collaboration space is built for you: the Team, the channel, the right people and the document folders, all in your own Microsoft 365 tenant.
CMap
→
Microsoft Teams
CMap
↔
Microsoft Teams
Microsoft Teams
→
CMap
Teams & channels
Confirm you want a Teams channel when you save a project, and CMap creates the workspace in Microsoft Teams: a Team per client with a channel per project, or a Team per project. You choose the structure, and how project channels are named.
CMap
↔
Microsoft Teams
Microsoft Teams
→
CMap
CMap
→
Microsoft Teams
Right people, added automatically
The project owner, project manager, co-pilots and creator become Team owners; the project team become members, matched to your Microsoft 365 users automatically by email address.
CMap
↔
Microsoft Teams
Microsoft Teams
→
CMap
CMap
→
Microsoft Teams
Document folders ready
CMap creates the project's folder structure in the Team's SharePoint drive, and the project's Documents page in CMap is backed by that same drive, so files live in one place.
Why it matters
No IT tickets. No hand-built Teams.
CMap runs your projects; Microsoft 365 runs your collaboration. This integration means every project starts with its workspace already in place.
No workspace admin
The collaboration space spins up the moment the project is saved. No IT tickets, no creating Teams by hand.
Tidy and findable
An admin-set naming convention means every Team and channel is named consistently, so nothing gets lost.
Right people from day one
Owners and members come straight from the project team in CMap, so there is no chasing people to join.
One home for project files
Documents live in the Team's SharePoint drive and surface on the project's Documents page in CMap, so files live in one place.
getting set up
Approved once. Then just a confirmation.
This is a core CMap integration: built, supported and maintained by CMap, connecting securely to Microsoft 365 through the Microsoft Graph API. Approve CMap's app once for your whole organisation and from then on project managers simply confirm they want a Teams channel when saving a project. The full setup guide walks through every step.
Approve CMap's app
Your Microsoft 365 administrator approves CMap once for the whole organisation. No per-user sign-ins.
Choose your structure
An admin picks the Team structure and the project channel naming convention in CMap's settings.
Confirm on save
When saving a project, project managers confirm they want a Teams channel created.
Frequently asked questions
Who builds and supports the integration?
CMap. It is built, supported and maintained by CMap, connecting securely to Microsoft 365 through the Microsoft Graph API. Your Microsoft 365 administrator approves CMap's app once for the whole organisation, with no per-user sign-ins.
Which CMap editions include the Microsoft Teams integration?
It is a core CMap integration, available on both the Consulting and AEC editions.
Can we control how Teams and channels are named?
Yes. An admin chooses two things in CMap's settings. First the structure: a Team per client with a channel per project, or a Team per project. Then how project channels are named: project title; project number and title; client name and title; or client name, project number and title. Every Team and channel is then named consistently, so nothing gets lost.
Where do the Teams and files live?
In your own Microsoft 365 tenant. CMap connects securely through the Microsoft Graph API and creates the Teams, channels and SharePoint folders inside your organisation's environment, then stores the link on the project so your team jumps straight from CMap to the channel.
Does CMap read our Teams chats, meetings or calendars?
No. The integration is one-way creation only. CMap creates Teams, channels, members and SharePoint document folders when a project is saved, stores the link on the project, and never reads chats, meetings or calendars. It also never changes a Team after it is created.
integrations
CMap, embedded in your wider tech stack
Microsoft Teams is one of CMap's core integrations, connecting project delivery to the tools your business already runs on, alongside your accounting, CRM and HR systems.
View all integrations
