How to work on PT with two different user accounts [solved]

Question

I have found this one:

[Link Removed]

But I am not two different persons, I have (and want) only one user on my Windows computer but am presently working for two different orgs. So I need to toogle in PT between two users, to see and work the respective projects.

I found a permanent way, via the menu, to change registration info. But do not know how impactful that is, each time I need to toggle. What would it wipe? How long would it run? And with sloooow internet?

Other idea: Is there a way to install PT9 twice and make it look at different data locations. I am using - for historic - reasons a non-default data location anyway. What would happen, if I tried to install PT9 on a machine where it is already installed?

All ideas welcome. This is only for a couple of weeks, so will not even submit a feature request. I still want to work properly and not damage any project. Thank you.

Answer 1

Here is something I have done. I have a test user account for when I want to investigate a send/receive or shared project problem report.

Find your user settings folder, which is usually in c:\windows\users\USERNAME\appdata\local\Paratext93.
(USERNAME means your WIndows login user name. The last folder may be Paratext91 or Paratext92, depending on your installed version. Paratext93 means Paratext 9.3)

The registration info is stored in the file RegistrationInfo.xml.
So when you are logged into Paratext as User 1, copy the RegistrationInfo.xml file and name the copy User1Info.xml. Now when you use the registration info to change to the second user, when you finish close Paratext, and copy RegistrationInfo.xml to User2Info.xml.

Now when you want to switch IDs, copy the User Info file from the file you want to switch to, naming it RegistrationInfo.xml (replacing the existing file). When you start Paratext it should be using that user info. It will still go through the process of “Preparing Paratext for a new user” (I am not sure all that is involved).

But remember what anon848905 said about doing send/receive. One thing that could happen when you switch users is Paratext might say “you are an observer in Project X, all changes have been discarded”. So don’t make changes and forget to send them before you switch users.

Answer 2

When you use the menu (Registration Information) to change the registered user Paratext will mark history in all the projects and then you must close and restart Paratext. If you have projects in one organization that your new users is not a member of you can still open it (it is in your directory) but you will be an observer on that project. You can switch back and forth between users by changing the registration information and Paratext keeps track of who is working.

IT IS IMPORTANT to do Send/Receive on your projects to make sure everything is sent to the serves before you change users. This of course should be a regular habit. Always S/R before and after you start working.

Comments

I can report (also as a note to self) that this method is working well in Feb. 2023 with the presently up-to-date Paratext 9.xx.

We are not toggling user-accounts by the minute; rather rarely. But this is much better than my first work-around, where I had created a full second user on my Windows machine and made another install of PT.

Thank you @anon848905

Answer 3

Doing what anon848905 suggests (using the Paratext menu) is much safer as it ensures that changes are marked in the history for the correct user. If you are not careful when switching users without telling Paratext (via sewhite’s suggestion), changes may get put into the project history with the wrong user (rare, but it could happen).