Use case
LiveWhose documents, whose permissions, whose answer.
One index, scoped to the person asking. A community manager queries the whole association; a homeowner queries their lot, their tract, and the amendments recorded against it — and neither sees a corpus they have no business reading.
The problem
Most document search treats permissions as a filter applied after retrieval: find the answer, then decide whether to show it. That leaks. A homeowner asking about delinquency procedure should not be able to surface another owner's account, and a manager covering forty associations should never get an answer drawn from the wrong one's declaration. Scoping has to happen before retrieval, not after.
What Covenance does
Identity is query context. Each association is its own index, and each asker carries the scope they're entitled to — association, tract, lot. Retrieval runs inside that boundary, so an answer that would require documents outside it is not filtered out of the response; it was never a candidate. The citation names the document the asker could have opened themselves.
- Scope
- Per-association index, then per-tract and per-lot scoping inside it. Cross-association retrieval is not possible, not merely discouraged.
- Who asks
- Community managers and management leadership today. Homeowner access is member-gated behind the association's portal and branded to it.
- On refusal
- Out-of-scope questions route to the manager rather than answering from a document the asker was never entitled to.
Send us the document set.
Fifteen minutes, and you'll see Covenance searching your own documents — including the questions it refuses.
Book a 15-minute call