Sharing plans and collaboration in planning

This forum is restricted to registered users. If you are a registered user, please login. If you would like to become a registered user, please join us.
6 messages - 984 views Feed-icon
How do I give a partner access to a plan we are working on, without given them access to other plans in the account?
 
We suggest setting up a separate account for the plan that you would like to share with your partners. There is no way to restrict access to plans within an individual account, so it is best to set up a separate account, all it takes to do that is an email address. To create a new account, ensure you are logged out and go to the login/create an account tab THCU

If you have already started the plan and would like to copy it over to a new account, create the new account and then email technical support at skingston@media-doc.com with details regarding which plan you would like to copy to and from which accounts.
 
What happens if two people are logged on working on the same plan, at the same time?
 
Two or more people can work on a plan at the same time by logging in on the same account. Any changes made by either user will be saved each time one of the users saves their data.
 
Are there previous versions of the plans saved somewhere – can we go back to previous versions if a partner makes changes we don’t agree to, or ‘undo’ work that has been done recently?
 
Unfortunately no. It is important that when working on a plan collaboratively you establish a clear, common understand around authority for updating or changing the data in the OHPP. Once data has been entered or changes have been made you cannot undo/go back.

It is also recommended that to alleviate potential issues related to multiple users that you: (a) establish a common practice of downloading and saving a full copy of the plan each time you update it, and (b) establish a naming convention each user will apply when saving the downloaded document to serve as a method of version control (for example: DocumentName_DayMonthYear_Time).

In using this practice you can refer back to previous versions and make revisions as warranted.