Make · Product

Make Teams & Enterprise

Shared workspaces, roles and governance for automation at scale.

Teams and Enterprise plans exist for the moment automation stops being one person's side project: shared workspaces, role-based access, higher operation ceilings and organisation-level controls. Enterprise terms are quoted, so treat published capability lists as the starting point for a procurement conversation.

Disclosure: We may earn a commission if you purchase through links on this page. This never affects our reviews.

Features
👥

Shared workspaces

Group scenarios by team or client with clear ownership.

🔑

Roles & permissions

Separate who can build, who can run and who can only observe.

📈

Higher ceilings

Larger operation allowances and priority execution.

🏢

Org controls

Organisation-level administration for multi-team deployments.

Use cases
  • Agencies running separate client automation workspaces
  • Finance and ops teams sharing scenarios with reviewer-only access
  • Scaling from one automation owner to a team without losing control
Tutorials

Structure a Make workspace before it sprawls

Naming and ownership conventions that survive team growth.

  1. Create one workspace per team or client, never per app.
  2. Name scenarios after the business process, not the trigger app.
  3. Record an owner and an escalation contact in the scenario notes.
  4. Give reviewers read-only access so audits don't require builder rights.
  5. Review operation consumption per workspace monthly.
FAQs
What does Make Enterprise cost?+

It is quoted rather than published — confirm operations, seats and support terms directly with Make.

Can I self-host Make?+

No. If self-hosting is a hard requirement, n8n is the alternative to evaluate.

Related reading