Member Junction
    Preparing search index...

    The scope a notification is sent in, mirroring the polymorphic scope MJ's AI layer carries for scoped prompt configs and parts: a primary record of any entity (an Application, a Company, …) plus named secondary dimensions. The engine adds the recipient and the recipient's roles as primary-scope candidates itself, so a caller names only what it knows, usually its application and the notice's origin.

    interface NotificationScope {
        primaryScopeEntityId?: string;
        primaryScopeRecordId?: string;
        secondaryScopes?: Record<string, SecondaryScopeValue>;
    }
    Index

    Properties

    primaryScopeEntityId?: string
    primaryScopeRecordId?: string
    secondaryScopes?: Record<string, SecondaryScopeValue>