Data Sources

Data sources are the places where Nairo gets the materials used for review work.

In the current product, data sources are primarily document-based. Teams upload documents into the Library, into Projects, or directly into supported product surfaces such as Experts and Actions.

Nairo does not currently provide a self-serve admin connector platform for external systems.

What exists today

Library as the document repository layer

The Library is Nairo’s document repository layer.

It is where uploaded documents are stored, organised, processed and made available to supported product surfaces.

Library materials may include:

Underwriting guidelines
Appetite materials
Policy wordings
Claims handling guidance
Internal reference documents
Templates
Spreadsheets
Project document folders
Other uploaded materials used in review work

Library materials can be used across supported surfaces, including Assistant, Experts, Actions, Insight Table and Projects.

The exact experience depends on the workspace configuration and the product surface being used.

Project materials

Projects are focused document workspaces.

Users upload documents into a Project when they want to review a specific document set with the Assistant and other configured Project capabilities.

When documents are uploaded to a Project, Nairo creates or uses a corresponding Library folder for that Project’s materials. This keeps Project documents part of the workspace document repository while allowing users to work from the Project interface.

In practice:

Use Projects to work on a specific document pack or review
Use Library to store, browse, organise and reuse uploaded materials
Use the Project’s associated Library folder to keep Project materials available in the workspace document layer

Context in Assistant conversations

When starting an Assistant conversation, users can select supported context such as Library folders or specific documents.

Internet search may also be available where enabled for the workspace.

Context is set when the conversation is created. If a different document set is required, users should start a new conversation with the right context.

Experts and selected materials

Experts can use selected Library folders or documents as reference materials.

Users may also upload materials for an Expert session where supported.

This helps teams create specialist assistants that work with relevant uploaded materials, instructions and review guidance.

Actions and input materials

Actions can use uploaded inputs, Library materials or both, depending on how the Action is configured.

This allows teams to run repeatable tasks using documents already stored in the Library, or to provide specific files and text at run time.

Examples include:

Running a comparison using selected Library documents
Uploading files as inputs for a specific Action run
Producing a memo, table, checklist or draft communication from selected materials

Action outputs should be reviewed before they are used in business workflows.

Insight Table document sets

Insight Table uses document sets for structured review across multiple documents.

Teams add documents to a table and define columns that ask the same question across those documents.

Insight Table is useful for extraction, comparison and batch review.

What is not available as self-serve today

Nairo does not currently provide a self-serve Data Sources admin area for connecting external systems.

This means there is no general admin UI today for:

Connecting third-party systems
Scheduling automated ingestion
Monitoring external sync jobs
Managing connector credentials
Mapping external repositories into Nairo automatically

External integrations require separate implementation work.

Until an integration is available, teams should use upload-based workflows through Library, Projects, Experts, Actions or Insight Table.

Considerations for administrators

When preparing data sources for a pilot, administrators should define which documents are required and where they should live.

Useful questions include:

Which documents are authoritative for the pilot?
Are the uploaded versions current and approved?
Should the materials be uploaded to Library, Projects, Actions, Experts or Insight Table?
Which Project folders will be created for case-specific document packs?
Who should have access to each folder or document set?
Has document processing completed successfully?
Which materials should be selected as context for Assistant, Experts, Actions or Insight Table?

For most pilots, it is better to start with a small, well-organised set of high-quality materials than to upload a large uncurated repository.

Document governance

Uploading a document to Nairo does not automatically make it authoritative.

Customer teams remain responsible for deciding:

Which documents are current
Which versions should be used
Which users should have access
Which materials can be used for business-critical review
Which outputs should be retained in the customer’s own process

Nairo helps teams work with uploaded materials. It does not replace the customer’s document governance process.

What data sources are not

Data Sources are not a live connector platform in the current release.

Nairo does not automatically sync with external systems unless a specific integration has been implemented.

Nairo does not decide which documents are authoritative.

Nairo does not replace the customer’s own records management, retention or approval process.

Library - document repository and folder management
Projects - focused document workspaces
Assistant - conversations over selected context
Experts - specialist assistants using selected materials
Actions - repeatable tasks using uploaded inputs or Library materials
Insight Table - structured review across document sets
Data Handling - how uploaded data is processed

Getting started

Start by listing the documents required for your first workflow.

Upload shared reference materials to the Library, create Projects for focused document packs, and use Library or uploaded inputs for Experts and Actions where relevant.

Confirm that documents finish processing successfully before users rely on them in review work.