How to Share Scenarios in Make.com

Sharing automation scenarios in make.com lets you collaborate, gather feedback, and reuse workflows across your team or community without rebuilding everything from scratch. This guide walks you through how scenario sharing works, how to generate and manage shareable links, and how to control what others can do with your automation.

What Is Scenario Sharing in Make.com?

Scenario sharing in make.com allows you to create public links to your scenarios so other users can view, duplicate, or, if you allow it, edit them. Instead of exporting complex configurations, you provide a single URL that opens directly in the scenario editor for anyone who has access.

You can use these shared scenarios to:

Showcase best practices to your team or clients.
Offer templates to your community or audience.
Support training, documentation, or onboarding.
Quickly clone working automations into another account.

How Scenario Sharing Works in Make.com

When you enable sharing, make.com generates a special public link tied to your scenario. Anyone with this URL can open the scenario in the editor and interact with it according to the permissions you set. You remain the owner, and you can modify or revoke access at any time.

Crucially, scenario sharing is a scenario-level setting. You control sharing for each scenario individually, which helps keep sensitive projects private while still allowing safe distribution of selected automations.

Permissions for Shared Scenarios in Make.com

Make.com supports three main permission levels for shared scenarios. Each level determines how recipients can interact with your workflow once they open it using the public link.

View-only access in Make.com

View-only is the most restrictive sharing option and is ideal when you want to demonstrate or document a process without letting others change it.

With view-only access, recipients can:

Open the scenario in the editor.
Inspect modules, connections, and flow structure.
Learn how the automation is built step by step.

But they cannot:

Modify modules or connections in your original scenario.
Save changes to your scenario.
Run or schedule your scenario from their side.

Duplicate access in Make.com

Duplicate access lets people create their own independent copy of your automation. This is the best choice if you are sharing templates or examples that others should adapt to their own needs.

With duplicate access, recipients can:

Create a new scenario cloned from yours within their own account.
Change modules, settings, and connections in their copy.
Run, test, and schedule the duplicated scenario freely.

Your original scenario in make.com stays unchanged, so you can maintain a clean, reference version while others iterate on their copies.

Edit access in Make.com

Edit access is the most permissive option and is typically reserved for close collaborators or team members you fully trust.

With edit access, recipients can:

Modify your original scenario directly in the editor.
Add, remove, or reconfigure modules.
Save changes that affect everyone who uses that scenario.

Because edit access gives full control over the scenario, use it carefully and only when collaboration on the exact same asset is required.

How to Share a Scenario in Make.com

The process for sharing a scenario is straightforward. Follow these steps to generate and distribute a public sharing link.

Step 1: Open the scenario in Make.com

Log in to your make.com account.
Navigate to your dashboard or scenario list.
Click the scenario you want to share to open it in the editor.

Step 2: Open the sharing options

Inside the scenario editor, locate the options or settings menu for that scenario.
Look for the feature labeled for sharing or public link; this panel controls who can access your scenario via URL.

Step 3: Choose the permission level

Select how others can interact with your shared scenario:

View-only if you want them to inspect but not change it.
Duplicate if you want them to create their own copies.
Edit if you want full collaborative control over the same scenario.

Carefully confirm the permission level before you generate or share the link, especially when working with production or business-critical automations.

Step 4: Generate and copy the shareable link

Enable sharing for the scenario according to your selected permission.
Make.com generates a unique public URL for that scenario.
Click the option to copy this link to your clipboard.

This URL is what you send to colleagues, clients, or community members so they can access the automation.

Step 5: Share the link securely

Decide how you will distribute the link:

Via email or direct message to your team.
Inside internal documentation or wikis.
On public help pages, community posts, or tutorials.

Remember that anyone with the URL can open the scenario with the assigned permissions, so treat it as a sensitive link, especially when edit access is enabled.

Managing and Revoking Scenario Sharing in Make.com

After you share a scenario, you may want to adjust or revoke access later. Make.com gives you control to change sharing settings or completely disable the public link.

Change permission levels

If collaborators no longer need edit rights, or you want to allow only duplication going forward, you can modify the permission level from the same sharing panel.

Open the scenario in the editor.
Go back to the sharing options.
Switch the permission between view, duplicate, or edit.

The change applies to anyone who opens the link from that point on.

Disable the public link entirely

If you want to stop all access:

Open the scenario's sharing panel.
Turn off sharing or delete the generated public link.

Once disabled, the old URL no longer opens the scenario, effectively revoking access for everyone who had it.

Best Practices for Sharing Scenarios in Make.com

To keep your automations safe and well organized, follow these practical tips when sharing:

Prefer duplicate access when distributing templates or examples.
Use view-only access for demonstrations or documentation.
Reserve edit access for trusted team collaborators.
Regularly review shared scenarios and revoke links you no longer need.
Avoid including sensitive data in example scenarios you intend to share publicly.

These habits help you maintain control while still benefiting from the flexibility of shared automation.

Learn More About Make.com Scenario Sharing

For deeper technical details and the latest updates on scenario sharing, consult the official documentation on the Make.com help center: Introducing scenario sharing. You can also explore professional automation consulting resources such as Consultevo if you need strategic guidance on how to structure and share workflows at scale.

By understanding how to control view, duplicate, and edit permissions, you can use scenario sharing in make.com to speed up collaboration, training, and deployment of reliable automations across your organization.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help