Atlas project production

HR / Aeries / Google Preferred Name Synchronization

Carries HR-maintained preferred-name changes through the staff identity pipeline so downstream directory and display systems stay aligned.

Internal-only entry. Do not publish externally without review.

Type: Component
Lifecycle: Active
Last touched: 2026-03-24
Visibility: Internal

Purpose

Update preferred-name and name-change information across systems based on HR-maintained values.

Current state

Preferred-name logic is active in the production staff export and downstream directory sync path as a component of Staff AD Account Management.

Next step

Document the full downstream target map, reconciliation rules, and exceptions process inside the parent staff AD runbook.

Interfaces

Inputs

preferred-name and legal-name HR fields
staff export SQL
directory sync configuration

Outputs

updated display names
directory-sync inputs
identity reconciliation artifacts

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Contributes in this stage.

Human Interfaces

Not in scope.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

OCDE HR is canonical for preferred-name and legal-name source fields.
Downstream directories should mirror the export path unless an explicit exception is approved.

Safe handling

Limit access to HR extracts and identity logs.
Document rollback expectations before changing downstream mappings.

Operational notes

Reliability posture

Preferred-name handling is embedded in the production staff export path, but exception handling and rollback are still lightly documented.

Observability

Integr8r logs
post-processing logs
directory sync outcomes

Security and privacy

Confidential staff identity data; name-change workflows should remain restricted to authorized staff.

Dependencies

Upstream

OCDE HR 2.0
ActiveDirectoryStaff export
Google directory sync path

Downstream

Active Directory
Google Workspace display names
other downstream account displays

Ownership

Owners

Technology Services, Josh Barton

Users

Technology Services, HR, Josh Barton (owner)

HR / Aeries / Google Preferred Name Synchronization

Operational Notes

The registry points to ActiveDirectoryStaff/SQL/BOUSD-Staff.sql as the place where preferred-name precedence is defined.
The same production job then flows into local PowerShell processing and Google directory sync.
Failure results in inconsistent names and manual correction work across staff-facing systems.

Registry Alignment

Former standalone registry entry INT-011 is now documented as component scope within Staff AD Account Management.
Registry clarified: preferred-name handling is embedded in the active identity export path and is not only a downstream cleanup routine.
Validation gaps: document the exact downstream systems touched and the reconciliation rules for exceptions.