Collaborate
Project Visibility
Every project is either public or private.
Private Projects
Private is the default. When a project is private:
- Only you and invited team members can access it.
- It does not appear in the Explore gallery.
- It is not indexed for search.
- Published URLs still work (anyone with the link can view the deployed site), but the source project is not discoverable.
Public Projects
When you set a project to public:
- It appears in the Explore gallery and is searchable.
- Anyone can view the project card: preview image, name, description, tags.
- Other users can clone it to create their own copy.
- Category and tags affect gallery placement and search results.
Going public does not share your environment secrets. The .env file and Supabase credentials stay private.
Changing Visibility
- Open Settings > Project.
- Find the Visibility section.
- Select Public or Private.
- Click Save Changes.
Switching to public indexes the project for search. Switching back removes it from the gallery and search.
Moderation
Public projects are subject to content moderation. A moderation status section appears in project settings showing whether the project has been reviewed. Projects violating community guidelines may be flagged or removed from the gallery.
Visibility vs Publishing
These are independent settings:
| Published | Not Published | |
|---|---|---|
| Public | Live site via URL. Visible in gallery. | No live site, but appears in gallery for cloning. |
| Private | Live site via URL. Hidden from gallery. | Only accessible to team members in the editor. |
Tips
- Start private, go public when ready. Polish the preview image, title, and description first.
- Add tags and a category before going public. They drive discoverability in the gallery.
- Upload a preview image. Projects with thumbnails get more views and clones. Set one in Project Settings.
- Review before sharing. Public projects are moderated. Follow community guidelines.