---
title: "When batch loading users into the Pharos database, users' groups don't change within Pharos to match their domain."
slug: "when-batch-loading-users-into-the-pharos-database-users-groups-dont-change-within-pharos-to-match-their-domain"
updated: 2024-04-01T14:34:34Z
published: 2024-04-01T14:34:34Z
canonical: "kb.pharos.com/when-batch-loading-users-into-the-pharos-database-users-groups-dont-change-within-pharos-to-match-their-domain"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pharos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# When batch loading users into the Pharos database, users' groups don't change within Pharos to match their domain.

When loading users from a Windows domain into the Pharos Database using the Pharos batch load utility, users can be added to a group within Pharos matching the user's domain group.

When re-running the batch load to add new and update existing users, if existing users have their group changed within the domain, these changes aren't reflected within the Pharos database after the batch load is complete.

---

This is expected behavior.

Users can belong to multiple groups in a domain, but they can only belong to a single group in the Pharos database. So when a user is first imported into the Pharos database, their group is set based on the group that is imported first. As the remaining groups are imported, the same users can potentially come up again and again, but their group membership in the Pharos database is not changed.

## Related

- [Help! I Don't Have Any Reporting Data in Blueprint!](/help-i-dont-have-any-reporting-data-in-blueprint.md)
- [The Pharos Print App for iOS is not connecting to the server, I can't login.](/the-pharos-print-app-for-ios-is-not-connecting-to-the-server-i-cant-login.md)