When developers’ applications authenticate with refresh tokens and do not specify an organization_id, the response now includes the most recently used organization for that session. Previously, the response only included the organization if it was part of the session’s initiation.
The new behavior is helpful for onboarding flows that create new organizations. Before this change, if a user signed up and the developer’s application created a new organization and switched the user into that organization, token refreshes would not include the new organization. Now, token refreshes will include the new organization.
