Make Private Spaces Add Governed Sandboxes for Every Automation Builder.

Make is giving every organization member a private place to build automations and AI agents, while adding the controls administrators need to monitor access, credentials and permissions. The governance package addresses a growing problem for businesses adopting no-code automation: how to let more employees build without exposing unfinished work or losing oversight of sensitive connections.

The company detailed four updates in an official blog post: Private Spaces, expanded Audit Log events, real-time credential alerts and Custom Roles. Make later summarized the changes in a LinkedIn announcement, framing them as a way to give builders privacy while providing administrators with evidence that activity remains controlled.

Private Spaces creates an isolated workspace for every organization member. Scenarios and AI agents placed there are hidden from the rest of the organization by default, allowing employees to prototype workflows before deciding what should be shared.

A revenue operations manager, for example, could test several customer-management automations without asking an administrator to create a separate workspace. The manager can then share the completed work when it is ready. This reduces the temptation to develop company workflows in personal accounts or expose drafts, test credentials and incomplete agents to an entire team.

Private Spaces can be enabled across an organization with a single toggle. Administrators can set a default monthly credit limit that applies automatically, then raise, lower or remove an individual member’s allowance. Setting the limit to zero effectively disables that person’s space without requiring their removal from the organization.

The feature is available on every Make plan, including Free. Enterprise customers receive an additional, optional layer of read-only administrator visibility. This can reveal scenario names, modules used and credit consumption inside a member’s Private Space, but it does not expose run histories, data stores or connection details.

That distinction matters. Make is treating privacy as separation from everyday organizational browsing, rather than immunity from governance. Administrators can understand what tools and resources are being used without automatically gaining access to the underlying business data.

Private workspaces alone would create a visibility gap, so Make is also expanding Audit Logs. The new events place identity, access and credential changes into a common record. According to the company, administrators can see events such as two-factor authentication being disabled when they happen, rather than discovering the change during a later access review.

Credential owners now receive real-time email alerts when another person uses their connection or key. This does not necessarily indicate malicious activity, since shared operational workflows often rely on centrally managed connections. It does, however, give the owner an immediate opportunity to confirm whether that use was expected.

Custom Roles complete the package by letting organizations tailor permissions to a person’s responsibilities. Teams no longer have to choose only between broad administrator access and a more restrictive standard role. The change supports least-privilege access as automation spreads into departments whose builders may need control over scenarios but not organization-wide settings. Create With examined that capability separately in Make Custom Roles Add Granular Enterprise Permissions for Growing Teams.

The timing is notable because Make is also lowering the barrier to creating workflows through conversational AI. Its broader workspace changes put Maia closer to the building experience, as previously reported. Easier creation can produce more builders, scenarios and credentials. Governance therefore becomes infrastructure, not simply an enterprise compliance feature added after adoption.

For small businesses, Private Spaces offers immediate practical value even without Enterprise oversight. Employees gain somewhere to experiment, while owners can contain credit consumption. Larger organizations get a more complete model: private development by default, metadata-level supervision where required, detailed records of security changes and narrower permission sets.

What is Make Private Spaces?

Make Private Spaces gives each organization member an isolated workspace for building scenarios and AI agents. Work inside the space is hidden from other members by default, and builders can share it when it is ready.

Which Make plans include Private Spaces?

Private Spaces is available on every Make plan, including Free. Optional read-only administrator visibility into members’ spaces is limited to the Enterprise plan.

What can Enterprise administrators see inside a Private Space?

Enterprise administrators can optionally view scenario names, modules used and credit consumption. They cannot inspect run histories, data stores or connection details through this read-only visibility feature.