Help! Add-on in Multi Tenanted Env concerns (Glossary - Terminology Manager)

Hey WKnowledge Team,

We have recently tested and trialled the latest version of your Confluence add-on ‘Glossary - Terminology Manager’ for Data Center

We have a fantastic use case for it, and it’s a great add-on, however with our enterprise level multi tenanted environment we have some concerns.

Background Info:
We have around 10’000 users in our Confluence Instance

We’ve drafted a list of things highlighted as a concern / bug, If you could help us understand if some the issues we’ve encountered are by design, or if any have to potential to be included on your roadmap in future?

The ‘Reviewers' feature doesn’t work for us at an enterprise level

A user group can be set as a ‘Reviewer’ of a term created for a specific ‘Domain’ (E.g. Software)
- ‘Domains’ - Similar to ‘Resolution’ in Jira, this is a global field, meaning the options/values will be seen by anyone creating a term, therefore having just one group defined as a 'Reviewer' for ‘Software’ terms would not work for us
  - Ideally we would need ‘Domains’ at a space level, not global level. This would enable us to set user groups as ’Reviewers’ for domains in specific Space, not globally

2. Approvals of a term are not currently trackable

It seems having a 'Reviewer' group defined simply enables the reviewer to change the term status from ‘Proposes’ to ‘Approved’ by clicking the edit icon
- Ideally we would like a history of the approval recorded (Name, Date etc)

3. Bug with the creation of a term via highlighting function

When creating a new term by highlighting a word in an existing page, the new term page is created under the existing page within the tree, not under the dedicated ‘Terms’ page.
- Ideally we would need it to default always under the ’Terms’ page

4. Security Issue with the ‘Term Owner’ field (user picker). Testing confirms

All users are currently searchable to select from, regardless of space permissions
- We appreciate this field can be disabled in the admin config, but ideally we would need this field to follow the Space permissions - only enabling a user to select another user who is within the same space

5. Term Security / Restrictions

The 'Highlight Term' button (next the in the 'restriction' lock symbol in page) function scans the page for all terms in the instance, regardless of permissions, even highlighting ones which users don't have permissions to view the definitions for
- If the user does not have permissions to view the term a message will appear: "The term exists, but you do not have permission to view it. Please, contact your Confluence administrator."
  - This could be confusing for our users, and could result to a user raising a support request for permission
    - Ideally if a user does not have access to the definition of a term, we would need the term not to be highlighted at all

6. Space Level Restrictions

Here’s a list of functions we would like to see at space level:

‘Auto Highlighting’
‘Exclude term from highlighting’
‘Domain’ permissions - (as mentioned in no. 1 above)
The ability to hide the module completely from certain space (or, only allow on some spaces)

‌

Thank you,

Seon
Platform Architect
Uhub

Comments (4)