Security and deployment

Designed so your IT and security teams can say yes.

This page states plainly what Knovara can access, what it does with it, what it keeps, and where it runs. If a question isn't answered here, write to support@knovara.app and we'll answer it in writing.

Access: the signed-in person's, never more

Knovara works through delegated permissions. When you ask a question, Knovara searches and reads SharePoint as you, using a token issued for your Microsoft 365 account. There is no service account with standing access to your documents, and Knovara cannot see anything you cannot open yourself.

Your Entra administrator reviews and consents to the delegated scopes once, for the whole organisation. Knovara is a Teams personal app only; it does not read channel messages, chats or mail.

Delegated permissions requested

ScopeUsed for
openid profile offline_accessSign-in from Teams and refreshing your session.
Sites.Read.AllFinding the SharePoint sites and lists your organisation has enabled, and reading list items you can already open.
Files.Read.AllSearching and reading documents you can already open, to answer and cite.
Files.ReadWrite.All, Sites.ReadWrite.All only if writes are enabledCreating a new document from an approved template, and updating an item in an approved list. Not requested for read-only deployments.

Where Microsoft Graph supports resource-specific consent (Sites.Selected and the Selected file and list operations), we prefer it and scope access to the sites you choose. Where Search requires a broader delegated scope, Knovara enforces its own server-side site scope before any content reaches the model.

Explicitly not requested

  • Sites.FullControl.All or any application-only (app-only) read/write scope.
  • Mail.*, Chat.*, ChannelMessage.*.
  • Directory permissions beyond what sign-in needs.
Site scope is yours to set. Knovara can be limited to a named list of SharePoint sites, or allowed to search everything the signed-in person can already open. Either way, Microsoft's own permission trimming applies to every search result.
Tenant controls. Each organisation has a pause switch that stops Knovara immediately, a monthly usage ceiling that cannot be exceeded, and a disconnect procedure that revokes access and ends processing.

What Knovara keeps, and what it never keeps

Documents are read at answer time and passed to the model with your question. Knovara does not build a copy of your document library.

KeptNever kept
  • Metadata about sources used in an answer (site, document identifier, version) so a later question can re-check access.
  • Audit records: who asked, when, which sources were used, what was changed and its outcome.
  • Conversation state for follow-up questions, for a bounded time.
  • Usage counts for the monthly ceiling.
  • Document text, in the database, in logs, in analytics or in error messages.
  • Access tokens beyond the request that uses them.
  • Secrets of any kind in logs.

Prompt safety

Everything retrieved from a document is treated as untrusted data, never as instructions. Instructions that appear inside a document ("ignore your rules", "email this file") are not followed; Knovara has no ability to send mail, share files or call other tools from an answer.

Writes: previewed, confirmed, reconciled

Knovara never writes on its own. Every change follows the same path:

  1. Preview. Knovara shows exactly what will be created or changed.
  2. Confirm. You approve it. The confirmation is bound to that exact preview and expires after 15 minutes.
  3. Re-authorise. Your access is re-checked at the moment of the change, not when you asked.
  4. Execute safely. New documents are always new files (a name clash fails rather than overwrites). List updates are conditional on the item not having changed since your preview; if it has, you see the latest version and preview again.
  5. Read back. Knovara reads the result before it tells you the change succeeded, and never reports success it hasn't verified.

Templates and lists are approved by your administrators in advance. The model proposes the content; deterministic code validates and performs the change.

Deployment

One isolated deployment per customer, in your cloud.

Knovara is not a shared multi-tenant service. Each customer gets a dedicated deployment that only that customer's Microsoft 365 tenant can reach.

Your account, your region

Deployed into an AWS account you provide (Azure on request), in the region you choose for data residency. Infrastructure is defined as code and reviewed with you.

Model inside your account

Knovara runs on Claude models through your cloud's model service — Amazon Bedrock in your AWS account, or Azure OpenAI — so prompts and documents are processed within your account.

Private by construction

Private database, secrets held in your cloud's secret manager and injected at runtime, encrypted in transit and at rest, and a per-deployment cost budget with alerts.

  • Identity stays with Microsoft. Sign-in is your Entra ID; Knovara stores no passwords.
  • Upgrades are rolling behind health checks, and every release is pinned by version.
  • Offboarding is a procedure, not a promise: consent revoked, deployment destroyed, records exported or deleted on your instruction.

Certifications and assurance

Knovara does not currently hold a SOC 2 report or ISO 27001 certification, and we will not imply otherwise. What we can give you today is the architecture described on this page, our permission matrix, our data-handling and offboarding runbooks, and answers to your security questionnaire in writing. Ask at support@knovara.app.

Microsoft, Microsoft Teams, SharePoint and Entra ID are trademarks of the Microsoft group of companies; Amazon Bedrock is a trademark of Amazon.com, Inc. Knovara is an independent product and is not endorsed by either.