Translations for custom metadata fields

Problem

For accounts operating in multiple languages, custom metadata fields are currently limited to a single language. This creates friction for international teams, as field names and values may not be understandable or consistent across regions. It can also lead to duplicated fields or workarounds when managing multilingual contract repositories.

Solution

Introduce translation capabilities for custom metadata fields, allowing field names (and potentially predefined values) to be displayed in different languages depending on the user’s language settings.

Benefits

• 🌎 Better usability for international teams

• 🏢 Cleaner global contract management across regions

• 🧾 Reduced duplication of metadata fields

• 🤝 Improved collaboration in multilingual environments