---
title: "Step 2: Initial Configurations"
canonical: "https://support.appfire.com/space/FD/2833678537/Step%202%3A%20Initial%20Configurations"
format: markdown
---
> Macro (aura-html)

The goal of this step is to: 

- Define a preferred (default) domain.
- Configure group programming.
- Prepare merge settings.

## Preferred domain

This is a **low-effort**, **real-time**, **required** configuration.

![Initial configurations, preferred domain tab.](media://9a1be5b2-bfda-489d-b4a5-af176ac16181)

When developers commit code, their usernames or email addresses can vary. Flow uses a default domain to identify which email address should be the primary account for each person.

Initially, this domain is set based on the first admin’s email address. Verify that it is correct to ensure your user data merges accurately once imported. This is especially important when a user uses more than one account.

> 📝 If your default domain is not set correctly during user merges, your Flow data will be inaccurate, and you will need to update the default domain and manually merge and unmerge users in the future. This can be a lengthy process. 
> 📝 
> 📝 Ensure your default domain matches the domain you want to use for apex users to save time later. Setting this up before you import data is the fastest path to success.

**Why the preferred domain matters:**

- Helps Flow link multiple accounts to the correct individual.
- Ensures data is organized under your organization's primary email domain.
- Simplifies the process of merging duplicate users later.

To define your preferred domain, enter the domain address in the **Preferred domain** box.

Visit the [Merge users: Preferred domain and configurations](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802404067/Merge+users#Preferred-domain-and-configurations) page to learn more.

When done, click **Continue** to proceed to the *Group programming* tab.

## Group programming

This is a **medium-effort**, **minutes**, **recommended** configuration.

![Initial configurations, group programming tab.](media://6c04bacd-59fb-4484-b6c3-60b41411c97f)

Group programming setup lets Flow recognize, attribute, and visualize work authored by multiple people simultaneously, such as in pair programming or mob programming.

Since standard Git data typically credits only one author per commit, group programming ensures that everyone involved receives proper credit for their contributions.

**Why group programming setup matters:**

- It prevents invisible work where a developer contributes significantly to a session but does not appear in the metrics because they were not the one to hit Enter on the commit.
- It encourages collaborative practices like pairing and swarming without the fear that individual productivity scores will drop.
- It helps leaders see how much of the codebase is built collaboratively versus solo.

If this setup does not apply to you, you can disable it.

> 📝 Note that Flow only applies group programming setting changes to new incoming data. It does not automatically reprocess old data. For that reason, it is best to enable group programming before you import your repos.

Visit the [Group programming](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802403971) page to learn more.

The group programming setup consists of the following:

### Labelling

In the box under **Labeling**, enter the label you want Flow to apply to group programming commits. The label determines how group-programmed commits will be named in Flow reports.

![Labelling text box under group programming setup.](media://06ec8583-2fae-4b9f-8b1c-64d1096a0dd8)

### Assigning work to others

This toggle-based configuration determines the logic Flow uses to credit contributions when a commit involves multiple people.

![Two Assigning work to others toggle under group programming setup.](media://08ba80d7-377f-48fe-8aa8-9b1d01b90175)

- **Using “Co-Authored-By” in the commit message** - It is recommended to leave it enabled so that your git host can mark commits with multiple authors.
- **Using multiple names in the** `user.name` **and** `user.email` **fields** - This advanced setting is for you to manually mark commits with multiple authors. Enable it if you're unable to use the Co-Authored-By convention.

### Prefixes and delimiters 

The following settings:

- **Prefixes (optional)**
- **Email delimiters (required)**
- **Name delimiters (required)**

activate only when the **Using multiple names in the** `user.name` **and** `user.email` **fields **toggle is enabled.

Enter any prefixes and/or delimiters you want Flow to check for. Flow labels any commit containing these values in `user.name` or `user.email` as group work.

1. Click the **Add another** button to enter additional values.
2. Click the **X** button to remove a value.

When done, click **Continue** or **Skip** to proceed to the **Prepare merge settings** tab.

## Prepare merge settings

This is a **high-effort**, **real-time**, **required** configuration.

![Prepare merge settings tab under Initial Configurations.](media://156eb11f-b1a3-431b-8edf-2d7fcbd68df6)

Auto-merge is designed to maintain clean data by consolidating multiple identities from a single developer into a single Apex user profile.

Because developers often contribute code using different email addresses, their work can appear fragmented across several profiles. Auto-merge identifies these matches—primarily by looking for identical email addresses or sign-in credentials—and combines them automatically. 

This ensures that metrics like Coding Days and Impact accurately reflect a person's total contribution rather than splitting the data across multiple accounts.

Auto-merge is turned on by default.

Visit the [Merge users: Autom-merging](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802404067/Merge+users#Auto-merging) page to learn more.

The group programming setup consists of the following:

### Exclusions

The two toggles control emails or names you would like to exclude from being merged:

- **Exclude first name only matches from matching**
- **Exclude common words from matching **- When this option is enabled, a box appears for you to enter the words you want to exclude.

![Merge exclusions box.](media://b4e60ca7-c3e1-46f2-91dd-8933a6a7bdaa)

### Auto-merge

This adds an extra layer of logic to Flow, allowing it to merge new users either by the email they used to log in or by all their matching emails.

![Auto-merge options.](media://06499d13-670e-4444-a483-f8819ca60579)

When done, click **Continue** to proceed to [Step 3: Git Integration](https://appfire.atlassian.net/wiki/spaces/FDDRAFT/pages/2893349482).