I am very interested in this feature. It would make it easier for me both as a PM and as a linguist. The split and join functions in Memsource are very robust (thank you) and there are virtually no cases that I can think of where I would not want to enable unlocking of locked segments for a linguist.

Note, an idea that I have is that the feature would be selectable by the PM or administrator. Therefore, if a company did not want to enable the feature for their linguists, they could leave it disabled.

I too am very interested in this feature, it would be very helpful and avoid wastes of time bothfor the PM and the linguist, hopefully you can make it available soon :)

I am super interested in this feature request from a PM perspective. It is not feasible to be unlocking segments for linguists on an ad-hoc basis when you're handling a high number of projects daily, and we have seen plenty of tag issues already for strings that are leveraged in 100 and 101% and locked. Allowing our providers/linguists to unlock and correct these, or any other issues as needed, will be an extremely useful feature to have for something that should really be allowed by default. I agree with the Note from Sept 7th above on allowing the PM to select and allow this feature at a project level.

Upon activation, the exisiting Access and security feature "Linguists may edit locked segments” should give the Linguists the right to unlock segments (like PM can do via CTRL+L). 

Having this feature will eliminate the introduction of TM inconsistencies. If Linguists, in Translation step, only edit (and not unlock) locked segments, the users in the subsequent steps will not be aware of the changes made in locked segments, and they will not save the amended locked segments to TM.