Currently VectorChatMemoryAdvisor stores conversationId as metadata and use it for similarity search. This chats are not directly linked to user.

Option 1: New Table for Chat and Conversation IDs Create a new table to store both chat IDs and conversation IDs. Link chat data to the vector store using chat IDs.

Option 2: Add User IDs as Metadata Add userId as metadata alog with conversationId. Custom Advisor: I think there's no built-in support for adding custom metadata in VectorChatMemoryAdvisor, you'll need to develop your own advisor to handle this.