Agreement Manager - Use Folder-Level Path as Categorization Metadata on Bulk Upload

When bulk uploading agreements into Agreement Manager, categorization currently relies on AI content analysis after ingest, or manual assignment to agreement types/categories/sets. There's no way to leverage the folder structure of the files being uploaded (e.g., from a mapped drive or cloud storage) as a source of categorization metadata.

Many organizations already store historical agreements in a meaningful folder hierarchy, such as:

/Sales/MSAs/2026/
/Procurement/Vendor Agreements/2026/

Today, this structure is lost on upload — every file lands in Agreement Manager as an individual record, categorized only by what the AI infers from the document content, or by tags applied manually afterward.

Request: When uploading a folder (or nested folders) of agreements, allow the folder path to be captured and mapped to categorization fields, for example:

• Auto-populate or suggest an agreement type, category, department, or custom field based on the folder name(s) in the path
• Let admins define a mapping between folder structure and metadata fields before or during upload (e.g., top-level folder → Department, second-level folder → Agreement Type)
• Preserve the original folder path as a searchable attribute on the agreement record, even if the user doesn't set up a mapping

Why it matters: Migrating agreements from network drives, SharePoint, or other DMS tools into Agreement Manager means re-doing categorization work that already exists in the folder structure. Using folder-level information would speed up migration, reduce manual tagging, and give AI categorization a stronger starting signal instead of relying on content inference alone.