Design: UserId and GlobalUserId Field Clarifications

Modified on Mon, 30 Dec, 2024 at 12:09 PM


The use of these two fields are clarified below, and can also be found in the descriptions of mutation input fields as to whether a workspace or a global user ID should be provided.


DesUser type

The UserId field in DesUser type is nullable.

  • It may only return null on desUserByGlobalId or desUserByAuth queries
  • Anywhere a user is returned, the UserId should be asserted as not null, if required.


The GlobalUserId field:

  • Will only return null if the user is not found globally

Task DesUser

The UserId field returns the workspace user ID (not the global user ID), as seen in desWorkspaceTasks and desProjectTasks

Global desUser

The UserId field will always return null for global user queries, as seen in desUserByGlobalId and desUserByAuth


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article