# Configure Agent Mappings

## Objective

Set an agent's business attribution when their inherited group mapping is too broad. An individual **Brand**, **Market**, or **BPO** mapping can make workforce reports reflect the agent's actual assignment.

## Environment

- You can manage **Data Mappings**.
- The agents and their group memberships are available in the workspace.

## Resolution

1. Open **Settings**, select **Mappings**, and open the **Agent Mappings** tab.
2. Find the agent and review their group memberships and the **Brand**, **Market**, and **BPO** values inherited from those groups.
3. Leave **Inherit from groups** where the group mapping is correct. Select an individual **Brand**, **Market**, or **BPO** value only where that agent needs an override.
4. If **BPO Rules** controls the **BPO** value, review its email-domain rule instead of trying to change a locked **BPO** selector. Enabled matching rules take precedence over the row's **BPO** choice.
5. Use **Bulk Editor** when the same override applies to several agents. Select **Save Mappings** after reviewing the affected agents.

> Canonical page: https://zenops.cx/help/articles/configure-agent-mappings/
> Audience: For administrators
> Summary: Override inherited group attributes for agents whose assignments need more precise workforce attribution.

## Notes on this article

### Note: BPO rules take precedence

After step 4 in resolution. An enabled email-domain rule can control an agent's BPO value. Check BPO Rules when that value is locked or unexpected.

## Visual references

- Anonymized Agent Mappings example showing inherited values, group membership counts, and BPO rule controls.: [Anonymized Agent Mappings table with fictional agents and inherited Brand, Market, and BPO values.](https://zenops.cx/help/assets/realtime-agent-mappings-anonymized.png)