Configuration workflow

1. Server Git registering

Go to Git to register your Git server connections.

• Forge exposure: Konfigomatik only calls a public forge. Probe () checks whether it can reach yours; the menu next to it declares the forge public or internal instead.
• Refresh icon (): on a public forge, re-sync projects from the server to fetch latest repositories and updates.
• Register (): Konfigomatik never calls an internal forge; the workstation of an administrator inventories it. You can also register a repository yourself: one your developers have opened, listed under Seen on workstations, or its path typed on the card of the server, one per line.
• You can also edit server URL/token, and delete obsolete server entries.

2. Group configuration

Open Configurations > Groups to create groups of projects that share common IDE settings.

• Create logical project groups (team, domain, product line, etc.).
• Assign projects to a group once, then maintain settings centrally.
• Use groups to keep consistency across multiple repositories.
• A project can belong to only one group at a time.

3. Settings configuration

Define IDE behavior at the right scope (project or group) using:

Codestyle, actions on save, compiler, Maven and JDK are all sections of that one screen.

• Apply consistent quality and formatting rules.
• Automate save-time actions for cleaner workflows.
• Standardize build/runtime settings across teams.

4. Creating developers

Go to Developers to create your developer team.

• Add developers and manage onboarding from a single place.
• Each developer receives an email with an access token.
• They must register this token in the Konfigomatik plugin to authenticate with your organization.