But what happens when different teams use different terms for the same thing? Or when an acronym means something completely different depending on who’s reading it?

For Knowledge Managers, the challenge isn’t just making information accessible. It’s making sure employees understand the terminology behind it and use it consistently.

A knowledge base helps teams document what they know. A shared company glossary helps everyone speak the same language.

Why your company knowledge base needs a shared vocabulary

Knowledge management is about more than documenting information. It also means making that information understandable and reusable across an organization.

Imagine three teams working on the same project:

• The Product team refers to a feature as a release candidate.
• The Engineering team uses RC in technical documentation.
• The Support team sees RC in an internal troubleshooting guide without knowing what it means.

Everyone has access to the documentation, but not everyone understands the terminology in the same way.

The problem becomes more complicated when organizations grow, new employees join, and different departments develop their own abbreviations, acronyms, and technical language.

This creates several challenges:

• Employees spend time searching for definitions.
• The same concept appears under different names.
• New hires struggle to understand internal documentation.
• Teams interpret unfamiliar terminology differently.
• Documentation writers repeatedly explain the same terms.

A shared company glossary helps address these challenges by providing a consistent reference for organizational terminology.

Rather than explaining the same concept across multiple pages, teams can maintain a definition that employees can access whenever they encounter the term.

Step 1: Identify the terminology your teams use every day

Before building a glossary, start by identifying the terms that appear regularly in your existing documentation.

You don’t need to define every word. Focus on terminology that is specific to your organization, frequently misunderstood, or important for cross-team communication.

For example:

Start with the Confluence spaces your employees use most often, such as product documentation, engineering, operations, or HR.

You can identify terms manually by reviewing frequently accessed pages and collecting team feedback.

Alternatively, Smart Terms includes Lexi, an AI Glossary Assistant, which can scan existing Confluence content, identify relevant terminology and acronyms, and draft definitions for review.

This gives Knowledge Managers a starting point without having to review every page manually.

Step 2: Organize your terminology into a company glossary

Once you’ve identified your terms, decide how to organize them.

Not all terminology needs to be available to everyone. Some definitions may apply company-wide, while others are relevant only to a particular team or department.

For example, your organization might need:

With Smart Terms for Confluence, you can create and manage glossaries within Confluence spaces.

Terms can remain associated with a specific space or be made available more broadly through global glossary settings.

For instance, Engineering may maintain technical terminology within its own glossary, while company-wide terms are shared across other spaces.

This gives Knowledge Managers flexibility to organize terminology around their teams while making important definitions accessible across the organization.

Step 3: Define terms and connect related vocabulary

Creating a glossary isn’t just about listing terms alphabetically. The definitions should explain the meaning clearly and reflect how your organization uses each concept.

Consider the term Service Level Agreement.

A simple glossary entry could contain:

Term: Service Level Agreement

Acronym: SLA

Definition: An agreement that defines the expected level of service between a provider and a customer, including specific performance commitments.

Related vocabulary: Service Level Objective (SLO), Service Level Indicator (SLI).

This gives employees the definition and helps them recognize related concepts.

Smart Terms lets you enrich glossary entries with definitions, images, videos, PDFs, and related vocabulary such as acronyms, synonyms, antonyms, and plurals.

You can also create relationships between terms to help employees explore connected concepts.

For example, if your organization uses RC as an acronym for Release Candidate, you can associate both expressions with the same glossary entry rather than creating unrelated definitions.

Knowledge Managers can also use Lexi to generate draft definitions and review or edit them before adding them to the glossary.

The objective is to make your glossary a reliable source of terminology rather than another collection of disconnected information.

Step 4: Make definitions accessible directly in Confluence pages

Having a company glossary is useful. But expecting employees to open it every time they encounter an unfamiliar term creates another step in their workflow.

Consider a new employee reading a Confluence page about an internal release process.

They encounter terms such as Feature Flag, Release Candidate, and Deployment Pipeline.

Without contextual definitions, they might interrupt their reading, search for each term, or ask a colleague for clarification.

With Smart Terms’ automatic highlighting, recognized glossary terms can be highlighted directly in Confluence content.

When readers hover over or click on a highlighted term, they can access its definition without leaving the page.

Smart Terms can also recognize related vocabulary, such as configured acronyms and synonyms, so employees can access the relevant definition even when the documentation uses a different expression.

Knowledge Managers can customize the highlighting experience by controlling which terms are highlighted, where highlighting is applied, and how frequently highlights appear.

For example:

• Highlight company-wide terminology across relevant Confluence spaces.
• Keep department-specific terminology within designated spaces.
• Display only the first occurrence of a term to reduce visual clutter.
• Exclude selected content areas or adjust highlighting behavior through configuration.

The result is documentation that provides explanations in context without requiring writers to repeat definitions across every page.

New: Highlight glossary terms in the Confluence editor

With the latest Smart Terms release, glossary terms are now highlighted directly in the Confluence page editor and Live Docs.

Content creators can recognize existing glossary terms while writing, helping teams maintain consistent terminology from the first draft to the published page.

Step 5: Extend shared terminology across teams and Jira

Company terminology rarely stays within a single Confluence space.

The same acronyms and technical concepts can appear in project documentation, Jira work items, support workflows, and internal discussions.

For example, an Engineering team might document a technical process in Confluence and then reference it in a Jira work item.

If a Product Manager or Support colleague is unfamiliar with the terminology, they may still need to look up its meaning.

Smart Terms supports glossary term highlighting across Confluence and Jira, using the glossary managed in Confluence as the source of definitions.

Once the Jira connection and required browser extension are configured, supported Jira content can display highlighted terms and their definitions.

This helps teams use the same terminology across documentation and work items.

The connection is particularly useful for organizations where several departments collaborate on technical projects but have different levels of familiarity with the terminology involved.

For example:

• Engineering defines technical concepts in Confluence.
• Product teams reference those concepts in Jira work items.
• Support teams consult definitions when reviewing related requests.
• New employees use contextual definitions to understand unfamiliar language.

Instead of maintaining separate terminology lists for each workflow, teams can rely on shared glossary definitions.

Step 6: Keep your company glossary consistent and up to date

A glossary is only useful when employees trust its definitions.

As products evolve, processes change, and new terminology emerges, your company vocabulary needs to evolve with them.

For Knowledge Managers, the objective is to maintain consistent definitions while making it easy for the right people to contribute.

A practical terminology management process could include:

1. Identify new terms: Review updated documentation and collect employee suggestions.
2. Review definitions: Confirm that new terms and explanations reflect the organization’s preferred terminology.
3. Maintain glossary organization: Keep company-wide and department-specific terminology appropriately organized.
4. Review terminology regularly: Update definitions when processes, products, or internal language change.

Smart Terms provides glossary management capabilities, including term creation, editing, sorting, filtering, and import/export options.

Lexi can help discover new terminology from Confluence content and draft definitions for human review.

How Atlassian’s Teamwork Collection fits into company terminology management

Shared terminology becomes more valuable when it’s connected to the tools employees already use.

Atlassian’s Teamwork Collection brings together Confluence, Jira, Loom, and Rovo to help teams connect knowledge, communication, and everyday work.

Each plays a different role:

• Confluence: Organize and maintain company documentation, policies, and knowledge.
• Jira: Manage work items where teams frequently reference project and technical terminology.
• Loom: Record explanations and walkthroughs that help employees understand processes and concepts.
• Rovo: Help teams find relevant knowledge and access AI-assisted capabilities.

Smart Terms adds a terminology management layer to this environment.

Confluence becomes the place where glossary definitions are managed, while Smart Terms makes that vocabulary accessible through highlighted terms in supported Confluence and Jira content.

Lexi also works with Atlassian Rovo to help identify terminology and generate glossary drafts from existing knowledge.

It’s important to distinguish their roles: Loom and Jira do not automatically manage company terminology, and Rovo isn’t a replacement for a maintained glossary. Smart Terms complements these capabilities by connecting documented terminology with the content employees read.

From documented knowledge to a shared company language

Your organization may already have thousands of pages of valuable information in Confluence.

But having information in one place doesn’t automatically mean everyone understands it in the same way.

A company glossary helps connect the knowledge you’ve documented with the vocabulary employees need to understand it.

Start with the terminology used most often across your teams. Define important concepts, organize them into glossaries, and make their meanings accessible where employees work.

Then, as your organization grows, expand the glossary to support new teams, products, processes, and languages.

You don’t need to rewrite every page to make company terminology easier to understand. Instead, establish a consistent way to define and share the language behind your knowledge base.

With Smart Terms for Confluence and Jira, you can create a shared glossary, connect related vocabulary, highlight definitions in context, and use Lexi to help manage terminology as your knowledge base evolves.

Try Smart Terms on the Atlassian Marketplace or book a demo.

With features like Atlassian AI definitions powered by ROVO, employees can select an unfamiliar term, ask for an explanation, and get an answer instantly. Some acronyms are even defined and highlighted automatically, so you don’t always have to look it up. It is fast, convenient, and often surprisingly accurate.

So if AI can explain terms on demand, do organizations still need a glossary?

The short answer is yes.

Because explaining a term and managing organizational terminology are two completely different challenges.

AI helps people understand information in the moment. A glossary ensures everyone across the organization is working with the same definition, the same language, and the same source of truth.

The most effective knowledge management strategy is not choosing between AI and a glossary. It is understanding where each one delivers value.

Where do AI definitions shine?

Imagine a new employee reading a technical document for the first time.

They encounter a term they have never seen before. Instead of opening another tab, searching through documentation, or messaging a colleague, they can simply define that word from a Confluence page using Atlassian AI definitions.

This is where this feature excels.

AI-generated definitions are contextual. They can analyze surrounding content, interpret intent, and provide explanations tailored to the situation. They require little maintenance and can scale across large amounts of information automatically.

For quick clarification, AI is often the fastest solution.

When the question is: “What does this mean right now?” AI is usually the right answer.

Where does AI reach its limits?

The challenge begins when terminology becomes specialized, or when the same word means something different depending on who you ask.

Consider terms like:

• RAID log (Risks, Assumptions, Issues, Dependencies), a staple for any PMO, rarely explained the same way twice
• WSJF (Weighted Shortest Job First), core to SAFe prioritization, and genuinely hard to look up in plain language
• Product Owner, a title that exists natively in Jira, yet means something different on nearly every team that uses it
• CAB (Change Advisory Board), meaningless as three letters unless your org has already defined it
• DORA metrics: deployment frequency, lead time, MTTR, change failure rate, often tracked differently team to team
• RTO / RPO (Recovery Time Objective / Recovery Point Objective), high-stakes compliance terms that are easy to mix up
• Definition of Done (DoD), famously interpreted differently by nearly every Agile team

These aren’t just vocabulary. They’re business-critical concepts, and in several cases, the inconsistency itself is the problem, not just the definition.

Different teams may interpret them differently. Different departments may create competing definitions. Over time, documentation becomes inconsistent, and onboarding becomes harder.

AI can explain these terms, but it cannot guarantee that every employee receives the exact same official definition every time.

AI explanations are probabilistic. They can vary depending on context and available content.
That flexibility is useful for understanding and less useful for governance.

The role of a glossary app

A glossary exists for a different reason. Instead of generating definitions dynamically, it establishes approved definitions that everyone can reference.

When someone asks:

“What is the official meaning of this term in our organization?”

A glossary becomes the authoritative source.

With Smart Terms, organizations can:

• Create and manage glossary entries
• Identify who created a term
• Control who can create and edit definitions
• Standardize terminology across teams, spaces, pages…
• Reuse definitions across multiple spaces
• Maintain a central glossary repository
• Ensure consistent definitions for every employee

AI helps people discover information.

A glossary helps organizations govern it.

A glossary is more than a definition.

One of the biggest misconceptions about glossary tools is that they simply store definitions.

Modern glossary platforms do much more.

A Smart Terms entry can include rich formatting, images, links, related terms, synonyms, acronyms, labels, multilingual definitions, and related vocabulary structures.

This transforms a simple definition into a knowledge object.

Instead of explaining a term, you are building relationships between concepts and creating a navigable knowledge network.

That is something AI-generated explanations do not inherently provide.

Why does highlighting matter more than definitions?

Definitions are only useful if people see them. This is where many AI-based approaches fall short.

Users must actively ask for a definition or trigger an AI interaction. Or, in the Atlassian AI definition case, it selects and decides which terms will be highlighted.

Smart Terms takes a different approach.

Terms are automatically highlighted throughout Confluence and Jira, making knowledge discoverable exactly where people are working. Hovering over a term immediately reveals its definition without interrupting the workflow.

More importantly, highlighting can be controlled.

Organizations can customize:

• Where terms are highlighted
• Which glossaries apply to specific spaces
• Global glossary behavior
• Term visibility
• Highlighting rules

This creates a structured knowledge layer directly inside Confluence rather than relying solely on ad hoc AI interactions.

AI and glossary management work better together.

The future is not AI versus glossary software; it is AI-enhanced glossary management.

That is exactly the direction Smart Terms is taking with Lexi, the new AI assistant for Smart Terms glossary.

Lexi helps organizations accelerate glossary creation while maintaining governance and control.

Instead of manually creating every glossary entry from scratch, teams can use AI to identify terminology, generate definitions, and build glossary content faster based on a space or page content. You can also upload a file, and Lexi will determine all the terms that should be defined.

The difference is that these definitions become managed assets rather than temporary AI responses.

Once created, terms can be edited, approved, enriched, translated, and governed like any other term created with Smart Terms.

Lexi helps create the glossary; Smart Terms advanced configuration helps manage it.

When to use Atlassian AI definitions and when to use Smart Terms Glossary?

Use Atlassian AI definitions when:

• Users need quick contextual explanations
• Information changes frequently
• You want immediate answers with minimal setup
• Understanding is more important than standardization

Use Smart Terms when:

• Definitions must be consistent across teams
• Terminology requires ownership and governance
• You need a central glossary repository
• Compliance and documentation accuracy matter
• You want rich definitions and structured relationships
• You need advanced highlighting and discoverability
• Multiple languages must be supported consistently

The strongest knowledge strategy combines both. AI helps people understand what they are reading, while a glossary ensures everyone is speaking the same language.

Final thoughts

AI has made knowledge more accessible than ever. But accessibility is not the same as consistency.

Features like AI definitions are excellent at helping employees understand unfamiliar concepts in context. They reduce friction and improve productivity.

Yet organizations still need a trusted source of truth for business terminology; that is where Smart Terms continues to deliver value, not because it competes with AI but because it provides the governance, structure, discoverability, and consistency that AI alone was never designed to provide.

And with Lexi bringing AI-powered glossary creation into Smart Terms, organizations no longer have to choose between intelligence and control.

What really sets Smart Terms Apart is its precision and customization. Instead of relying on automatic guesses or generic suggestions, every definition, highlight rule, and translation is intentional and admin-controlled. It doesn’t try to infer meaning it enforces the correct one. Smart Terms gives teams the power to define terms once and apply them consistently everywhere, with complete flexibility over how they appear, who sees them, and how they behave on Confluence pages.

From fine-grained highlight rules to space-level overrides, multilingual glossaries, logographic indexing, and rich definition pop-ups with media, Smart Terms is built for organizations that want reliability and customization, not shortcuts.

Highlighting Engine & Customization

Smart Terms’ highlight engine is highly flexible. You can fine-tune exactly how and where terms are highlighted:

• Auto-highlight or manual: Choose to automatically mark all terms when a page loads, or not. A toggle button on each page lets users turn highlights on or off (If disabled by space/global settings).

• Visual style: Pick your highlight colors and style, set the background color, text color, and underline/bold/italic style.
  You can even add custom CSS for special styling.

• Hover vs click: Control interaction by enabling “highlight on hover” or forcing users to click a word to see definitions. (We’ve seen product teams disable hover so users must click, while support teams keep hover on.)

• First vs all occurrences: Choose whether to highlight only the first occurrence of a term per page, or every occurrence. This avoids overwhelming pages with repeated highlights if desired.

• Substring & sensitivity: Turn on/off substring matching (e.g. highlight “mar” inside “Smart”). Toggle case-sensitive and diacritics-sensitive matching to prevent unintended highlights (e.g. treating “API” differently from “api” or handling accented characters).

• Content targeting: Enable or disable highlighting in specific parts of pages, headings, page titles, links, code blocks, and even blog posts can all be individually toggled.

When you hover or click a highlighted term, a definition pop-up appears with all details (term title, definition text, media, related terms, etc.). If a term has multiple definitions (e.g. an acronym vs. a full phrase), users can slide between them in the pop-up. Related terms or synonyms flash briefly to draw attention, helping users explore your custom glossary easily.

Smart Terms supports space-level and user-level rules. Admins can disable highlighting globally or for specific glossaries.

Likewise, each space can override settings: in one real-world example, an “Accounting” space simply turned off all highlighting, while a “Product” space enabled highlighting with a yellow, bold style and disabled hover. Individual users can even disable Smart Terms on their profile if they prefer. This per-space/user flexibility means you can highlight terms differently for each team without affecting others.

Multi-Language & Logographic Support

Smart Terms is built for global teams. You define terms in a default language, then add translations as needed. You can create a new term and immediately choose multiple languages, or add translations later via the term editor. Bulk import of multi-language terms from Excel is also supported for fast setup.

When highlighting, Smart Terms can mark up all translations at once or just the user’s language. For example, if your Confluence pages have content in English and German, you can highlight both English and German terms for a mixed audience.
Or you can choose “only user language” mode: a German user will see only German-term highlights, while an English user sees only English terms.
This is ideal when different groups share pages (e.g. an external audience of mixed nationalities sees all translations, or a multicultural team each sees terms in their own language).

Smart Terms even handles logographic languages (Chinese, Japanese, Korean). It applies language-specific indexing so those terms sort sensibly in glossaries.
For instance, Japanese terms are indexed by gojūon order, Chinese by character stroke count or Pinyin, and Korean by the initial Hangul consonant.
If the app misdetects a language, you can manually fix the index letters. This support means you can build a truly multi-language glossary in Confluence – even for CJK (Chinese/Japanese/Korean) text without hassle.

In addition to translations, Smart Terms supports alternate terms and meanings. Each term can have multiple definitions, synonyms, or related terms. For example, the term Item might have two meanings (“Incident” vs “Ticket” in one example) that users can toggle between.
Related terms link together as a “vocabulary,” so clicking one can flash others. You can attach images, videos, or diagrams to any term, too. In short, Smart Terms becomes your central terminology library: a terminology management for Confluence that covers all languages and complexities.

Use Cases and Benefits

Smart Terms helps teams maintain a single, unified vocabulary across the company while still allowing each department to manage its own terminology. A global glossary can hold the official definitions everyone agrees on, while teams like Product, Support, or Marketing keep space-level glossaries for internal jargon. This setup gives every group the flexibility they need without losing a shared source of truth, maintaining communication clean, and avoiding conflicting definitions.

Highlighted terms also make documentation easier to understand. When someone reads a Confluence page, they can hover over or click a term to instantly see its definition, synonyms, related terms, and even rich media. This reduces confusion during everyday reading and helps new hires settle in faster by allowing them to immediately grasp the meaning of acronyms and technical phrases without leaving the page.

Because every team works differently, Smart Terms adapts to each documentation style. Support teams can use hover highlights with a blue underline and strict case sensitivity, while Product teams prefer bold yellow highlights on click. Accounting might disable highlights entirely. This flexibility ensures each department presents terminology in a way that fits its workflow and audience, all without affecting other spaces.

Centralizing terminology also reduces redundant work. When a team updates a term, whether the meaning shifts, a new synonym is added, or an acronym needs clarification, the change is automatically applied everywhere. Teams no longer lose time re-explaining definitions or correcting misunderstandings. Everyone stays aligned with less back-and-forth, fewer errors, and far more consistency across documents.

Smart Terms also supports multilingual documentation, which is especially helpful for international teams or client-facing spaces. Terms can be translated into multiple languages and highlighted based on the reader’s preferences, or highlighted in all available languages at once. This makes joint work across regions far smoother by removing language barriers and ensuring everyone understands terminology in their own language.

In environments where documentation is central, like engineering wikis, support knowledge bases, product manuals, and onboarding guides, Smart Terms enhances how teams consume information. Readers get definitions right in the flow of the page, authors avoid cluttering documents with extra explanations, and admins maintain terminology centrally. By combining rich definitions, customizable highlighting, and multilingual support, Smart Terms turns Confluence into a clearer, more aligned workspace where terminology confusion disappears.

中国  |  日本  |  한국

“Hello” doesn’t always look like hello.
It could be こんにちは, 안녕하세요, or 你好, and if your team operates across Asia, you’re seeing all of them in your Confluence pages.

But can your Confluence Glossary keep up?

Global companies require more effective ways to manage knowledge and collaborate across languages and cultures. Confluence is already one of the most powerful platforms for organizing information, building company knowledge bases, and improving teamwork.

However, for companies operating across Asia and using logographic languages like Chinese, Japanese, and Korean (CJK), maintaining consistent terminology becomes particularly challenging.
That’s where Smart Terms for Confluence comes in. It refines glossary management, solves multilingual search challenges, and makes Confluence an even stronger tool for global businesses.
On the other hand, if inconsistent terms, buried multilingual content, and frustrating search experiences are slowing down your global teams, you need to discover how Smart Terms transforms your Confluence into a unified, searchable knowledge hub across all CJK languages.

Why do global companies choose Confluence?

Confluence is used by thousands of teams worldwide for one reason: it simplifies knowledge sharing.

With Confluence, you get:

• Centralized documentation for everything from project plans to technical guides.
• Real-time collaboration with comments, inline feedback, and document version history.
• Powerful search features to find what you need quickly.
• Global accessibility from any location or device.

It’s flexible, powerful, and customizable. However, global teams often face one persistent problem: maintaining multilingual consistency.

Confluence: the foundation for global collaboration

For multinational teams operating across East Asia, Confluence provides essential infrastructure through space management and robust integrations.

Its knowledge management core acts as a centralized repository, while collaboration tools, such as real-time editing and commenting, are available.
In addition, documentation templates maintain terminology consistency, and global accessibility ensures 24/7 availability across time zones.
But while Confluence lays a solid foundation for collaboration, one critical piece remains complex for multinational teams: managing terminology across languages.
Without a structured, multilingual glossary, even the most organized Confluence spaces can fall into confusion, especially when dealing with East Asian languages like Japanese, Korean, or Chinese.

However, without a structured glossary in Coufluence, this can cause:

• Misunderstandings between teams
• Inconsistent terminology in customer communication
• Wasted time searching for the right content

Why do multilingual glossaries matter for multinational enterprises?

Unified knowledge across borders

Companies operating in China, Japan, Korea, and beyond often face the challenge of maintaining consistent terminology across different languages and scripts. A term like “User Guide” may appear in Confluence as 用户指南 (Chinese), ユーザーガイド (Japanese), or 사용자 가이드 (Korean).

Smart Terms for Confluence ensures that these variants are centralized, searchable, and properly indexed.

Enhancing knowledge retrieval

When employees search for terms within a glossary, the indexing system matters. Poor indexing of logographic languages leads to inefficiencies, misunderstandings, and inconsistent usage. Smart Terms addresses this by introducing intelligent, language-aware indexing, which enables smoother access to information.

New feature spotlight:

Smart Terms for Confluence: logographic language indexing (Chinese, Japanese, Korean) support

Smart Terms for Confluence now includes advanced indexing:

• Simplified Chinese (简体中文): Indexed using Pinyin transliteration. Terms like “学生 (xuésheng)” are automatically sorted under “X,” while “苹果 (píngguǒ)” falls under “P.”
• Traditional Chinese (繁體中文): Organized by stroke count, allowing terms like 第一章 to be found systematically based on character structure.
• Japanese (日本語): Sorted using Gojūuon order based on Hiragana/Katakana. If a term is Kanji-only (e.g., 学生), Smart Terms defaults to Chinese rules unless Hiragana is appended in brackets, such as 学生 (がくせい).
• Korean (한국어): Indexing follows the initial consonant rule based on Hangul structure. For example, 가 (ᄀ) is filed under “ᄀ” (Giyeok), 나 (ᄂ) under “ᄂ” (Nieun).

Page definitions macro & custom indexing

In addition to multilingual indexing, Smart Terms introduces the Page Definitions macro. This feature scans a Confluence page and displays all highlightable glossary terms used within it, complete with their definitions. This provides readers with instant context, helps new team members learn company terminology more quickly, and ensures that no important definition goes unnoticed during reviews. Additionally, when exporting to a PDF file, you can view all the terms within the exported page.

For greater flexibility, Smart Terms for Confluence provides custom indexing. If automated language detection encounters mixed scripts or rare characters, users can manually assign the correct index letter to ensure every term is perfectly organized.

Glossary re-indexing: update pre-existing glossaries

Need to apply the new intelligent indexing to an existing glossary?
Smart Terms for Confluence supports bulk re-indexing. Here is how you can do this:

1. Export the existing space glossary.
2. Re-import it into the same space with “Update existing terms” enabled.
3. Preserve attached images or files by disabling “Reset existing terms media.”
   This allows legacy glossaries to be upgraded to the new, powerful indexing rules without losing valuable assets.

Use case: a global software company operating in APAC

Company: A global software company with HQ in the US, R&D in Seoul, customer support in Tokyo, and marketing in Shanghai. All teams collaborate via a centralized Confluence knowledge base in their native languages, but apparently it’s not enough!

Challenge: Inconsistent glossary terms caused confusion and slowed workflows. Japanese support agents were unable to locate key Korean or Chinese documents.

Solution: Smart Terms for Confluence:

• Shanghai Marketing: Used Pinyin-based sorting.
• Tokyo Support: Adopted Gojūuon indexing.
• Seoul R&D: Implemented Hangul consonant rules.

Result: The entire multilingual glossary became interlinked, instantly searchable across all teams, and correctly indexed for each CJK script. Confusion dropped, and finding critical information became easier.

Try Smart Terms for Confluence today and empower your global teams!