Major user entity update

The GraphQL User type and Query.users are updated across two API versions:

• 2026-07: New fields, types, enums, Query.users arguments, the user_configs query, and stricter pagination on users.
• 2026-10: Legacy fields on User are planned for removal. Treat removal timing as subject to the published API schema for your version; migrate off legacy fields as soon as you target 2026-07 or later.

If you only use User.id, User.email, User.name, and User.kind, you do not need changes for those fields. If you use photo URL fields, kind/status booleans, is_verified, join_date, or the old users(kind: …, newest_first: …, non_active: …) arguments, review the sections below.

For step-by-step migration examples, follow the User and users sections in the monday.com API reference for the API version you target.

Changes in 2026-07

New User fields

Existing fields (type updates in 2026-07)

These fields are also served in the updated shape from 2026-07:

• User.created_at: Date → ISO8601DateTime!
• User.birthday: Date → String (breaking type change)
• User.utc_hours_diff: Int → Float (breaking type change)

email, name, kind, and created_at remain; only the types above change where noted.

New types

• PhotoUrl — original, small, thumb, thumb_small, tiny (each String).
• UserConfig — kind: String!, role_id: ID!, visibility: [String!]!.

New enums

• UserStatus: ACTIVE, INACTIVE, PENDING.
• InvitationMethod: USER, SCIM, SSO, AUTH_DOMAIN, FIRST_USER, CONSOLIDATION, INTERNAL_CREATION, UNKNOWN, SERVICE_PORTAL_AUTH_DOMAIN, SERVICE_PORTAL_USER_INVITATION, API_USER_CREATION.
• UserKindFilter: Individual kinds (ADMIN, MEMBER, GUEST, VIEW_ONLY, AGENT_MEMBER, PORTAL), kind groups (BASIC = admin + member + guest + view_only), and API-user kinds (PORTFOLIO_API_USER, NEXUS_API_USER, RESOURCE_DIRECTORY_API_USER, OMNICHANNEL_API_USER, GOALS_API_USER, PROJECTS_API_USER, SPRINT_MANAGEMENT_API_USER, CRM_COMMERCE_API_USER, CAMPAIGNS_API_USER, DATA_RETENTION_API_USER, MONDAY_SERVICE_API_USER, AI_PLATFORM_AGENT_API_USER, DEPENDENCIES_API_USER, HISTORICAL_TRACKING_BACKFILL_API_USER).
• UsersSortField: CREATED_AT.
• UsersSortDirection: ASC, DESC.

New input types

• UserKindFilterInput: in: [UserKindFilter!], not_in: [UserKindFilter!].
• UsersSortInput: field: UsersSortField!, direction: UsersSortDirection!.

New Query.users arguments

Deprecated Query.users arguments (2026-07)

kind, newest_first, and non_active are deprecated on Query.users starting in 2026-07 and marked with @deprecated in the schema. They still work at runtime in 2026-07 and 2026-10, but clients that introspect with includeDeprecated: true will see the deprecation reasons below:

Update integrations and codegen to the new arguments above. A removal version has not been announced; monitor the release notes for the version your integration targets.

New query

user_configs(kinds: [String], visibility: String): [UserConfig!]!

Returns user configs for the account, sorted by role_id ascending. Requires users:read and appropriate authorization.

Pagination on Query.users (breaking)

Integrations that omitted limit may see fewer results. Use limit with page (and sort as needed) to paginate explicitly.

Query.users(emails: …) nullability

Argument type changes from [String] to [String!] in 2026-07. Do not pass null entries in the emails array.

Planned in 2026-10

The following User fields are planned for removal in 2026-10 (verify with introspection or release notes for the version you call):

• Photo: photo_original, photo_thumb, photo_thumb_small, photo_tiny, photo_small
• Kind flags: is_guest, is_admin, is_view_only
• Status flags: is_pending, enabled
• Other: is_verified, join_date, encrypt_api_token, sign_up_product_kind

In some preview builds these fields may still appear in introspection or return data until removal is fully rolled out. Do not rely on them for new work; use the replacements below.

Deprecated fields → replacements

Further reading

• monday.com API documentation — versioning, authentication, and reference for User, Query.users, and related types.
• API release notes and changelog on the developer site for the exact behavior of each API-Version you call.