---
title: "Group programming"
canonical: "https://support.appfire.com/space/FD/1802403971/Group%20programming"
format: markdown
---
> Macro (aura-html)

Use group programming settings to customize how work authored by multiple people is credited and visualized in Flow.

## Permissions

You need the **Manage Configurations** permission to turn on group programming.

## Enabling group programming

To find and enable group programming:

1. Click **Settings **in the top navigation.
2. In the left navigation, click **User Settings** located under **User Management**.
3. Click the **Group programming** tab on the *User Settings* page.
4. Toggle the **Enable** toggle **On**.
5. In the text box under **Labeling**, enter the label you want Flow to apply to group programming commits. This determines how group-programmed commits will be named in Flow reports.

> ℹ️ Flow only applies group programming setting changes to new incoming data. It doesn't automatically reprocess old data, so it’s best to enable group programming before importing your repos.
> ℹ️ 
> ℹ️ If you import a repo before enabling group programming, the previously imported data won’t be affected by the new settings.

![Group programming tab showing labelling.](media://28037328-d57b-4205-815e-34b225bd6b84)

## Assigning work to others

Use the toggles in the **Assigning work to others** section to set how Flow identifies when a commit is authored by a group.

![Assigning work to others configuration.](media://bbdc71e8-b466-4864-96ce-8b59db445702)

Toggle on **Using Co-Authored-By in the commit message** so your git host can mark commits with multiple authors:

- This convention is used by git hosts to mark commits with more than one author. For example, learn how to create a [commit with multiple authors](https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) on GitHub.
- For group commits authored solely on the commit message, you must include Co-Authored-By with an email address or a username with an email address.

> ℹ️ If you include a comment in addition to listing the co-authors in the commit message, make sure each co-author is on a new line.

Toggle on **Using multiple names in the user.name and user.email fields** so you can manually mark commits with multiple authors if you're unable to use the Co-Authored-By convention:

- This toggle is useful for commits with user.name and user.email fields similar to:
  - Jen Smith & Robert Aspens `jsmith@mycompany.com, raspens@mycompany.com`
  - Jen Smith & Robert Aspens `raspens@mycompany.com`

When the **Using multiple names in the user.name and user.email fields** is toggled **On**, the **Prefixes**, **E-mail delimiters**, and **Name delimiters** text boxes are active and editable on this page.

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

![Group programming prefixes and delimiters configuration.](media://c1f2ffb6-e205-4029-86e7-59bf30dde6a8)

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

For example, a commit’s user.name field contains `Jen Smith & Robert Aspens`. The commits user.email field contains `jsmith@mycompany.com,raspens@mycompany.com`.

In this example, Flow labels the commit as group work when a text box under Email delimiters contains `,` or a text box under Name delimiters contains `&`.

Learn more about [Manually marking a commit as a group commit](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802666201).

### Allocating credit for group work

Configure how Flow assigns credit for group work. You can split the work between contributors or give each contributor full credit.

![Credit allocation diagram example.](media://b604dd80-950e-4b66-8820-d8fd51cd7405)

Choose whether credit is split evenly or each contributor gets full credit for these metrics:

- Coding days
- Commits per day
- Impact
- HALOC metrics

Click **Save Changes** once you’re done adjusting your group programming settings.

## Viewing group-programmed commits in reports

Once you’ve enabled group programming, Flow shows co-authored commits as squares in the **Work log** when the Group filter is enabled.

![Square commits in Work log.](media://844720d8-4d42-4108-a4d5-013f514be765)

Click a group commit to see more details.

![Group commit pin drawer in Work log.](media://8baa2200-aad3-4ec1-92e8-08aa893549de)

If Flow missed a commit or added too many authors, update the commits manually.

Learn more about [manually marking a group commit](https://appfire.atlassian.net/wiki/spaces/FDDRAFT/pages/2892530140).