Can multiple users open, write and save an openroads template library at the same time on a server?

If the template library can be opened by two users at once (which may work, may not--if it's like Microstation DGN files, only one of you will be able to open it read-write), you won't both be able to save the file at the same time, and if one of you saves the file, I don't think the other user's copy will be repopulated with modified templates without resetting their work.

If the template library can be opened by two users at once (which may work, may not--if it's like Microstation DGN files, only one of you will be able to open it read-write), you won't both be able to save the file at the same time, and if one of you saves the file, I don't think the other user's copy will be repopulated with modified templates without resetting their work.

Last time I checked, it was 100% possible for user A to open a ITL or an IRD followed by user B doing the same. Then have user A make a bunch of edits and save their work and exit. Finally, user B makes a few edits, saves their work and exits and all of user A's edits are lost.

So how does everyone get around this problem when you have multiple people accessing the ITL file? I am getting ready to have multiple people working on a project and right now we have 1 ITL file, is the only way to fix this to have an ITL file for each corridor (which has its own dgn)?

Per corridor might make sense. One other option (perhaps far from ideal) is to have everyone use their own ITL to work with and use that for template drops.

In either case, when you've come closer to a stage where you can have one ITL projectwide, you can gather each template that is in use into one ITL. To do grab templates that are in use within a corridor, from within the Create Template window, go to Tools > Template Library Organizer. Expand the Active Design File Corridors. For each corridor you'll have a list of the templates used in that corridor. Then drag each template into your new primary ITL.

That is an excellent approach - have everyone copy a "seed" itl and add their initials or some other identification to each file and them have a master itl that is only used for template drops and then closed.
Any time someone needs to update the master, they can let everyone know that need it exclusively, use the organizer to add new templates and save and close when done.
Periodically, everyone would copy the master to make their new personal itl, so everyone stays up to date will all additions.

Thanks for the input everyone. Template libraries have been around for a long time and it would be nice to have a multi user solution such as projectwise design history in the next CONNECT edition.