Devana
All applications

Argos

Your SharePoint, open to your agents.

Category
Documents & knowledge
Compatibility
  • On-premises
Works with

Your SharePoint. Connected to your agents.

Argos indexes your on-premises SharePoint sites, from version 2013 to Subscription Edition, and exposes them to your agents through an MCP server. ODIN extracts the content; search covers text, meaning and the knowledge graph. SharePoint permissions are collected with the documents: an agent only returns to a user what that user can read.

  • On-premises SharePoint
  • Search & knowledge
  • MCP-connected agents
  • Per-user permission filtering

What you can do

  1. Targeted synchronization

    Libraries, pages and subsites: choose the folders and metadata in your scope. Additions, changes and deletions are picked up at every run.

  2. SharePoint permissions enforced

    Argos collects permissions with the documents and applies removals at the next synchronization. The agent only returns what the user can read.

  3. One MCP server per team

    Create MCP servers with their own scopes and keys. Full-text, semantic and graph search are included.

In detail

What Argos does with your SharePoint. What your agents see of it.

Argos now collects SharePoint permissions with the documents and filters answers for each user. Here is how it enforces those permissions, syncs your sites, makes them searchable and exposes them to your agents.

An application that queries Argos on behalf of a user only receives the documents that user can read in SharePoint. The filter is switched on server by server.

Permissions collected at the source
During a full synchronization, Argos records who can read each site, library and item with unique permissions, subsites included.
Removals applied
Every incremental synchronization reads SharePoint’s security change log: permissions removed, inheritance broken or restored, groups changed.
Identity verified
The application sends the user’s token (X-User-Token header), validated with Entra ID, ADFS, Keycloak, Authentik or Devana.
Active Directory
The user’s groups are resolved over LDAPS, nested groups and other forests included. SAML and FBA identities are declared through mappings.
Cautious when in doubt
The token narrows what the key can see and never widens it. When in doubt, access is reduced. A document the user cannot read is reported as not found.
Tested before it is switched on
Test a user: provider, groups, readable documents per site. The filter can only be switched on once a directory and a provider have been tested.

Good to know: a permission removed in SharePoint applies at the next incremental synchronization. Drafts are indexed like published versions, and site collection administrators see fewer documents through MCP than in SharePoint.

Runs on your premises.

Where this application runs, and the technologies that come with it.

Plan your deployment
On-premises
On your servers, with a configuration sized for you.
Requirements
Argos extends Devana.ai and uses a dedicated ODIN v2 instance. For SharePoint: a read-only service account, with Kerberos, NTLM or Basic. For permission filtering: the Full Read policy for that account, LDAPS access to Active Directory and an identity provider.