Skip to content

docs: RBAC for text and vector search - #1719

Merged
vpavicic merged 1 commit into
release/3.13from
docs/text-vector-search-rbac
Aug 12, 2026
Merged

docs: RBAC for text and vector search#1719
vpavicic merged 1 commit into
release/3.13from
docs/text-vector-search-rbac

Conversation

@DavIvek

@DavIvek DavIvek commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Release note

Document how fine-grained access control (RBAC) applies to text search and vector search. Results are now filtered per node/relationship: an entity is returned only if the caller can read it (its labels or edge type, and both endpoints for relationships) and the property the match came from (the queried property for search, every indexed property for search_all/regex_search, the embedding for vector search). Denied hits are silently dropped, and text_search.aggregate returns an error under fine-grained restrictions.

Related product PRs

PRs from product repo this doc page is related to:
memgraph/memgraph#4316

Checklist:

  • Add appropriate milestone (current release cycle)
  • Add bugfix or feature label, based on the product PR type you're documenting
  • Make sure all relevant tech details are documented
  • Check all content with Grammarly
  • Perform a self-review of my code
  • The build passes locally
  • My changes generate no new warnings or errors

Add an "Access control" section to the text-search and vector-search pages
explaining how fine-grained access control filters results: a node or
relationship surfaces only if the caller can read it (labels/type, and both
endpoints for relationships) and the matched/indexed property. Notes the
per-procedure property gating (search vs search_all/regex), silent dropping,
the aggregate limitation, and wildcard-index per-result filtering.
@DavIvek DavIvek self-assigned this Aug 10, 2026
@vercel

vercel Bot commented Aug 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
documentation Ready Ready Preview Aug 10, 2026 12:58pm

Request Review

@DavIvek
DavIvek marked this pull request as ready for review August 11, 2026 07:44
@DavIvek DavIvek added this to the 3.13 milestone Aug 12, 2026
@vpavicic
vpavicic merged commit 5262ca5 into release/3.13 Aug 12, 2026
2 checks passed
@vpavicic vpavicic mentioned this pull request Aug 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants