bridge-38

Here is a formalized, professional draft tailored for your Teams channel. It is structured to be clean, scannable, and direct, ensuring your colleagues can quickly understand the requirements and action items for the COMET NAM deployment.

📢 Teams Discussion Draft: COMET GUI Deployment (NAM Group Setup)

Hi Team,

As we begin kicking off the COMET GUI deployment for the NAM (North America) group, we want to proactively align our setup based on the lessons learned and decisions made during the EMEA migration.

To ensure a smooth onboarding for the NAM environment on Citi Desktop, I have compiled our key operational requirements and open questions below:

1. User Visibility & EEMS Group Mapping

Context: In Citi Desktop, users can only see an application configuration if they belong to its designated EEMS group.
Action/Question: We need to confirm if our NAM users are already mapped to the appropriate EEMS group, or if we need to request the UI Platform team to perform a bulk migration/entitlement sync for the NAM user base.

2. Administrative Access & Configuration Permissions

Context: For EMEA, the UI Platform team provisioned a dedicated developer admin group (app_harness_ls_157514_comet-emea_developer) to manage configurations and handle UAT promotions.
Action Required: We need to request the creation and provisioning of a parallel administrative group for our team—specifically: app_harness_ls_157514_comet-nam_developer—to grant us administrative control over the COMET NAM configuration.

3. Active Directory (AD) Group for Production Promotions

Context: Moving builds to production requires a designated AD group to authorize and execute promotions.
Action Required: The NAM team needs to identify and agree on the correct AD group (likely our production support group) to be mapped for NAM production promotions.

4. Isolated Standalone Application Configuration

Context: Per the core migration strategy, we are moving away from multi-stream dropdowns. EMEA was successfully configured and troubleshooted as its own isolated application definition.
Action Required: We must initiate the same process for comet-nam, actively configuring and troubleshooting it as a distinct, standalone application definition in the directory rather than bundling it under shared configurations.