An assistant that knows your organization: and respects its permissions
An internal knowledge assistant that answers your employees from approved sources only: every answer carries its references, every question passes through the asker's permissions, and every access attempt is recorded in the audit trail. Institutional knowledge reaches the people entitled to it: and leaks to no one else.
A governed knowledge library, not an open sea
The assistant answers only from knowledge collections your organization has approved: each with a content owner, a sync source, and a declared access scope.
Every knowledge collection has a content owner and a declared access scope: and the assistant never sees past it.
Every answer carries its source
An answer without a reference is an opinion: and the assistant doesn't offer opinions.
The assistant answers from approved documents alone, attaching its references to every answer: document name, version, and approval date. When no approved source exists, it says so plainly: “I have no approved source for this question”: instead of a guess that costs your employee a wrong decision.
Document name, version, and approval date: with every answer, not on request.
When a document changes in its system of origin, the answer changes: automatically.
Out-of-scope questions are declined and logged: without exposing anything unauthorized.
Same question: an answer sized to the permission
The assistant reads with the asker's identity, not the system's.
Two employees ask the same question and receive two different answers: each to the extent of their own permissions. Anything beyond the asker's scope never appears in the answer: not in the text and not in the references. Exceptions go through a documented approval from the content owner: never a silent permission expansion.
| Employee | Dept. manager | Compliance team | |
|---|---|---|---|
| HR policies | Access | Access | Access |
| Procurement procedures | Blocked | Access | Access |
| Technical guides | Access | Access | Blocked |
| Compliance documents | Blocked | With approval | Access |
Knowledge that doesn’t know who is reading it isn’t an institutional asset: it’s a deferred risk.A principle from NOVA's knowledge-governance philosophy
What teams ask before adopting
No. The assistant queries with the asker's own identity and permissions: not the system's. Anything beyond the employee's scope never enters the answer: not as text, not as a citation, not even as a hint that the document exists. Out-of-scope attempts are recorded in the audit trail without exposing the content.
From approved knowledge collections your organization defines: policies, procedures, and guides: each with a content owner and a declared access scope. Whatever is not in the approved sources, the assistant does not answer: it states that no approved source exists instead of guessing.
Sources sync from their systems of origin: the HR system, the internal procedures portal, and others: and every answer shows the document version and its approval date. When the source changes, the answer changes; previous versions stay in the log for review.
Yes. It runs under the same NOVA deployment options: NOVA Cloud inside Saudi Arabia, your own private cloud (VPC), or on-premises in your data center: including fully air-gapped environments. Details on the deployment & sovereignty page.
What stands behind the assistant?
The Arabic understanding engine
How NOVA's engine understands the question: dialect and context included: before searching your sources for the answer.
Explore the enginePersonal data protection (PDPL)
How access controls and data minimization support your obligations under the law.
Read our positionIllustrative case templates
Anonymized, clearly-labeled templates of governed knowledge and service workflows in Saudi sectors.
See the templatesYour organization’s knowledge, under its control.
Show us your knowledge sources and your employees' most repeated questions: and we'll come back with a practical blueprint for a governed assistant that respects your permissions.