Mesh Sources

Mesh Sources define what data Mesh can search. Each source points to a system or location (e.g., Autodesk Vault, ACC, Network Drives, SharePoint, Monday.com, etc.). You must create a source before any data from that system can appear in Mesh.

Important: Creating a Mesh Source does not index data by itself. Indexing is performed via the Automations Engine. Link or trigger an automation to pull content into the source you create here.

---

Workflow Overview

1. Create a Mesh Source in the Console.
2. Configure permissions on that source (roles and/or users).
3. Use Automations to index/push data from the external system into that source.
4. Users with permission can now search that data inside Mesh.

---

Creating a New Source

1. Go to Console → Mesh Sources.

2. Click New.

3. Enter a Source Name (descriptive of content or security boundary).

4. Select a Source Type from the available list (e.g., Autodesk Vault, ACC, Network Drive, SharePoint, Monday.com, …).

5. Set Permissions:

   • Role-based: Pick one or more roles. Only members of those roles will see/search this source.
   • User-specific: Limit to individual users instead of (or in addition to) roles.
   • Open (no selection): Leave empty and everyone can see the source.

6. Click Save.

---

Multiple Sources from the Same System

You can create several sources pointing to the same platform but with different scopes and permissions.

Example:

• Network Drive – Projects → indexes \\Server\Projects (Role: Engineering)
• Network Drive – HR → indexes \\Server\HR (Role: HR Only)

Both are “Network Drive” types, but each has its own indexed content and access rules.

---

Indexing Data (Automations Required)

• After saving the Mesh Source, configure an Automation workflow to crawl/extract the data and push it into Mesh under that source.
• Re-run the automation on a schedule (or event-based) to keep the index up to date.
• Without this step, the source will remain empty.

See Automations Module documentation for how to build and schedule these indexing jobs.

---

Permissions Model

• Permissions are evaluated at the source level first—if a user can’t see the source, they can’t see any of its documents.
• Additional document-level permissions (e.g., inherited from Vault/ACC) can also apply, depending on how your automation populates ACL data.

---

Best Practices

• Name by Purpose & Audience: Make it obvious what’s inside and who should see it.
• Segment by Security Boundary: Separate confidential sets (HR, Legal, Executive) into distinct sources.
• Automate Refreshes: Schedule re-index jobs to keep Mesh current.
• Audit Regularly: Review who has access to each source and adjust roles as teams change.

---

See Also

• Automations Engine – Required for indexing data into Mesh.
• Search Connection (Global Settings) – Configure Elasticsearch & AI service accounts.
• User Management / Roles – Control who can see each source.