Hi Jérôme, you should be able to use cloud project templates for this purpose. You should be able to set all the desired settings in the cloud project template and then specify this template when creating the project from Studio and/or use the "Save to Cloud" functionality. Both wizards give you the ability to specify a project template, and those settings should then be used as part of creating the cloud project and you should no longer need to make the changes manually every time. I cannot answer the API question, but I would think the same should apply - when creating a project via the API and specifying a project template that has the TM update settings set, then those settings should be applied as part of creating the project. I hope this helps, thanks, Daniel

Hi Jérôme, you should be able to use cloud project templates for this purpose. You should be able to set all the desired settings in the cloud project template and then specify this template when creating the project from Studio and/or use the "Save to Cloud" functionality. Both wizards give you the ability to specify a project template, and those settings should then be used as part of creating the cloud project and you should no longer need to make the changes manually every time. I cannot answer the API question, but I would think the same should apply - when creating a project via the API and specifying a project template that has the TM update settings set, then those settings should be applied as part of creating the project. I hope this helps, thanks, Daniel

Thanks Jerome from bringing this up. And also thanks Daniel for your reply.
We have the same issue at our organization. I have created a project template in the cloud and I do not get to see it when creating the project in Trados Studio so I cannot update the user-defined fields. Updating those fields is extremely important for us as we used them to filter TM matches when it comes to updating a particular document. Let me know your insights. Thanks a lot.

Thanks for your answer Daniel. For each project, we set a unique identifier in a field value. Since the identifier is unique, it doesn't make sense to save it in the template. We need at the project creation time.

The other field we set is a theme from a list of 18 different themes. In that case, I could created 18 templates covering all the themes. But it doesn't feel right and I would still have the problem with the unique identifier.

Yes, field values are a powerful and versatile feature. It is actually the only way for my agency to find the original text from which a TM unit comes from. It's a pity that this feature is buried in settings and not made more accessible for Cloud projects.