Configuration Guide

Minute Mesh

---

MinuteView MESH – Unified Search & Insight Engine

User Guide

---

1. What Is MESH? — High-Level Overview

MESH is the information “nervous system” of MinuteView. It breaks down data silos by crawling, indexing, and unifying content from platforms such as SharePoint, Monday.com, Zendesk, Autodesk Construction Cloud, and any future system that exposes an API. Key capabilities:

Capability	What it means for you
One-stop search	A single query box returns ranked results from every connected repository.
AI & vector intelligence	Classic keyword search is fused with vector similarity, sentiment, and natural-language Q&A.
Security-first	Source-level and item-level ACLs are honoured automatically; all activity is audit-logged.
Low-code extensibility	New connectors or relevance tweaks can be added without touching core systems.

In short, MESH turns “where data lives” into “where answers live.”

---

2. Core Building Blocks

Term	Purpose
Data Source	A definition of where content lives (e.g., a SharePoint site or Zendesk instance) and who may query it.
Service Account	A credential bundle (client ID/secret, PAT, certificate, etc.) stored in the Console that the crawler uses to read the repository.
Indexer Node	The automation task that performs the crawl, extraction, and vectorisation.
Automation	A low-code workflow that schedules and orchestrates Indexer nodes + any follow-up tasks (notifications, QA checks, etc.).

---

3. Before You Begin – Prerequisites

Requirement	Why it matters
MinuteView Administrator role	Only admins see the Console menu.
Security model (roles/groups)	You will assign these to each Data Source.
Repository-specific credentials	Needed to create Service Accounts (e.g., Azure app for SharePoint, API key for OpenAI embeddings).

---

4. Step-by-Step Guide

4.1 Create a Data Source

1. Open Console → MESH Connectors.
2. Click ➕ New Data Source.
3. Choose a Connector Type (SharePoint, Monday.com, etc.).
4. Enter a display name (e.g., SP_ProjectDocs).
5. Permissions tab → add MinuteView roles/groups that may search this data.
6. (Optional) Toggle Inherit source ACLs to mirror item-level security from the origin system.
7. Save.

Tip: Use a naming convention such as SP_, ACC_, ZD_ to keep the list tidy.

---

4.2 Create Service Accounts

1. Console → Service Accounts → ➕ New.
2. Pick the same Connector Type as your Data Source.
3. Fill in credential fields (client secret, PAT, certificate ID, etc.).
4. Test Connection → Save.
5. Back in MESH Connectors, open the Data Source and choose your new Service Account in the Authentication drop-down.
6. Activate the Data Source.

Setup order recap: 1️⃣ Data Source → 2️⃣ Service Account → 3️⃣ Bind & Activate

---

4.3 Build an Automation with an Indexer Node

1. Open Automations (MinuteView’s low-code canvas).
2. Add Trigger – choose a schedule (e.g., nightly RRULE:FREQ=DAILY;BYHOUR=2), a webhook, or a manual “Run Now”.
3. Drag in Indexer Node and connect it to the trigger.
4. Configure the node:

Indexer Controls ( authoritative list )

Group	Control	Description
Common—apply to every connector
Include Text Vectorization	Calls your AI Service to generate embeddings, enabling semantic search.
Include Full Text Content	Extracts the full body of supported formats (DWG, DGN, IDW, PDF, DOC(X), XLS(X), PPT(X), MSG).
Include Thumbnail	Pulls a preview image if the source can supply one.
Include OCR	Runs OCR on image-based docs (PNG, PDF, TIF/F, JPEG).
Select Index	Choose which Data Source to crawl.
Record Title	Display title in MESH; supports concatenation.
Sub Title	Secondary line in result cards; also supports placeholders.
Index Action	Full Index | Update From Date | Update Single Record.
Data-source-specific (only show if the connector exposes them)
White List Folders	Crawl only these paths.
Lifecycle States	Filter Vault/PLM items by state.
Board ID (Monday.com)	Limit crawl to a board.
…etc.	Other connector-specific filters.

5. (Optional) Add follow-up tasks:

   • Notification node – Teams/Email “Index complete”.
   • Conditional branch – e.g., if newItems > 100 then trigger QA review.

6. Save and Enable the automation (or Run Now for a seed crawl).

---

4.4 Validate the Index

1. Wait for the Indexer node to reach Completed status.
2. Open MESH Search → set Source Filter to your new connector.
3. Test a keyword query and a natural-language question (if vectorisation is on).
4. Verify thumbnails, previews, and field concatenations.

Troubleshooting checklist

Symptom	Check
No results	Does your MinuteView role have permission?
“Authentication failed”	Verify Service Account credentials.
Outdated items only	Is the automation schedule running? Index Action = Update From Date correct?
OCR text missing	Ensure Include OCR is enabled and the file type is supported.

---

5. Operating & Scaling

5.1 Tune Freshness

• High-churn libraries → Hourly triggers.
• Archive stores → Weekly or Monthly.

5.2 Parallelism

Large SharePoint sites? Create multiple Indexer nodes scoped to sub-folders and run them in parallel to reduce throttling.

5.3 Post-Processing Ideas

• Sentiment analysis on new tickets.
• Auto-classify docs by project code.
• Notify a Teams channel when critical files are added.

---

6. Security & Governance Best Practices

• Dedicated, least-privilege Service Accounts – never index with a human login.
• Secret rotation – observe expiry policies; MinuteView warns ahead of time.
• Audit trail – Console → Audit logs every credential edit and automation run.
• Deactivation – toggle a Service Account Inactive to pause crawling without losing indexed data.

---

7. Quick Reference – “Recipe” to Go Live

1. Create Data Source in Console → MESH Connectors.
2. Create Service Account(s) and bind them to the Data Source.
3. Build Automation with an Indexer node; set controls as needed.
4. Run the workflow → Validate in MESH search.
5. Iterate & scale schedules, scopes, and post-processing tasks.

Follow this sequence and your organisation’s content—files, tickets, drawings, emails—becomes instantly discoverable through one AI-powered search bar in MinuteView.