On this part of the website, you have free access to up to date click-by-click instructions for NVivo on Windows. Simply click on the headings below to reveal the instructions.

Use the index of click-by-click instructions as a companion guide to help you find the instructions you need, or browse through the instructions below that accompany this chapter.

11.a. Passwords, Recording memos and tracking users and Identifying users


Passwords can be added to specific Projects to allow for Read/Write access or Read Only access.

  • File: > Project Properties > Passwords.
  • If you enter a Read/Write Password, you will also enter a Read Only Password.
  • You will be asked for the Password the next time you open the Project.

Recording Memos and tracking Users

  • With a Memo such as Teamwork in NVivo open and in edit mode, add the date and time (Ctrl + Shift + T) to track the chronology of ideas about team protocols, and write something about your team process (e.g., ‘We need to identify someone to manage the backup of our Projects.’).
  • Close the Detail View and look at the columns that are visible in the List View (Figure 11.1).


Figure 11.1 List View of Memos with Detail View closed or on the bottom

This is your first glimpse of NVivo’s ability to track researchers. This list is available for every type of item in the List View of your project (Files, Nodes, Attributes, Sets, Queries, Maps, etc.). We describe ways you might want to customize this list in Chapter 3.

Identifying Users

If you are working on a solo copy of the project, on your own computer, ensure that it is correctly registering you (and not the administrator) as the User each time you open the software. If you work on a shared computer, the default setting that does not prompt for the user on launch should be changed (Figure 11.2).

  • File: Options > General tab > Prompt for user on launch (check the box).

Subsequently, each time a researcher launches the software on the computer they will be asked to provide their login name and initials.


Figure 11.2 Setting the Application Options to ‘Prompt for user’ on launch in Windows (left) and Mac (right)

11.b. Combining Users

  • File > Project Properties > Users.
  • Click a name > Remove > Select a user (who will replace the User being removed) > OK > OK.

11.c. Turn the Project Log on or off and see Log entries

Turn the Project Log on or off

  • File: Project Properties > Write user actions to project event log (check or uncheck).

To see the Log entries (or to clear the Log):

File: Open Project Event Log (or Clear Project Event Log).

11.d. Manually matching the Project Title and Project Path

  • File > Project Properties > rename the Title > OK > Save the Project (Figure 11.4).


Figure 11.4 Changing the Project Title to match the Project Path (or File Name) (Windows)

11.e. Import the auxiliary Project

  • Open the master Project that will be the foundation for the new, combined project.
  • Ribbon: Import > Project > Project to import > Browse > locate the project you want to import > Open.
  • Tick the All (including content) option if you want to add all items in the auxiliary Project to the master.
  • Import.

11.f. View coding by different Users with Coding Stripes

  • Navigation View: > Data > Files.
  • List View: Double-click on a File.
  • Detail View: Click on some text so NVivo knows you are active in the File.
  • Ribbon: Document > Coding Stripes > Selected Items > check Users.

You will be shown the equivalent of a coding density bar for each User, allowing you to hover to see what Nodes each used (if any) for the adjacent passage of text (Figure 11.5). If you are using this method to review or assess commonality of coding strategies, it is critical that you hover over the different Users’ Coding Stripes to see what actual Nodes have been coded, as the stripe might appear the same, but the Nodes coded might be different.


Figure 11.5 Coding Stripes showing the work of three coders on a File