Admins and the small group of users with Org Settings access can create tags there.
Users who contribute content, such as SMEs and authors tagging QAs in projects, are assigned other roles. Those roles can be given the "Create tags" permission in the Projects section.
When these users tag a QA in a project, they can only search for and apply existing tags, which turn blue once applied. If they type text that doesn't match an existing tag, it's added as a grey label. Grey labels stay on that QA only and are not added to the org's tag list.
Why is this a problem?
- Admins never see the grey labels, so they can't review them as suggested tags and create them in Org Settings.
- We have to go back to QA authors and ask for the tags again. SMEs then have to dig back through project work they've already finished to re-tag those QAs.
- The "Create tags" option in the Projects section is misleading: roles with this permission have no practical way to create tags without Org Settings access.
Is there a workaround for this we might be missing, or is a fix planned so that roles with the "Create tags" permission can actually create tags from Projects and the Content Library?
