Usage, activity, and API key limits follow the active organization

Usage and activity are scoped to the active organization, API key limits apply per organization, and existing keys can be assigned to the current organization.

Usage and activity views now include events for keys in the active organization and organization-unscoped keys. Organization-less API sessions continue to see usage and activity across all of the owner's keys.

The 10-key limit now applies per organization, including organization-unscoped keys visible there. Organization-less API sessions keep the user-wide 10-key limit.

Keys can be explicitly assigned to the current organization. Keys created before organization scoping, or created by organization-less API sessions, remain visible in all of the owner's organizations until they are assigned.