Microsoft Teams, governed from M‑Files
Start a project and its team is ready
A new project needs a team with the right people, and the usual folders and templates in place. CtrlTeams creates it from the project in M‑Files. The documents people make in Teams are kept in M‑Files, and are still there after the team has closed.

The project already knows what the team needs
The project in M‑Files already lists the people, the folders and the templates. CtrlTeams builds the team from that, so nobody has to enter them twice.
-
A team is there when the project starts
Connect the project and CtrlTeams creates the team and its channel in Microsoft Teams.
-
The right people are already in it
Whoever is on the project team in M‑Files becomes a member of the team.
-
Folders and templates are waiting
Your standard folder structure is created in the team, with the document templates you manage in M‑Files already in it.
-
The team's documents are kept in M‑Files
Documents made from a template, in a folder or in the channel conversation are picked up and synchronised to M‑Files with metadata.
-
The record outlives the team
When the work is done, pause or stop the synchronisation and set the conditions for archiving. The documents stay in M‑Files.
Every team laid out the way you decided

The tenth team looks like the first
People find their way around a new team because it looks like the last one. You define the folder structure once in M‑Files and apply it to a project, and its team or channel is created with the same folders in it.

People start from the templates you manage
Document templates for Teams are managed in M‑Files, so a new team starts with the versions you keep there and last year's copy stays in last year's project. People can still create a document the ordinary Teams way, and CtrlTeams picks that up too.
Who gets the most out of it
IT and compliance know who had access
Each team and channel is kept as a record in M‑Files, with the project it belongs to, and its permissions are set there. Opening or changing a document leaves an audit trail, so when somebody asks which teams exist and who could open what, you look it up.
Project organisations start every project alike
Each project team starts from the same template, with the same folders and the baseline documents in place. After delivery the project's documents are kept where people can find them.
Regulated sectors keep records where policy requires
In sectors such as pharma and finance, keeping records is a requirement. Archiving conditions preserve the records when a team closes, and storage stays where your policy needs it.
What it needs to run
Any M‑Files edition, in M‑Files Cloud or on-premise, with M‑Files 25.1 or later on the server and in the clients.
CtrlTeams needs Microsoft Azure, with the Microsoft Graph permissions that let it create teams and read and write their channels, members and files.
The permissions and the set-up guide are in the CtrlTeams documentation. We go through anything else your installation needs with you when we plan it.
Questions about CtrlTeams
Why create the team from M‑Files instead of in Teams?
Do people have to use the templates?
How is this different from CtrlSync?
How is access to a team controlled?
Where do the documents go when the project ends?
Can it take over the teams we already have?
Is there a trial?
More CtrlDocs add-ons for M‑Files

CtrlPortals
Dashboards and UI that make M‑Files yours
Record pages, forms, boards and dashboards inside M‑Files, set up around your own records for any process. Open a project, a customer or a document and see everything that belongs to it.
See CtrlPortals
CtrlShare
Co-author in Office on any M‑Files, cloud or on-premise
Open an M‑Files document for colleagues and outside parties to edit together, in desktop Office or the browser. It comes back to M‑Files as a new version.
See CtrlShareCtrlScout
AI for your M‑Files vault, cloud or on-premise
Ask your M‑Files vault in plain words. CtrlScout finds the records, counts and charts them, summarises documents, drafts the email and suggests the details for a new document. It only sees what you can see.
See CtrlScoutCtrlProcesses
Show your people how the work is done, inside M‑Files
Your Elements.cloud process maps inside M‑Files. Every step leads to its procedure, the record it produces and the standards that apply.
See CtrlProcesses
CtrlSync
Teams and SharePoint, filed with metadata and rights
People work in Teams or SharePoint, and the documents you want kept are copied to M‑Files with metadata, filed under their project with the access rights preserved.
See CtrlSync
CtrlConnect
M‑Files details, right inside Teams and Outlook
An M‑Files link pasted into Teams or Outlook shows the record's title and description, and in Teams it comes with buttons that open the record. You can also search M‑Files from the Teams chat, on a phone too.
See CtrlConnect
CtrlTime
Time tracking where the work happens
Record hours in a calendar inside M‑Files, on the customer or project they belong to. Approved weeks feed payroll, invoicing and project follow-up.
See CtrlTime
FancyLinks
M‑Files links with the details built in
M‑Files links that show which document and which version they point to, and open it directly. Free to use.
See FancyLinks