Projects in Microsoft Teams and SharePoint
Every project gets a consistent Microsoft Teams folder structure based on your requirements. Access follows your company roles and groups, from Active Directory to Teams and SharePoint. TeamsFlow prepares a permission change plan and applies it after your approval.
Book a demo
Everyday work
Projects often need the same folder structure, but different teams need access to different documents. We configure TeamsFlow around your company’s folders and roles. New projects follow those rules, while staff continue working with files in Teams and SharePoint.
Less manual setup
TeamsFlow / How it helps
Folders and AD / Entra groups
Consistent folders and access in Teams
TEAMSFlow IN ACTION
See your projects and their status at a glance. From here, create another project or review who can access its folders.
TeamsFlow
Enter a name in the agreed format. TeamsFlow creates the project in the correct year folder, adds standard subfolders and assigns access.
Use a text file of project names for batch creation. Check naming and duplicates without changing Teams, then review the results after creation.
Map your Active Directory groups, available in Microsoft Entra ID, to project folder permissions. Give each role read, write or no access. Finance works with invoices; project teams work with documentation. This is role-based access control — RBAC.
Select one project, a year or the full project structure. TeamsFlow compares current access with your configured rules and prepares the required changes.
Plan compares current permissions with your policy and shows access to add, change or remove. Apply executes the prepared changes only after confirmation. You review the impact before running the update.
Managed groups can work in their assigned subfolders. Read-only access at project level prevents them from renaming the project or adding folders alongside the standard structure.
View all projects, active projects or archived projects. When choosing a project to archive, search by part of its name.
TeamsFlow downloads the project to the designated archive folder and marks it as archived in Teams. Managed groups receive read-only access, while folders they could not access remain restricted.
Bring existing project access into line after rule changes or manual edits. Choose the review scope first, then approve updates using the displayed plan.
Your environment
During setup, we define your folder template, company roles and permissions together. We verify that your Active Directory groups are available in Microsoft Entra ID; this connection is a deployment prerequisite, not a synchronization feature of TeamsFlow. The tool then creates the structure in a selected Teams channel and its SharePoint storage. Your team operates it independently and can adapt the template.
GETTING STARTED
We review how you create projects, who needs access to each type of document and where you keep completed work.
Agree on project structure and access for each group.
Connect to Microsoft 365 and verify the configuration on a selected project.
Learn how to create projects, review permissions and archive completed work.
Service terms
Pay a one-time instance setup fee followed by a monthly fee per instance. Pricing depends on scope, not the number of users or projects. Source code remains with Connectica; you receive an export of your data when the service ends. Support is provided in Czech and English.
Who it is for
CONNECTICA / TeamsFlow
We’ll review your folder structure and team roles, then show you how TeamsFlow can prepare projects, check access and archive completed work.
