Microsoft 365 permissions
Knovara works entirely through delegated permissions — it acts as the signed-in person, never with a standing service account. Your Entra administrator consents once, for the organisation. These are the scopes we ask for and, just as importantly, the ones we do not.
Last updated September 2026
Scopes requested
| Scope | Used for |
|---|---|
openid profile offline_access | Sign-in from Teams and refreshing your session. |
Sites.Read.All | Discovering the SharePoint sites and lists your organisation has enabled, and reading list items you can already open. |
Files.Read.All | Searching and reading documents you can already open, to answer and cite. |
Files.ReadWrite.All, Sites.ReadWrite.Allonly if writes are enabled | Creating 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 Microsoft Search requires a broader delegated scope, Knovara enforces its own server-side site scope before any content reaches the model, so a broader consent never widens what is actually searched.
Explicitly not requested
Sites.FullControl.All, or any application-only (app-only) read or write scope. Knovara has no standing, non-delegated access to your content.Mail.*,Chat.*,ChannelMessage.*— Knovara is a Teams personal app; it does not read mail, chats or channel messages.Directory.*beyond what sign-in needs.
What consent does and does not grant
Admin consent enables sign-in and delegated calls; it does not grant Knovara access to content on its own. Every Graph call runs as the signed-in employee, limited to what that employee can already open, and — for writes — re-authorised at the instant of the change. New permissions in a future release require a fresh, explicit consent; nothing is added silently.
Two independent controls sit on top of Graph's own permission trimming: an administrator-set site scope (a named allowlist, or "everything the person can open"), enforced server-side before content reaches the model; and a per-organisation pause switch and usage ceiling.
The full endpoint-by-endpoint matrix (each Graph call, its minimum proven scope, and the exact admin-consent text) is available on request from the trust center.