At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Consumer team or project space | Select Space that will use shared terms | Target for one sharing rule | Personal spaces are hidden from this UI |
| Source team or project spaces | Select Spaces to read approved terms from | Direct source-space list | Maximum 50 sources; self, duplicates, and ALL are removed |
| Saved sharing rule | Resolve global, consumer, and direct source keys | Effective glossary scope | Source subscriptions are not expanded transitively |
| Page space context | Load the Compliance Glossary or Glossary term macro | Approved terms visible to that space | Missing context returns no terms; corrupt configuration is surfaced |
How it works
- Open Settings.
- Find Shared Glossary Across Spaces (Advanced).
- Under Space that will use shared terms, select the consumer space.
- Under Spaces to read approved terms from, select each source space.
- Select Save Sharing Rules.
- Add or reload the Compliance Glossary macro in the consumer space.
- Confirm that only approved, in-scope terms appear.
Example
Legal owns approved definitions in the Legal space. Product selects Legal as a source. Product pages can display those approved meanings through the Compliance Glossary macro. Product scans also treat the subscribed terms as part of the effective glossary. Legal still owns the source records.
What this does not mean
A sharing rule changes live glossary scope. It does not copy records, transfer ownership, freeze a definition, or create a baseline. The relationship is direct. If Product reads Legal and Legal reads Risk, Product does not inherit Risk through Legal. Global terms remain available without a source subscription.
Related questions
Next step
Add a sharing rule only when one space is the accountable source for another.
View on Atlassian Marketplace