Put the right people in every workspace from day one.
nBold enforces owners, members, and guest rules per template — so every Microsoft Teams workspace starts with the right people in place, automatically.
Membership is where governance quietly erodes.
Provisioning a workspace is the easy part. Keeping the right people in it — and the wrong people out — is the part that breaks down over time. Owners leave, guests linger, and the team on paper stops matching the team in the workspace. Every drift is a compliance question waiting to surface.
Orphaned workspaces
Workspaces left without an active owner drift out of governance — no one to manage access, lifecycle or content, and every audit turns up another gap.
Uncontrolled guests
External access is granted ad hoc and rarely reviewed, leaving sensitive content exposed long after a project ends.
Wrong people, missing people
Key stakeholders are forgotten, guests stay too long, and workspaces start with the wrong access by default — because membership was set by hand.
Drift from the source
The account team changes in the CRM, but workspace membership never catches up — the two views of who is on the deal diverge until someone notices.
Define the rules once, enforce them on every workspace.
Membership rules live on the template. Encode them once and every workspace provisioned from that template inherits the same owners, the same guest controls, and the same access posture — no manual setup, no exceptions slipping through.
Mandate a minimum number of owners on every workspace created from a template, so no workspace is ever left without someone accountable for access, lifecycle and content.
Allow, restrict or block external guests per template — internal-only for confidential work, named guests permitted for client-facing rooms.
Pre-populate owners and members by their role in the scenario — the deal owner, the project lead, the compliance reviewer — added automatically at provisioning, not by manual invite.
Set whether workspaces from a template are private or public by default, so access posture is decided by policy, not by whoever clicks create.
What a membership policy controls.
Each rule is defined per template and travels with every workspace created from it — applied automatically at provisioning, no manual setup needed.
| Policy | What it does | Example |
|---|---|---|
| Required owners | Minimum owner count enforced per template | At least two owners on every project team |
| Guest access | Allowed, named-only, or blocked | External guests permitted on deal rooms, blocked on HR workspaces |
| Default members | Added automatically by role at creation | Account manager + CSM added to every onboarding workspace |
| Default owners | Assigned automatically by role at creation | PMO lead set as owner on all portfolio teams |
| Privacy | Private or public default per template | All finance workspaces created private |
| Membership sync | Driven from a source of record via nFlow | CRM account team mirrored into the Teams workspace |
nBold is Microsoft 365 native. Membership rules are applied to your own Teams and groups through the Microsoft Graph API, under a service account you control. ISO 27001 certified and SOC 2 Type II certified.
Keep membership in sync with your CRM.
For workspaces tied to a deal or an account, membership should not be maintained by hand. With nFlow, the people in the workspace follow the people in the CRM — so the two never drift apart and context travels with the work.
Define the source of record
Point a workspace at a source of record — the account or opportunity team in your CRM. nFlow connects Salesforce and HubSpot to Microsoft Teams without code.
Map CRM roles to workspace membership
Decide how source roles translate into workspace owners and members — the deal owner as owner, the wider account team as members, so context carries over automatically.
Keep the two in sync
As the team changes in the source system, nFlow keeps the Teams workspace membership aligned, so the CRM stays the source of truth and Teams becomes where execution happens.
One guardrail in the full governance layer.
Membership policy is one of the building blocks your teams use every day — alongside naming, classification and lifecycle — so structure, access and protection are all decided together at the template level.
Governance
Naming, labels, approvals, membership and lifecycle — guardrails applied per template across every workspace.
Explore GovernanceSensitivity labels
Pair membership rules with the right classification and protection, applied to every workspace by default.
Explore Sensitivity labelsnFlow
CRM-driven workspace automation — provisions the full workspace and keeps membership synced from your account and deal teams.
Explore nFlowFrequently asked questions
What happens if a workspace loses its last owner?
A membership policy can require a minimum number of owners on every workspace. When an owner leaves the organisation or steps off a project, nBold flags the gap so the workspace is never left ownerless — the state that most often leads to orphaned, ungoverned workspaces.
Can we block external guests entirely on some workspaces but allow them on others?
Yes. Guest and external-sharing rules are set per template, so a confidential workspace can be internal-only while a client-facing deal room permits named external guests. The rule travels with every workspace created from that template.
Can membership sync from Salesforce or HubSpot?
Yes, through nFlow. When membership is driven by a source of record — such as the account or opportunity team in your CRM — nFlow keeps the Teams workspace membership aligned as roles change in the source system, so the people in the workspace always match the people on the deal or account.
Can ownership be enforced?
Yes. Templates can define owner requirements and lifecycle processes can notify owners when a workspace becomes inactive — so accountability is built in, not chased down after the fact.
Does nBold move any of our membership data outside the tenant?
nBold acts on your Microsoft 365 tenant through the Microsoft Graph API, under a service account you control. Membership changes are applied to your own Teams and groups. nBold is ISO 27001 certified and SOC 2 Type II certified. See our Security & compliance page for the full detail on how nBold handles data.
The right people in every workspace, from day one.
See how nBold turns membership rules into guardrails that apply automatically — so owners are always present, guests are always controlled, and access never drifts.