A shared workspace for your KiCad team
Keep project source, saved revisions and review access together, so the next engineer can work from the same version.
Source and history belong to the organization
Organization boards keep their source files and published versions in the shared workspace. Administrators manage membership and board access. Each published version retains its own files; saving source and completing its previews are separate steps.
Give each reviewer the access they need
Members work through their organization roles and board permissions. Administrators can grant someone outside the organization access to a particular board. A password link is a separate way to admit a reader with both the full link and password; it does not make them a member or give them publishing rights.
Organization uploads start Private. Compare sharing options before sending source to a contractor.
Review the same saved revision
- An authorized editor saves a baseline and checks that the required schematic and PCB previews have finished.
- A second authorized person opens that published version and reviews its source and available outputs.
- The editor saves the change as a new version. Signed-in readers can compare supported, accessible published pairs when the required comparison data is ready.
- Continue in KiCad. Pull retrieves the current remote version; download from history when you need a particular older revision.
Coordinate simultaneous edits: BoardRepo does not merge CAD changes. Read the version-control workflow.
Keep GitHub where it fits
Use GitHub for branches, firmware, pull requests and automation. With the GitHub App and Keep up to date enabled, default-branch changes can update an imported board. Plugin and assistant saves are not automatically committed back to GitHub. Agree which system owns the next edit before switching between them.
Continue in your editor
The native plugin supports the PCB Editor on KiCad 9.0.1 or later and the Schematic Editor on KiCad 10. Download an available platform package and follow the platform-specific sign-in and enrollment steps on BoardRepo for KiCad. Team publishing requires the relevant organization and board permissions.
Team setup and pricing
Team has custom pricing and contact-led setup. It includes an organization workspace, member roles, board access and team-wide file exclusion policies. Tell us who needs to publish, who needs to review and how you manage source today.
Enterprise deployment, SSO, integrations and support requirements are agreed separately. Contact us to establish availability and scope; these are not automatic entitlements in a standard Team workspace.
Available capabilities and upcoming work
Browser inspection, retained published versions and supported visual comparison are available workflows. KiCad Web, branches and organization saving through MCP are upcoming capabilities. Assistant organization reads, checks and reviews follow separately approved access and current board permissions. AI is optional.