Documentation

Parlance for Confluence

Parlance is a company glossary for Confluence. Its point is not the list: it is that the list reaches the reader on the page they are already reading, without anyone installing anything.

Install

Install Parlance from the Atlassian Marketplace, as a Confluence site administrator. Nothing else is needed: no server, no account, no browser extension. The app appears under Apps in the Confluence navigation, as Glossary.

Build the glossary

Add terms one by one

Open Apps → Glossary and choose Add a term. A term has:

TermThe canonical name, the one shown to readers.
DefinitionOne or two sentences. What the thing is and what it is for.
Synonyms and acronymsComma separated. Parlance recognises these in pages too, and tells the reader which form it read.
Reference pageOptional. A full link, or a Confluence path starting with /.
ScopeAll spaces, or one space. A scoped term only appears on that space's pages.

If a term with that name already exists, Parlance says so while you type and tells you that saving will update it rather than create a second one. Its previous version stays in its history.

Load an existing list

In Settings → Load terms, paste a CSV with five columns: term, definition, synonyms, link, space. The last three are optional. A header row is recognised and skipped.

Check before applying writes nothing. It reports what it will do, names every line it refuses and why, warns about a wrong separator or an unclosed quote, and lists the ambiguities the result would contain. Only Apply the import writes.

Export the glossary gives the same format back, for an archive or a round trip through a spreadsheet.

Put the glossary in front of readers

Three surfaces, none of which asks the reader to install anything.

The panel under the page title

Automatic, on every page. It shows how many glossary terms appear on that page, each with its definition and the form that was actually read, for example read here: POs. A reader who met an acronym learns which term it belongs to.

Glossary of this page

A macro you place in the page body. It lists the same terms as page content, so it prints and follows a PDF or Word export.

Highlight glossary terms

A block you wrap around a section. Its glossary terms are marked as the page loads, and their definitions are listed underneath. Type /Highlight in the editor, then write or paste your text inside the block.

Glossary term

An inline macro for a single term, with its definition on hover. Type /Glossary term and pick the term.

How matching works

Drafting a definition

In the term form, Draft a definition searches your own pages for the term and writes a draft from what it finds, naming the pages it used. When no page mentions the term, it says so and marks the draft as generic.

The model runs on Atlassian's own infrastructure, through the Forge LLMs API. The request never leaves Atlassian, and Coreyard never receives, stores or trains on it. The draft always runs as the signed-in user, so it can only read pages that person could open themselves.

Who can edit

In Settings → Who can edit, the glossary is open to everyone by default. You can restrict editing to a Confluence group. Either way every change stays attributed and reversible: opening it up does not cost you the audit trail.

History, trash, and deleting for good

Every term keeps a history. It shows what changed, field by field, and restores any version in one click. A deleted term goes to Deleted terms in Settings, survives a reload, and can be restored with its definition and synonyms intact.

A glossary owner can empty the trash, which erases the deleted terms and their history for good. Use it when a deletion has to be final.

Language

The interface follows each reader's own Confluence language, in English and French. Your glossary stays in whatever language you write it, and a drafted definition follows the language of your pages, not the language of the interface.

Limits

Getting help

Use the Support panel in Settings, or write to parlance@bycoreyard.com. Response times are on our support page.