[UI Feature] Display user identity in the UI

[mys007]

Motivation: Why do you think this is important?

The user identity of execution (and ideally also workflow registration) user should be available in the UI. This would enable good collaboration because one could easily see which workflows and which executions belong to which users.

Goal: What should the final outcome look like, ideally?

• Besides the JWT subject claim (which is the current "user" as in ExecutionIdentity), one should also store a real user name in the postgres backend.
• It should be possible to filter executions by user (now it's just executions belonging to the current user or all executions)
• User info would be also a special column in the executions overview.
• User info would be also linked to versions (registrations).

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

Displaying user identity in the Flyte UI for executions is already supported: executions store the principal (user identity) and this can be shown and filtered in the UI, such as with the "Only Mine" toggle or by filtering on the user/principal field. However, filtering by user is not available for workflows, tasks, workflow versions, or launch plans, as these entities do not store the principal; only executions do. Storing and displaying a real user name (beyond the JWT subject) in the backend is not currently implemented, but the system does persist the principal for executions and exposes it for filtering and display in the UI. Linking user info to workflow registration (versions) is not supported, as user identity is not tracked for those entities. See the discussion and implementation details in the linked issues and RFCs for more context.

For executions, the user identity is stored in the metadata and can be filtered in the UI and via API. The UI can display this information as a column in the executions overview, but this is not available for workflow registration or versioning. If you need more detail on how to enable or use these features, or on the technical limitations for other entities, let me know.

Sources:

• feat: "Only Mine" Global Toggle

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[mys007]

@RunLLM How can you filter on the user/principal field? I cannot see such thing in the UI?

[runllm]

You can filter executions by user/principal in Flyte because the execution entity stores the principal (user identity) in its metadata. In the UI, this is typically exposed via the "Only Mine" toggle, which filters executions to those launched by the current user. However, there is no general-purpose user/principal filter input in the UI for arbitrary users; filtering by user is only available for the current authenticated user via this toggle. Filtering by user/principal for other users is supported via the API using the user field, but not directly in the UI for arbitrary user values. This limitation is confirmed in the implementation and issue discussions—filtering by user is not available for workflows, tasks, workflow versions, or launch plans, only for executions, and only for the current user in the UI. See the linked issues for details and API filter syntax.

If you want to filter executions by a specific user/principal other than yourself, you must use the API and specify a filter like eq(user,username). The UI does not currently provide a text field or dropdown to filter by arbitrary user/principal values—only the "Only Mine" toggle for your own executions is available. Would you like more detail on how to use the API for this purpose?

Sources:

• feat: "Only Mine" Global Toggle
• Allow executions to be filtered based on who launched them
• Flyte Admin API filterable fields

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!