We have a review process set up in Splunk where multiple end users log in and tag individual events. These tags MUST be public by default so other users will not duplicate work. Forcing each user to go into manager and make all their tags public is not acceptable - it is way too much work for hundreds of review items every day.
What options do I have for forcing all tags to be public (app-level) upon creation?
Yes, I've done it in the past. But this is a little too extensive to be described here. Essentially it's modifying the behavior of the EventsViewer module using a custom application.js.
Symbolic AND hard links don't work, Splunk appears to remove the file before rewriting it. It appears Linux does not have the ability to allow write but disallow delete of the one tags.conf file in etc/users/username/appname/local while allowing updating of the other files.