Sharing and cloning

There are three different things people mean by sharing a project, and they are separate controls. Copying a link lets a workspace member open the project. Sharing turns on a read-only link for anyone. Cloning lets those people make their own copy.

Copy a link

Two of the items in a project's card menu copy links, and they are not the same link.

Copy Project Link copies the dashboard address of the project. Only people in the workspace can open it. Sending it to someone outside the workspace gets them nowhere unless you also share the project.

Copy Published App Link copies the live web address of the published site, either its free address or your custom domain. Anyone can open it. Open Published Project opens that same address in a new tab. Both are disabled until the site has been published once.

Share a read-only link

Open the project and choose Share in the header. A panel titled Share Project appears.

The first switch is Share a read-only link, described as Anyone with the link can view your published site. Turn it on and a copy box appears underneath with the link to hand out.

If the site has not been published yet, a note under the box reads Viewers see nothing until you publish this site. Sharing exposes the published site, not your working preview, so there is nothing to see until you publish.

Let people clone it

With sharing on, a second switch appears: Viewers can clone this project. Turning it on gives anyone with the link a Clone button on the project, which drops a copy into their own workspace.

Turning cloning on forces sharing on, since a link nobody can open cannot be cloned. The reverse is guarded too: while cloning is on, the Share a read-only link switch is disabled with the tooltip Disable cloning first.

Choose what the copy includes

By default a clone gets your structure and none of your content. Three more switches appear once cloning is on.

Include database content, described as Copy your data, not just the structure. This one only appears when the project has a database.

Include uploaded files, described as Copy your uploaded files and media.

Include environment variables, described as Copy your real values, not placeholders. Leave it off and the variable names still come across, each with the value VALUE_HERE for the cloner to fill in. Turn it on and your actual values go with every copy, so think before you do.

With database content on, a Choose collections row appears. Opening it gives three modes:

Mode	What it copies
Everything	The content of every collection
Only these collections	The ones you pick, nothing else
Everything except these	Everything but the ones you pick

Turning cloning back off resets all of these, so re-enabling it later starts from the safe default again.

Every switch in this panel saves as you toggle it. There is no separate save button.

Duplicate a project yourself

Duplicate in the card menu makes a copy in the same workspace. The copy is named after the original with (Duplicated) on the end.

A duplicate is your own project, so it takes everything regardless of the cloning switches above: the full database content, the uploaded files, and the real values of the environment variables. It arrives unpublished and without the original's custom domain, and it is not itself shared or cloneable.

A duplicate is a new site, so it needs a free site slot. If your plan has none left you are offered an extra site or an upgrade before it proceeds.

What a clone or duplicate does not carry

Whichever route the copy took, some things stay with the original:

• It is not published, and it has no publish history
• It has no custom domain
• Its own sharing and cloning switches start off

Next

• Templates is the other side of this, cloning someone else's project.
• Publish a site is what makes a shared link show anything.
• Transfer a project hands the project over rather than copying it.