Share a board privately

Unlisted

The board does not appear in browse, in search on the site, or in the sitemap, and the page tells search engines not to index it. Anyone holding the link can open it without an account. The share link contains an access token that the server checks before serving the board and its files; knowing the board's ordinary address does not grant access. Copy the complete share link using the board's sharing controls. Treat it as a credential: anyone you forward it to can also view and download the project.

The page metadata for a non-public board is deliberately generic. Your board name does not appear in the title or the description, because those get read by anything that fetches the URL, including a link preview in a chat app.

Password link

Same as unlisted, with a password on top. Use it when an unlisted URL is not enough: you are sending the link into a group chat, a ticket, or an email thread that gets forwarded. The recipient needs both the complete share link and the password. Send them through separate channels when that suits your review. A recipient can still forward both credentials or copy files after opening them.

Public

The default for a personal browser upload. A public board is eligible for listings and search indexing when it meets the publication and visibility requirements. Preview availability depends on its format and processing state. Public means others can find, view and download the retained source; review the files before choosing it.

Private

Access to a personal private board is restricted to you and assistant connections you explicitly authorize. A forwarded link grants no access. Organization uploads start as Private and follow organization membership and board grants; their password links can separately admit a recipient with the link and password.

Before you make a board public, look at what is in the archive rather than what is on the page. Review the retained Files after upload exclusions: customer names in a silkscreen layer, an internal part number in a BOM field, a supplier quote in a notes file, an .env that ended up in the project folder. The rendered views will not necessarily show you any of that, and the Files tab will.

Choose the access proof your review needs

A link is a credential that anyone can copy. It can be forwarded, pasted into a ticket, quoted in a screenshot, or left in a browser history on a shared machine. Nothing on our side can tell the difference between the person you sent it to and the next person they sent it to.

An unlisted link grants access to whoever holds its token. A password link requires a second secret. Private boards use signed-in identity and approved access instead of a forwarded URL. For an ongoing team workflow, organization admins assign board grants. Search exclusion keeps a board out of discovery; the server's access checks protect its contents. Those are separate protections.

Assistant access is a separate decision

Connecting an assistant does not change the board's sharing setting. Reading personal private boards needs your explicit own-board permission. Organization access is separately approved and read-only through MCP. Personal save permission, where offered, does not authorize changing visibility or writing organization boards. Check the consent screen before giving an assistant the context used for a review.

Changing your mind

You pick visibility when you upload. To change it afterwards, open the board's Settings from its page or the dashboard, then change Visibility. Organization admins manage board grants through Board access in the organization.

Making a public board private removes it from listings, but anything already fetched while it was public is out of your hands, and a search engine may hold a cached copy for a while. Treat publishing as one-way for anything sensitive.

Sharing for review

Use a complete unlisted or password share link for a recipient who should review without an account; use organization board grants for identity-based team access. Specify the version you want reviewed and confirm its required previews finished. The available schematic, PCB, 3D and BOM views let the recipient inspect the saved work before deciding whether to download it into their CAD tool.

One thing to do before you send it: run the checks yourself. A signed-out reviewer can read results that already exist but cannot start a run, so if you have never run them your reviewer finds an empty tab and no way to fill it.

Continue your work

Connect your AI to inspect board context and use separately approved personal saving where available. Use BoardRepo for KiCad to Push and Pull versions from the editor. For a shared organization workspace, contact us about Team.