It would be useful for geoprocessing tools executed in ArcGIS Enterprise—especially when triggered from Experience Builder or other web applications—to have direct access to the identity of the user who initiated the execution.
Currently, the execution context of a Python script in a Geoprocessing service does not consistently provide this information. Adding an accessible property to this context, allowing retrieval of the user name or Portal user ID, would greatly improve the traceability, auditing capabilities, and flexibility of geoprocessing tools.
