The screenshots and primary steps in this article show the desktop experience. On desktop, open Share from the top-right corner of the project. On mobile, open the project tools, then select Share. From there, choose a sharing state, copy a project link, control whether the project appears in Discover, or make the project Private when you no longer want it shared.

Before you share

Only the project owner can change visibility or App Card settings; editors should ask the owner to make these changes. Making a project Private or turning off Show in Discover requires Pro. If the owner is on the Free plan, follow the upgrade prompt before using either option. Before changing a project to Public, remove passwords, API keys, confidential information, or other content you do not want another person to see. The Share panel says a Public project can be accessed via link and Discover, so test the copied link from a signed-out/private browser window before sending it.

Who can access the project?

Use the access label shown in the current Share panel as the source of truth. This article does not add permission guarantees that are not visible in the supplied product evidence.

Public

The Share panel says “Project can be accessed via link and Discover.” Use Copy link, then verify the result from a signed-out/private browser window before sending it.

Private

The Share panel says “Only visible to you.” Use Private when you no longer want the original project shared, then test the old link from a signed-out/private browser window.

Share a project

1. Open the project you want to share.
2. Open Share. On desktop, select Share in the top-right corner. On mobile, open the project tools, then select Share.
3. Select Public. The current panel states that a Public project can be accessed via link and Discover.
4. Decide whether to use Show in Discover. This article uses the current UI term Discover throughout.
5. Optional: select Edit under App Card. Use it to review the cover, name, description, and version shown in the current App Card screen.
6. Select Copy link.
7. Verify the share before sending it. Open the copied link from a signed-out/private browser window or ask a recipient to test it. Confirm the intended project opens and that the content shown is appropriate to share.

Figure 1. Current Share Project panel with Public selected.

What to notice

• Public is selected, and the panel explicitly says the project can be accessed via link and Discover.
• Show in Discover is a separate control in the current UI. After changing it, verify the actual result in Discover.
• Copy link is the action used to obtain the link you will test and send.
• Export is visible in the panel, but it is a separate action from changing project access.

What happens after you share?

After Public is selected, the Share panel provides Copy link and the current Discover/App Card controls. The exact recipient experience should be verified using the copied link rather than assumed.

• Test the link outside your signed-in session so you see what a recipient can actually open.
• If the project content or access shown to the recipient is not what you expected, return to Share and change the state before distributing the link.

This page does not promise recipient editing or other permission behavior that is not established by the current product captures. For remix behavior, see Remix a project. For workspace roles and permissions, see Workspace settings.

Optional: review the App Card

The current Edit App Card screen shows controls for Cover, Name, Description, and Version. Review these fields before public sharing if the project will appear in Discover.

Figure 2. Current Edit App Card screen.

What to notice

• The screenshot directly supports the presence of Cover, Name, Description, and Version fields.
• Use these fields to review how the project is presented; access itself is controlled in the Share panel, not on this screen.

Stop sharing the original project

1. Open the project and select Share.
2. Make sure you are the project owner and have Pro, then select Private. On the Free plan, follow the upgrade prompt before continuing. If you are an editor, ask the owner to make the change.
3. Confirm the panel says “Only visible to you.”
4. Test the old link from a signed-out/private browser window. If the old link still opens for another user, do not assume access has been revoked. Contact Atoms Support before relying on the project as private.

Figure 3. Current Share Project panel with Private selected.

What to notice

• Private is selected, and the panel explicitly says Only visible to you.
• Copy link remains visible even in the Private state. Do not use the presence of the button itself as proof of who can access the project.
• Verify the old link outside your signed-in session after changing the state.

If sharing does not work as expected

• Public is selected but the copied link does not open as expected: reopen Share, copy the link again, and retest from a signed-out/private browser window.
• Private is selected but another signed-out user can still open the old link: stop relying on the state as revoked and contact Atoms Support.
• Show in Discover does not produce the result you expect: verify the current Discover surface and report the mismatch rather than assuming the toggle changed link access.
• Share, Public, Private, or another expected control is missing: do not infer why from this article. Capture the current screen and contact Atoms Support or the responsible product owner.

Related Action: Export Project Files

Export requires Pro. In the Share menu, select Export. On the Free plan, Atoms shows an upgrade prompt. On Pro, the browser downloads a ZIP archive named for the project. The archive can include code and assets, and its exact contents may vary by project. Treat it as project data and share it only with intended recipients.

Figure 4. Example ZIP archive downloaded after selecting Export.

Figure 5. Example contents after opening the exported project archive.

What to notice

• Export downloads files; it is not a sharing-permission setting.
• The ZIP can contain code and assets, so treat exported files as project data and share the archive only with people who should receive it.