01 · Permission-aware recall
Permission-aware by design.
Nura works from approved workplace sources and treats access as part of recall. A user or authorized agent only receives the context available to that identity and workspace.
SECURITY & PERMISSIONS
Company memory only works when
trust survives retrieval.
Nura is built to keep evidence, access boundaries, and uncertainty visible
as company context becomes recallable.
HOW TRUST WORKS
Trust survives retrieval on four principles.
02 · Provenance
Source stays with the answer.
Nura keeps sources, ownership, dates, and status attached to company memory, making important context easier to verify and keeping the path back to evidence clear.
03 · Conflict and uncertainty
Confidence doesn’t erase conflict.
When the available evidence conflicts or is incomplete, that limitation stays visible. The goal is not to manufacture certainty; it is to make the company's actual context easier to review.
04 · Workspace governance
Workspace-level governance.
Workspace admins manage who and what contributes to company memory, keeping source access and configuration visible, controlled, and aligned with how the workspace operates daily.
PERMISSION-AWARE RETRIEVAL
The question can be shared. The answer cannot cross access.
IdentityPerson or approved agentRetrieval begins with the identity asking the question.
Approved sourcesConfigured workspace accessNura only uses evidence available under the configured source model.
AnswerPermitted company contextThe answer remains traceable to the available evidence.
NORTHSTAR EXAMPLE
See permission-aware recall in practice.
Asked
FAQs
Security questions.
01Does Nura respect existing permissions?
Nura is designed to retrieve only information available to the requesting identity under the configured workspace and source access model.
02Can an administrator disconnect a source?
Yes. Administrators can revoke or remove connected sources from the workspace.