Ask us anything! - Product x Business - 26.06.2025

Created by Mohamed DT - MAHMOUD, Modified on Mon, 30 Jun, 2025 at 11:35 AM by Mohamed DT - MAHMOUD

1. ? Add-In Access Across Different CLM Servers

  • Issue: Add-in fails to connect when switching from EU servers to Moroccan production.

  • Clarification: Add-in is not geographically zoned and should function regardless of the tenant location.

  • Resolution Path: Mohamed to investigate internally and loop in Customer Care and Support teams for troubleshooting.


2. ? Document Storage for Multiple Entities

  • Concern Raised by: Gabriel Altiparmak

  • Use Case: Avoid duplication of documents across entities; improve search functionality using historic entity names.

  • Response (Aurelien):

    • Entity folders can be reused, but only one per entity.

    • No native support to relate a document to multiple entities.

    • Workaround: Use custom document fields to associate across entities.

    • Historic search functionality exists but may need bug validation.


3. ? Migration to Entities Platform

  • Status: No known migrations completed yet.

  • Next Steps: Follow up with Adnan or Gregoire for updates on potential or ongoing migration.


4. ? IP Restrictions by Country

  • Request from Clients: Restrict platform access by country instead of IP range.

  • Discussion:

    • Current solution supports IP restriction.

    • Country-based restrictions are not natively supported; typically handled via VPNs and company-side configurations.

    • Encouraged clients to manage access through internal IT policies.


5. ? Documentation Support in Matter Management

  • Request: Ability to manage and view documents in the same way as in Entities.

  • Response:

    • Storage supported, but no viewer currently integrated.

    • Viewer feature is planned but not prioritized for 2025.

    • Feedback encouraged if it's a deal blocker to adjust roadmap priorities.


6. ? Shared Documents Across Multiple Matters

  • Discussion: Interest in reusing documents across multiple matters.

  • Current Limitation: Each document upload is tied to a single matter; no shared reference mechanism exists.

  • Future Outlook: Related Matters feature may provide a framework for smarter document associations (targeted for Q4).


7. ?️ DiliSign Feature Status

  • Raised by: Marin Guillaume

  • Concern: Missing from current roadmap despite being a key sales point.

  • Response (Ludwig):

    • Postponed from Q2 to Q3 due to technical delays.

    • Target release: October 2025.

    • Marin to follow up directly as feature is a requirement in ongoing deals.


8. ? Feature Request Process

  • Clarified By: Ludwig

  • Action: Sales team members should email or use Teams to submit feature requests for internal ticket creation.


9. ? Integration with Oracle & SharePoint

  • Oracle Integration:

    • Via API & Webhooks – document validation statuses can be pushed/pulled to ERP systems.

    • Webhook setup allows notification of stage changes for contracts.

  • SharePoint Integration:

    • Bidirectional API support exists.

    • No webhook support on Entities module—batch processes recommended.

    • Use case discussion emphasized understanding the real client needs (e.g., user access policies, backup, metadata-only access).


10. ? AI & Roadmap Updates

  • AI Enhancements: Plans to introduce natural language querying for legal data (e.g., mandate holders, company address).

  • Sanofi Upgrade: Migrating to the new Entities module; sales contact is David Kraemer.

  • Q3 Roadmap: Updates to be shared mid-July; long-term vision document being validated for broader sales use.


11. ☕ Closing Remarks

  • Next Steps:

    • Q3 Roadmap finalization underway.

    • Long-term roadmap document under review.

    • Meeting concluded with encouragement for coffee and informal follow-ups.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article