Permission-aware context access
Control which agent, group, and user can reach each file.
Department
General
See all use cases
Access control decides who can see what. In a company, not everyone should read every document, and the same holds for the agents acting on their behalf. Permission-aware access means each request, from a person or an agent, only reaches the files that identity is allowed to see.
Agents get all-or-nothing access
Connect a knowledge base to an agent and it usually sees everything or nothing. Either sensitive files are exposed to any agent that asks, or access is locked down so hard the agent is useless. There is rarely a way to say that this Client can read these folders for this group, so companies either overshare or give up on connecting real data.
Qontext as the permission layer
In Qontext, every file and folder carries permissions for users and for Groups, and each Client connects through an API key that reaches only what it is scoped to. An API key can inherit its owner's read access or be scoped by hand per folder, and it can read or edit but never manage permissions, so connecting an agent never widens what a person could already see. Access can be widened deeper in the tree but not narrowed, so a folder's rules hold for every agent that touches it.
Get started
Set permissions on your folders for the users and Groups that should reach them.
Give each Client an API key scoped to only the folders its agents need.
Review retrieval logs to confirm which files an agent actually reached.