Feature

Notifications

Signal the right people when terminology, sources, assignments, approvals, or risks change.

Notification panels in a translation operations workspace

Awareness without noise.

Translation work changes constantly: a source document is updated, a glossary term is approved, a reviewer asks for clarification, or a domain expert rejects a proposed equivalent.

Idanium notifications are meant to be selective. They should route attention by ownership, urgency, language pair, domain, and whether the change affects live work.

Role-aware alerts

Notify translators, reviewers, domain experts, or administrators only when their attention is useful.

Project signals

Surface approvals, blockers, deadline risk, and glossary changes as they happen.

Source-driven updates

Alert teams when a referenced regulation, policy, guideline, or source document changes.

Digest options

Group lower-priority changes into daily or weekly summaries for less urgent monitoring.

What this adds

Notifications separate urgent work from background change.

A mature language operation needs both interruption and calm. Some changes need immediate review; others need traceability and scheduled attention.

01

Immediate

Safety-sensitive terms, legal changes, blocked reviews, and publication risks can trigger direct alerts.

02

Scheduled

Glossary updates, new candidate terms, and low-risk source changes can be summarized for review sessions.

03

Auditable

Notification history shows who was informed, when the signal was created, and how the issue was resolved.

Connected records

Signals come from real objects in the workspace.

Notifications are strongest when they are linked to the record that changed, not written as generic reminders.

Terms

A preferred term is approved, deprecated, challenged, or restricted to a specific context.

Documents

A source file, public notice, guideline, or translated output changes state.

People

A reviewer is assigned, an expert is requested, or an owner is needed for a decision.

Risks

A protected term appears without approval or a memory match conflicts with current rules.