Introduction:

Collaborative Authoring in Project Vault

Project Vault is a stand-alone application provided by Veeva to customers engaged with active services work.

With Collaborative Authoring enabled, users who are in Project Vault are also added to the Veeva Office 365 tenant as guest users, able to take advantage of the collaborative authoring capabilities within Project Vault. The same Veeva security of Office 365 is applied to this specific tenant by the Veeva Technical Operations team.

With the 21R2 feature, users no longer require an invitation to the Collaborative Authoring tenant to begin using Collaborative Authoring - this now happens behind the scenes automatically. See Automate Guest Invites to Azure AD from Vault for more details.

Veeva End Users

Collaborative Authoring in Project Vault will recognize that a Veeva End User already has a license to Office 365. The Veeva End User is still created as a Guest in the new Office 365 tenant using the Veeva End User's @veeva.com email address. This email address is already Licensed to use Office 365; the invite is to use the additional Office 365 tenant specifically for Project Vault.

Customer End Users

Collaborative Authoring in Project Vault will use a Customer End User's email address when being created as a Guest in the new Office 365 tenant. This email address must be licensed to use Office 365; the invite is to use the additional Office 365 tenant specifically for Project Vault.

If a Customer End User's organization does not have an Office 365 tenant with SharePoint and/or the Customer End Users do not have Office 365 Business licenses that include Office client applications (at least Office 365 Business or Office 365 ProPlus), they will not be able to use Collaborative Authoring.

Microsoft Support and Recovery Assistant

The usual fix for instances where the Desktop Microsoft Collaborative Authoring doesn’t work as expected is to purge credentials/ fix the registry. Microsoft has a Support and Recovery Assistant (SaRA) specifically for a scenario like this.

Read more about this Microsoft tool here:  About the Microsoft Support and Recovery Assistant.

Troubleshooting Tips:

This article gives troubleshooting tips for Collaborative Authoring using Project Vault. 

Video:

Due to the shared collaborative nature of the system, authentication into Project Vault’s own tenant for Office 365 is necessary before collaborative authoring can be used. This means an organization may authenticate into Project Vault’s Office 365 in addition to any other Collaborative Authoring tenants currently in place.

Here are some common things to try if you are having trouble with Collaborative Authoring in Project Vault.

Stuck in a Sign-in Loop?:

1. Initiate an Edit in Microsoft Office action in Vault.
2. Close the popup dialog.
3. Click the ? icon in the blue Collaborative Authoring Banner.
4. Click Continue to open the document in the browser.
5. If an error is received, sign out and sign back in with the email associated with your Vault user profile.
6. Accept the invitation to join Veeva Systems.
7. Follow the steps to set up 2FA.
8. Return to Vault.
9. Initiate an Edit in Microsoft Office action in Vault.
10. Select Edit in Desktop Application.

CA is working in Browser but not in Desktop App:

• If you have permission to download applications on your computer, do the following:
  
  
  1. Navigate to https://aka.ms/SaRA-OfficeSignInScenario.
  2. Download and install the Microsoft Support and Recovery Assistance (SaRA) for Office Sign-in Scenarios.
  3. Follow the steps.
  4. Select No when prompted if Sign In was successful even if able to sign in when in the tool.
     • This forces the tool to purge your stored credentials.
  5. Once the tool completes, restart your machine.
  6. Initiate an Edit in Microsoft Office action in Vault.
  7. Select Edit in Desktop Application, if applicable.
     
     
•  If you have limited permissions on your computer, contact your IT Department for further assistance.