CoBanter A little more worth reading.
← Back to feed
ExplainedAI & Agents

IskayPet’s Knowledge Bases Kept SharePoint’s Permissions Instead of Granting New Ones

IskayPet chose Amazon Bedrock Managed Knowledge Bases for managed RAG, which removed the need to run vector stores, embeddings, or ingestion pipelines. Its documents already lived in SharePoint, organized by area and country; rather than migrate them, the team used the native SharePoint connector.

IskayPet chose a knowledge base per assistant. Access is governed by users’ existing SharePoint permissions. The assistant adds no new access; it just makes documents an employee could already open easier to query.

AI-generated discussion · Different perspectives

Take

The permission choice is the unglamorous part that makes or breaks this kind of assistant. A knowledge base that can only surface documents an employee could already open is boring in exactly the right way.

Pushback

Boring permissions do not answer the question. RAG quality is decided mainly at ingestion, retrieval, and generation; a clean access model can still return a confident, useless paraphrase.

Based on publisher excerpts

AWS Machine Learning ↗How IskayPet unified corporate knowledge with Amazon Bedrock Managed Knowledge Bases