# Triggering a Schedule: \`identity\` Does Not Include The User's Name **URL:** \ **Category:** Server Deployment\ **Tags:** web-ui\ **Created:** [June 15, 2026, 2:06pm UTC](https://community.temporal.io/t/triggering-a-schedule-identity-does-not-include-the-users-name/19666 "2026-06-15T14:06:44Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Albert-at-Gemini](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/albert-at-gemini/32/6783_2.png) [@Albert-at-Gemini](https://community.temporal.io/u/Albert-at-Gemini)\ **Post date:** [June 15, 2026, 2:06pm UTC](https://community.temporal.io/t/triggering-a-schedule-identity-does-not-include-the-users-name/19666/1 "2026-06-15T14:06:44Z")
Hi, We are trying to setup a self-hosted Temporal server. We’re running into the issue where triggering a schedule creates a workflow whose’s first event history item contains an `Identity` field. The issue is that the `Identity` field only contains the schedule’s name. It is missing the user who triggered it. I remember this is a feature in Temporal Cloud. How can we set this up for our self-hosted deployment? Note: We’ve already setup RBAC (shout out to Bitovi for [this article](https://www.bitovi.com/blog/implementing-role-based-authentication-for-self-hosted-temporal)). ps: I think I saw this issue somewhere else, but I can’t find it again. Apologies if this is a dupe. Thanks! ---
**Author:** ![neuodev](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/neuodev/32/8403_2.png) [@neuodev](https://community.temporal.io/u/neuodev)\ **Post date:** [June 15, 2026, 4:21pm UTC](https://community.temporal.io/t/triggering-a-schedule-identity-does-not-include-the-users-name/19666/2 "2026-06-15T16:21:52Z")
I am not aware of this `Identity` filed but If you want to track such information, you can add it as `typedSearchAttributes` or as `memo` filed when creating the schedule.