Many projects involve multiple researchers working together.
If more than one user wants to work on a project at the same time, you can establish a 'master' project, and then give a copy of the master project to each team member. The team members work in the copied projects while you work in the master project. At regular intervals, import your team members' work into the master project.
Each team member can have their own user profiles in the project, however, users are not 'authenticated', so team members must take care to use the correct user profile.
We recommend that all team members use the same version of the software. We do not recommend working in teams with some members using the Windows platform and others using the Mac platform due to some known limitations and issues. Work with projects on Windows or Mac
If you are working in a team you should consider combining NVivo with NVivo for Teams. NVivo for Teams
When you first start NVivo, you are prompted to set up your default NVivo user profile. When you work in a project, this user profile is used to create your project user profile. If each team member accesses the project using their own user profile, you can monitor the work done by different team members.
If you change your default NVivo user profile, the next time you work in your project, a new project user profile will be created. Work you do from this point onwards will be associated with the new project user profile.
If you accidentally create two separate profiles in your project, you can merge the two user profiles, by removing one of the project user profiles and assigning all associated project content to the other user.
If team members login to a computer using a shared user account, then—if you want to be able to track their work individually in a project—it is important that each person uses their own NVivo user profile.
Each team member can create their own user profile and should ensure they use the correct user profile whenever they access the project. When a team member opens the project, they can check to see which user profile is currently in use. If they are not using the correct user profile, they can switch user profiles without closing the project.
You can also turn on the automatic prompt for user option, so that team members are prompted to enter their user account whenever they launch NVivo. When one team member finishes working with the project, they should exit NVivo, so that the next user is forced to launch NVivo and will be prompted to enter their user profile.
NOTE In NVivo for Teams projects, project user profiles are based on the user account used to login to the computer. If team members share a computer user account, you cannot track their work individually.
- A 'Read/Write' password—allows full access to the project.
- A 'Read Only' password—allows users to view the project. This password also allows users to copy your project or import data from your project into another project.
Set project passwords in Project Properties—click File > Project Properties.
NOTE If you are working with an NVivo for Teams project, you control access to your project by adding users to project user groups and by enabling or disabling 'guest access'. Control access to an NVivo for Teams project
NVivo for Teams allows simultaneous multi-user access—this means that everyone in your team can work on the same project at the same time. Team members can code, annotate, and link content at the same time.
NVivo for Teams project user profiles are linked to Windows user accounts. In a Teams project, the Project Owner controls who can view or modify the project. Users are authenticated when they connect to NVivo for Teams, and when they connect to a project.
'Edit mode' ensures that team members do not make conflicting changes to content. When you have a file open in edit mode, you have exclusive control of the content—other users can view the file, but they cannot edit, code, annotate or link the content. Edit mode also prevents conflicting changes to maps and reports.
The Project Owner can open the project exclusively, locking out all other users. This is necessary when importing structure or content from another project. It can also be useful if you are making large scale changes and want to be certain you can reverse your changes using the undo function.
Make sure that all team members who are working on a shared project are using the same version of NVivo. NVivo for Teams can host projects in NVivo 12, NVivo 11 and NVivo 10 formats.