# What is permission-aware AI?

> Permission-aware AI applies each person's access rights during retrieval, so a model only sees what they're allowed to see. Here's how it works.

Canonical: https://www.klaie.ai/learn/permission-aware-ai
Updated: 2026-11-01

Permission-aware AI is AI that applies each person's access rights when it looks up information, so a model only ever receives what the person asking is allowed to see. The check happens before the model reads anything, not after it has written an answer.

## Four signs an AI tool is really permission-aware.

- **Access is checked at retrieval**: The search itself is limited to what the person can open, so restricted content is never fetched for them.
- **It runs as the person**: Each search uses that person's organization, role and access, not a shared account that can see everything.
- **Code enforces it**: The rules live in the database and the backend. A prompt can't change them, so a clever question can't get around them.
- **Access leaves a record**: Opening confidential material is written to an audit log, so you can see what happened.

## Why it matters

Company AI is useful because it can reach so much, and that's also the risk. Files get shared more widely than anyone intended, and some folders are meant for only a few people. If an assistant can read all of it for everyone, one plain question can surface a salary file or an unannounced deal.

Permission-aware AI keeps the reach and removes that risk. Everyone can ask anything, and each person gets an answer from what they could already open.

## Checking first or filtering later

There are two common ways to build this. One indexes everything through a single account and filters what the answer shows, so the content has already been read and the filter has to hold the line. The other applies access during the search, so restricted material never reaches the model.

Checking first is the stronger guarantee, because a model can't repeat what it never received.

## What people see when they lack access

A good system doesn't guess and doesn't hint at what's hidden. It says it can't find anything the person has access to, and offers a way to ask for access. The restricted content stays out of the answer because it was never part of the request.

## How Klaie does it

Klaie applies each person's organization, role and collection access in the search query itself. When Jordan in engineering asks about the company's finances, the restricted report is never fetched. Maya, who can open Finance, gets the numbers, and opening the confidential report is written to the audit log.

## Questions to ask any vendor

These separate a real permission check from a promise:

- Is access checked during the search, or after the answer is written?
- Does the tool read with each person's access, or through one shared account?
- Can a prompt change what a person is allowed to reach?
- What does someone see when they ask about something restricted?
- Is opening confidential material logged?

## Questions people ask

### What is permission-aware AI?

AI that applies each person's access rights while it looks up information, so a model only receives what the person asking is allowed to see.

### Is it the same as role-based access control?

They work together. Role-based access control decides who can open what. Permission-aware AI makes an AI tool respect those decisions when it retrieves information for someone.

### Can a clever prompt get around it?

Not when the check runs in the database. The restricted content is filtered out before a model sees anything, so there's nothing for a prompt to extract.

### Does it stop data going to AI providers?

That's a separate question. Permissions decide what a request can reach. Where the model runs decides who processes it. Klaie covers both, with permission checks on every search and Sensitive mode for work that should stay on a private model.