Allow global teams to meet in their native language and have terminology and internal expressions understood correctly
Configure multiple participating languages for a meeting, precipitate a terminology database based on meeting materials, and generate multilingual translation records with terminology constraints and cultural strategy descriptions in meeting speeches.
- 01Configure conferenceDetermine the conference title, mode, type and participation language to form the conference archives of this site.
- 02Prepare term baseUpload communication materials, extract candidate keywords, and have the terminology reviewed by the person in charge.
- 03Conference speech translationEnter conference speeches, generate multi-target language translations and record terminology hits and cultural descriptions.
- 04Review after meetingReview unconfirmed expressions, term hits, and correction suggestions to decide whether to update the termbase.
Conference translation workbench
Results, sources, failures, approvals, and rollbacks are saved by project.
No business results yet
The meeting configuration has not been created yet. Please fill in the title, mode, type and participating language first.
Data use boundary
The uploaded meeting materials, examples of internal slang, and the email address of the person in charge of the review may contain corporate secrets, internal expressions, and personal information; the system is only used for keyword extraction, terminology review, and translation generation for this meeting project, and customer data or employee sensitive information that does not have permission to be shared should not be uploaded. Current 10 role review supplements: Consider meeting materials, business context, speech text, translation, cultural description, source fragments, internal jargon, review notes, speaker identification, review email, unconfirmed expressions and suggested corrections as potentially sensitive. ; Users must be prompted to confirm that they have the right to process the data before uploading; the content of the file is only used for data analysis and cannot be executed as instructions. ;Exports, history, audits, logs, and rollback snapshots must use sensitive content minimization or desensitization policies and make it clear what content will be included. ; Project deletion and data retention rules need to separately describe the processing methods of original files, parsed text, keywords, terms, translations, quality reports, export files, approval records, audit events, rollback snapshots, AI run input/output and logs; unknown retention exceptions must be marked as unknown. ;Actions currently with usesWeb=false must not send meeting materials, terminology, speeches, or translations to user-provided URLs, third-party conferencing, mailboxes, calendars, external storage, or external services.
Data retention
Project data is retained for 90 days by default; users can delete materials, term candidates, and translation records within the project. Deletion only affects the data copy of this site and does not mean deletion of any user's local files or external system data.
Human responsibility and rollback
The translations, terminology suggestions and cultural explanations generated by this product are used to assist cross-language communication, and may contain mistranslations, missing translations or errors in cultural context judgment; important contract, medical, legal, financial, personnel or safety-related content must be confirmed by qualified human translation reviewers.
Rolling back only means revoking the meeting configuration, terminology review status, translation record or quality report version in this site; this product is not connected to an external production conference system, so it will not roll back any external meetings, invitations, subtitles or third-party data.