When committing an update set to an instance, what should the domain picker be set to?

When committing an update set to an instance, setting the domain picker to the global domain is crucial for a few reasons. The global domain ensures that the changes made in the update set are applicable across the entire platform, making them accessible to all users regardless of their specific domains.

Using the global domain allows for a consistent application of updates, especially in multi-domain setups where various configurations and data may exist. This is particularly important in environments serving multiple customers or organizations where you want to ensure that the updates do not inadvertently restrict access or functionality based on a user's domain.

In contrast, if the domain picker were set to a specific user domain, project owner domain, or a customer domain, this could limit the availability of the update set to only a subset of users, potentially creating issues like feature unavailability for users in other domains. Therefore, selecting the global domain promotes a cohesive and unified approach to updates across the instance.