Dear Palantir team,
Currently, there’s a helpful feature in Marketplace/DevOps that allows adding prefixes to installed Ontology resources such as Action and Object types - much appreciated.
I’d like to raise a feature request to extend this functionality to also include Automation and Workshop titles. This would help ensure better organization and consistency across environments, especially when managing multiple deployments.
Best,
Ivar
Hello 
I’ll pass this along!
Have you seen the installation suffix option? It won’t rename the individual resources, but the installation project will have the suffix, so it may help you distinguish each deployment wherever you see a path for a resource
In workshop, you can set the module titles as a parameter, which can help this situation. However, its still not a complete solution because it only changes the header, not the resource name, so in all the shortcuts and links, the deployed resources all have the same name, which is confusing and annoying.
That said, I’d also add a big vote for enabling workshop to add prefixes. I’d add an even bigger vote for having workshop be able to replace prefixes. For example, if I had a workshop resource named [DEV] Workshop Name, it would be nice to be able to replace the [DEV] with [QA] and in prod it replace [DEV] with an empty string.
Big vote on prefix replacement from me too.
Another super helpful feature similar to the parameterized module titles is the variable color for a Tabbed Section header which can be leveraged to visually differentiate the Marketplace deployments.