Skip to main content

    Filter by Idea status

    Filter by category

    52 Ideas

    PslimNew Voice

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

    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 mappingWhy 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.

    lkatwlnNew Voice

    Bundle Main Contracts and Appendices into One Agreement with only one set of contract detailsIdea Submitted

    The current hierarchy feature doesn’t fully address our needs. While it allows agreements to be linked (works for interlinked contracts), all documents still remain separate agreements within Agreement Manager (becomes problematic when linking appendices, e.g. important provisions, such as terms and conditions, are defined in appendices rather than the main contract).Many of our agreements consist of a main contract and multiple appendices. When each document is stored separately, appendices appear as standalone agreements with own contract details, cluttering search results and making it harder to understand the contractual relationship and the contract situation of our company.A bundling feature would allow users to designate a Primary Agreement and associate all related appendices with it. Within Agreement Manager, only the Primary Agreement should appear as the agreement record, while appendices remain accessible through the bundle.In addition, key metadata and lifecycle attributes—such as status, term dates, and renewal dates—should be managed at the Primary Agreement level and automatically inherited by all bundled documents (there’s only one set of details for all documents). This would provide a more accurate representation of the agreement and prevent appendices from being treated as separate contract, including searches, reports, and dashboards.