Configuration workflow

1. Server Git registering

Go to Git to register your Git server connections.

• Closed network icon (): use this action when your Git instance is not publicly reachable. It opens the import flow to register projects with controlled network access.
• Refresh icon (): re-sync projects from the server to fetch latest repositories and updates.
• 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 sections of that one screen — the five screens they used to be answer with a redirect to it.

• 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.