When using HipChat v2 authentication tokens, the HipChat Plugin currently requires either a personal token, or a room-specific token to be stored within Jenkins. This means that you either have to accept all notifications coming from an existing user account (which costs a HipChat license), or you are constrained to using a single Room Notification token for each build job (which prevents you sending notifications to multiple rooms). Clearly you can revert to v1 API behaviour, but this prevents using the new Card notifications.

Ideally the HipChat plugin should install itself against HipChat using an Add-on generated token (see https://developer.atlassian.com/hipchat/guide/hipchat-rest-api/api-access-tokens). This could be installed against all rooms or single rooms within a HipChat instance. It would also remove the need for a specific user-account for notification messages.