Everyone gets a private workplace to build. Admins get everything they need to trust it.
Hey Makers 
As more teams build on Make, sensitive work needs clear boundaries, and account activity needs to be easy to track. Now every team member gets a Private Space for confidential automation projects, and admins stay in control by monitoring credit spend and Audit Logs.
What’s new
-
A Private Space for every member: Each person on your team gets their own private space to build scenarios and AI agents – hidden from the rest of the org by default. Admins can set a credit limit for each member’s Private Space, or let members draw from the organization’s overall credits without limitations. No more spinning up a throwaway team just to keep personal credentials and experiments out of everyone else’s view. -
Admins’ visibility into Private Space (Enterprise plan): Admins can open any member’s Private Space in read-only mode to view scenario names, modules used, and credit usage. Security and compliance teams get the oversight they need without seeing execution data, run history, or connection details – privacy and governance, not one or the other. -
Real-time email alerts for connection (key) usage. The moment a connection (key) is used by someone other than its owner, that owner gets an email. Shared credentials used to be a blind spot; now it reaches you directly, the moment it’s created. -
New Audit Logs events for identity, access, and credentials (Enterprise plan): Admins can now see SSO enabled, updated, or disabled; two-factor authentication enabled or disabled; organization role updates; member removals; and connections or keys used by someone other than their owner – all in one place. These are exactly the events a compliance review asks for first, now logged in one place instead of scattered across separate views.
Put it to work
-
Prototyping without the cleanup. Someone wants to test a few scenarios before rolling them out to the team. Instead of spinning up a throwaway team, they build in their own Private Space, then share only what’s ready.
-
Catching a security gap the moment it opens. Two-factor authentication gets disabled on an account. Audit Logs surface it immediately, instead of it surfacing weeks later in a routine review.
-
Knowing the moment your key gets reused. A shared API key set up months ago gets reused by someone else on the team. You get the email the moment it happens – not when you stumble across it in a scenario log.
This is how your business gains privacy where your team needs it, visibility where your admins need it.
Helpful resources