Skip to main content
Version: Latest

BrokerResearchProactiveRejectionReason

description

Reason a row was rejected on proactivelyEntitleBrokerResearchUsers.

enum BrokerResearchProactiveRejectionReason {
  USER_NOT_FOUND
  COMPANY_NOT_FOUND
  USER_NOT_RTR_ELIGIBLE
  USER_PERSONA_NOT_ON_BROKER_ENTITLE_POLICY
  USER_ALREADY_FULLY_ENTITLED
  COMPANY_HAS_NO_ENTITLED_USERS
  COMPANY_ALREADY_FULLY_ENTITLED_FOR_ALL_PERSONAS
  INVALID_GROUP_IDS
  ENTITLEMENT_FAILED
}

Values​

BrokerResearchProactiveRejectionReason.USER_NOT_FOUND​

BrokerResearchProactiveRejectionReason.COMPANY_NOT_FOUND​

Reserved — the current BE never emits this value. An unknown company_id lands in COMPANY_HAS_NO_ENTITLED_USERS and a post-validation exception lands in ENTITLEMENT_FAILED. Retained on the enum for forward-compatibility so removing it is not a breaking change for federated clients that switch on it.

BrokerResearchProactiveRejectionReason.USER_NOT_RTR_ELIGIBLE​

BrokerResearchProactiveRejectionReason.USER_PERSONA_NOT_ON_BROKER_ENTITLE_POLICY​

BrokerResearchProactiveRejectionReason.USER_ALREADY_FULLY_ENTITLED​

The target user already holds every non-AMR group in the provider's catalog — nothing left to grant.

BrokerResearchProactiveRejectionReason.COMPANY_HAS_NO_ENTITLED_USERS​

BrokerResearchProactiveRejectionReason.COMPANY_ALREADY_FULLY_ENTITLED_FOR_ALL_PERSONAS​

Every persona the provider entitles for at the target company is already fully entitled — the firm-level fan-out would be a no-op.

BrokerResearchProactiveRejectionReason.INVALID_GROUP_IDS​

BrokerResearchProactiveRejectionReason.ENTITLEMENT_FAILED​

The row passed every validation gate but the downstream approve pipeline raised. Row identity (userId / companyId) is preserved on the response so the caller can retry or investigate. Emitted only by the defensive except-block on the BE entitle endpoint.

Member Of​

BrokerResearchProactiveRejectedRow object