Make Private Spaces: Every Teammate Gets Their Own Workspace

In this walkthrough, Frank tackles a familiar pain point for busy Make organizations: too many collaborators, too many test scenarios, and zero privacy. He shows how the new Private Spaces feature gives every team member their own isolated workspace — no more spinning up separate teams just to keep personal builds out of view. 🔍 Inside the Build: * Enabling Private Spaces: Frank heads to the org dashboard, opens the three-dot menu, and toggles Private Spaces on for the whole organization — plus how to set a default credit limit per space. * What a Fresh Private Space Looks Like: Once enabled, each member gets an empty workspace: no scenarios, no credentials (aside from the default AI provider), completely separate from the shared team space. * Building a Real Scenario Inside It: Frank builds a simple email summarizer live — pulling a Gmail message, connecting a fresh Gmail credential, and passing the content to an AI provider to generate a short summary. * Proving the Privacy: Frank switches views to show that the scenario he just built is completely invisible from the shared team space — confirming other members can't see it. * Built-In Security Alerts: Frank highlights that if anyone else ever uses one of your connections, Make automatically emails you the moment it happens — on every plan, so nothing goes unnoticed. This is a great one for admins running larger orgs with lots of collaborators building test scenarios side by side. 🛠️ Featured Stack: * Make Private Spaces (Org-Level Workspace Isolation) * Gmail (Trigger Module) * Make AI Toolkit (Summarization) * Credit Limits (Per-Space Admin Controls) * Connection Usage Alerts (Automatic Security Notifications) 💡 Pro-Tip from Frank: Enterprise admins can view members' private spaces in read-only mode — so privacy for collaborators doesn't mean losing oversight where you actually need it.