On this page
  1. Source and history belong to the organization
  2. Access per reviewer
  3. Review the same revision
  4. Keep GitHub where it fits
  5. Continue in your editor
  6. One component library
  7. Files to leave out
  8. Team setup and pricing
  9. Available now and upcoming

How teams work in BoardRepo

Source, versions and access in one place, so everyone works from the same revision.

Source and history belong to the organization

Organization boards and every published version stay with the organization. Admins manage members and board access.

Access per reviewer

Members get access through roles and board permissions. Admins can add someone outside the organization to one board. A password link admits a reader without making them a member. Organization uploads start Private; compare sharing options.

Review the same revision

  1. Save a baseline and wait for its schematic and PCB previews.
  2. A reviewer opens that version.
  3. Save the change as a new version. Signed-in readers can compare the two once comparison data is ready.
  4. Pull the latest into KiCad, or download an older version from history.

BoardRepo does not merge CAD changes, so agree who edits next. Version-control workflow.

Keep GitHub where it fits

Use GitHub for branches, firmware, pull requests and CI. With the GitHub App and Keep up to date on, default-branch changes can update an imported board; saves on BoardRepo are not committed back. BoardRepo and GitHub.

Continue in your editor

BoardRepo for KiCad supports the PCB Editor on KiCad 9.0.1 or later and the Schematic Editor on KiCad 10. Publishing needs organization and board permissions.

One component library

An organization has a component library that every member can open. Admins and members who can edit add, move and remove parts. Any member can copy a part and paste it into a KiCad 10 schematic. A part is a symbol from the libraries KiCad installs, with the footprint you choose, or a part saved with its own files from the Parts tab of BoardRepo for KiCad. Each part shows how many boards you can open use it. A board that already uses a removed part keeps its own copy.

Files to leave out

Admins choose which files uploads leave out: build and debug logs, KiCad recovery and backup files, Altium history and preview files, or file patterns of their own. The choices apply to future browser uploads to every organization board. Existing board files stay unchanged, and BoardRepo for KiCad keeps its selected files. Every member can see the rules in the organization's Settings.

Team setup and pricing

Team has custom pricing and contact-led setup. Tell us who publishes, who reviews and how you manage source today. Availability and scope of Enterprise deployment, SSO, integrations and support are agreed separately; none is part of a standard Team workspace.

Arrange team setup

Available now and upcoming

Available: browser inspection, saved versions and visual comparison. Upcoming: KiCad Web, branches and organization saving through MCP. Assistant access to organization boards needs separate approval and follows board permissions. AI is optional.

Security

Continue your work

Shared boards with member and reviewer access.

Explore the team workspace

BoardRepo for KiCad adds Push and Pull to the editor.

Sign in to BoardRepo

New here? Signing in creates your account; there is no separate sign-up.