Valprovia Governance introduces Access Profiles: custom roles that can be defined directly in workspace templates and automatically linked to SharePoint permission groups. Project managers and end users simply select a role from a dropdown when adding members — Valprovia Governance sets the correct permissions automatically, without manual SharePoint configuration.
Organizations have faced the same problem for years: Microsoft Teams only allows two roles — Owner and Member. External guests are implicitly treated as Members, without their own role category. In practice, this isn't enough. A project manager needs different permissions than a team member, an external partner different ones than a steering committee member. Until now, the answer was: manually configure SharePoint after every workspace creation. With Access Profiles in Valprovia Governance, there's now a better solution.
Access Profiles introduces custom roles for Microsoft Teams workspaces. Each role is linked to a SharePoint permission group. When someone adds a person to a workspace and assigns a role, Valprovia Governance automatically sets the correct SharePoint permissions in the background.
A typical scenario from project work: A new consulting project is set up. The project manager needs full access to all documents and must be able to approve project plans. Team members should edit documents but not make structural changes. A controlling officer needs read access to financial documents. And the external consulting partner should only access shared project documents.
Microsoft Teams doesn't recognize these distinctions. There's only Owner or Member — nothing in between. The administrator faces two bad options: set everyone up as Members with identical permissions (too much access, security risk) or manually configure SharePoint groups and permissions after every workspace creation (error-prone, doesn't scale).
For a single project, this is still manageable. But organizations manage dozens or hundreds of projects simultaneously. Each project needs the same permission structure — and each time it has to be rebuilt manually. The result: inconsistent permissions, forgotten assignments, security gaps, and an IT team overwhelmed with permission tickets.
The same problem exists with pure SharePoint workspaces — and there it's often even more pronounced. Give end users extensive permissions in SharePoint, and they'll modify the permission structures independently — often uncontrolled and with unintended consequences. Give them no permissions for management, and every change has to go through IT.
Access Profiles solves this dilemma — for Microsoft Teams workspaces and pure SharePoint sites alike: IT defines in the governance template which roles and permissions are available. End users manage permissions independently through the role dropdown — but only within the framework IT has defined. Control without bottleneck, autonomy without chaos.