Upvoting this. Our internal translators use GroupShare, but when using external translators, we must send them a package, and it’s really pointless to have to enter a user.

Evzen Polenka Polenka ,I could not agree with you more!!

Complately what I want to say. And also we still need projects offline.

Would this ploblem be solved by develop group guys? Me and not only me will desire of that. Many thanks to sb.  who could help to improve this.

Hmmm, nice try... if GroupShare would be FREE, then it could be maybe considered as "partly delivered". But it's not free at all.

The whole point of the idea is simply to remove the mandatory user name in the package creation step, especially because the user name basically means nothing.

Many of us simply use single generic user named "Translator", just to satisfy this crazy requirement.

The point is that the actual translator who ends up getting the package is unknow at the time of creation of the package... simply because the person creating the opackages has nothing to do with assigning the translation tasks to actual people, or because it is unknown which translator will be available for the task, or for any other reason.

The whole thing is about implementing simple default user name which would be automatically used if the user name field is not filled. That's it.

I don't see any reason to pay terrible money for GroupShare instead.

Have you considered using GroupShare?  You could create a template for the assignment just once and then use this to assign the work in one click.