Private template permissions to override allowed PM tagging groups

AI-generated summary

The discussion revolves around private template permissions in Discourse Templates. evenrue wants to allow regular users to use private templates while restricting their ability to tag PMs with all available tags. Currently, users need access to all tags to use tagging in PMs, even if they only need to tag with template.

RGJ suggests a workaround using the automation plugin, which has been updated to relax its logic. The proposed solution involves creating a user (e.g., @Templates), setting up the templates plugin to use the template tag, and configuring the automation plugin to add the template tag to PMs sent to @Templates. Instead of having users tag PMs, they can send PMs to @Templates, which will then be automatically tagged.

I have a particular use case that I wanted to ask about for Discourse Templates and private templates. Assuming the current behavior is working as intended, I put this down as a feature request, but if it turns out that what I’m looking for is actually supported already in some way, would appreciate if I could be directed accordingly.

Currently my site is has many many tags and it is generally assumed regular users are NOT using them in PMs at all; I have tagging in PMs limited to only staff as we use it for administrative organizational support.

But I would like to potentially make available private templates to regular users. Given the current setup, even if I specify that the main group is allowed to use private templates, if I do not make ALL tags available to them (via regular Discourse settings), they will not have tagging enabled at all on PMs and therefore cannot tag with even just template.

It would be nice if there was a setting in Templates that allowed users in the permitted groups to tag only with the template tags specified by the Templates plugin. I realize this might be a tall ask, but wanted to throw it in there, especially if I’m missing something.

2 Likes

I have found a workaround for this. Since two weeks the logic in the automation plugin has been relaxed, so what you can do is set up an automation that tags the PMs, even when a user cannot do that.

  • Create a user, for instance @Templates
  • Set up the templates plugin so it uses the tag template to indicate a private template.
  • Set up the automation plugin so it will add the tag template to any PM sent to @Templates

  • Instead of having your users tag the PMs, ask them to send the PM to @Templates
1 Like