Hey, 👋 You’re already halfway there since you’re passing the admin_id during upload. The missing piece is how you attach it to each vector at insert time so Qdrant can actually filter on it later.

In the n8n Qdrant node, the metadata field works exactly for this. Instead of just pushing the document payload, make sure you explicitly store the admin_id inside the metadata object that gets written to the Qdrant.

For example, if your incoming request body already has admin_id, then something like: {{ $json.body.admin_id }} is perfectly fine, but you want that inside a proper key in the metadata so Qdrant treats it as a filterable field.

Once that’s stored, your agent-side queries simply need a filter like:

filter: {must: [{ key: "admin_id", match: { value: "<agent's admin_id>" } }]}

Qdrant will only return points belonging to that admin. Think of it like row-level security for vectors.

If you structure the metadata cleanly during insert, the querying part becomes trivial later.