Share work and collaborate
Choose the right review surface, check who can access it, and keep feedback tied to the correct version.
Create a viewable artifact link
Open Share in the file toolbar. In desktop version 0.25.0, Get a share link immediately creates an online link that anyone holding it can view. Check the artifact before clicking. The menu warns that this path currently shares one file and does not support embedded local assets such as images; do not assume it publishes the entire project.
Copy a link or withdraw the share
After creation, the menu provides Copy share link and Stop sharing. Test the page and its resources in the recipient’s environment before sending the link. To withdraw it, choose Stop sharing and recheck the old link. A published artifact does not grant edit access to its source project.
After Stop sharing succeeds, open the old link again to check access. Withdrawing a link is separate from deleting the local file or moving the project between spaces. If the action fails, retain the error and do not assume access has already been removed.
Make feedback specific
Use Comment to attach a request to an element, Comments to revisit saved feedback, Mark to explain a region with a screenshot, and Edit to change the HTML directly. Follow comments, marks, and AI revisions or direct canvas editing for the complete workflow.
Saving feedback, sending it to the agent, and checking the revision are three separate steps. After changing a shared artifact, use Update link so visitors can review the same version you just checked.
Account for newer sharing controls
Newer versions separate project visibility from publishing an online artifact. Private / Workspace moves the project between personal and team space; it is not a password or audience setting for a public share link. Confirm the destination when the move dialog appears. For an already published file, use Update link after checking changes: visitors keep seeing the previous published version until the update succeeds and they refresh. Newer sharing can include referenced resources, with a 20 MiB project limit. These controls differ from the 0.25.0 menu pictured above. Resolve sign-in, access or version-conflict messages before continuing.
| Control | What it affects |
|---|---|
| Private / Workspace | The project’s personal/team-space placement and team visibility. Check workspace and role permissions. |
| Get a share link / Update link / Stop sharing | The published artifact and its online URL. Check public content, resources and update/withdraw results separately. |
| Invite colleague | Workspace membership and role. It does not automatically publish an artifact or guarantee simultaneous source editing. |
| Deploy | A deployment through the selected hosting provider; it has its own account, configuration and resulting URL. |
Invite workspace members deliberately
The rules below apply to versions with free workspace invitations and shared workspace credits enabled. Older clients may still show a different invitation flow or seat prompts. Update the client and check the Members page in the web console for the features available to your workspace.
Open the workspace switcher and choose Invite colleague. Depending on your version and account, this opens an invitation dialog or the web Members page. Enter the recipient’s email and confirm the workspace.
- All plans, including Free, allow free invitations with no member limit; you do not need to buy extra seats.
- Owner, Admin and Member can all invite colleagues. Only Owner can choose whether to invite someone as Admin or Member. Invitations sent by Admin or Member always assign the Member role; no role selector is shown.
- Owner can change other users between Admin and Member. Admin can resend or revoke invitations and remove ordinary members, but cannot change member roles or manage paid seats.
- Workspace plan purchases and upgrades are managed by Owner. If you are Admin or Member and need a plan change, contact the workspace Owner.
- Members can create their own projects and view or comment on shared workspace projects. An invitation does not grant simultaneous editing of another person’s project.
If an invitation fails, check the email address, existing membership, invitation status and network connection against the displayed error. The recipient should sign in with the invited email address. Do not treat an old client’s seat prompt as a requirement to buy more seats; update the client and check the workspace’s web Members page.
Distinguish sharing from deployment
The Share menu also offers Deploy to Vercel and Deploy to Cloudflare Pages. Those use your hosting account and deployment configuration. A working share link does not verify a hosting deployment; check resources, access, and account requirements for the destination you choose.