For JetBrains IDE teams
Share IDE settings through git, not a personal JetBrains account.
JetBrains' Settings Sync only syncs to your own personal account. Team Settings Repo shares Actions on Save, file templates and live templates across a team through one committed .idea/team-settings.yml, with a machine-readable drift report for CI.
Install the free plugin from the JetBrains Marketplace first — detecting drift and applying settings is free forever; Pro unlocks the CI-ready report for an account already using it.
The gap JetBrains left open
JetBrains' own Settings Repositoryplugin (276,081 installs) was deprecated with no direct successor. Its replacement, bundled Settings Sync, syncs everything to your personal account -- not scoped to a project, which is precisely what a team asking to share settings through version control doesn't want. The enterprise answer, JetBrains IDE Services, has 36.7M downloads and enterprise pricing that prices out a small team. Team Settings Repo covers the specific gap in between: a plugin that reads what a team already committed and reconciles it with one click.
Frequently asked
Why not just use JetBrains Settings Sync?
Settings Sync is per-user: it syncs everything to your own JetBrains account, not to a project or a team. There's no way to say "everyone on this repo shares these specific settings" -- which is exactly what long-open JetBrains tracker requests (IJPL-13066, IJPL-36353, IJPL-8575) ask for.
What does the free tier include?
On project open, the plugin reads a committed .idea/team-settings.yml, compares it to your IDE's actual Actions on Save, file templates and live templates, and offers a one-click Apply if anything differs. Free forever -- fixing your own IDE is worth nothing to anyone but you.
What does Pro add?
Tools → Generate Team Settings Report writes a machine-readable JSON report with a CI-friendly exit code, so a lead can prove a whole team's IDEs actually agree -- the thing you'd otherwise need JetBrains' enterprise-priced IDE Services for.
What settings does it cover?
actionsOnSave (reformat code, optimize imports on save), fileTemplates and liveTemplates. Deliberately not code styles, inspection profiles, copyright profiles or run configurations -- IntelliJ's own .idea/ files already share those today.
Does it touch anything outside these three settings?
No. It only reads and writes Actions on Save, file templates and live templates. It never touches your source files, VCS, or build.
Team Settings Repo only reads and writes Actions on Save, file templates and live templates. It never touches your source files, VCS state, or build.