If you have "administrative" users on your account (such as receptionists and power receptionists), you can amend certain permissions around their access to letters and patient file attachments.

In some cases, letters and attachments might contain confidential patient information that should only be privy to their treating clinician. In this case, you would most likely not want receptionists to be viewing these documents. However, if you'd like receptionist users to be able to view letters and attachments, you can modify this within your account's settings.


Customise receptionist access to letters and file attachments

Head to Settings, and then General settings. Under Permissions, you'll see an area for Receptionists and rower receptionists:

You'll be able to tick (or untick) those boxes, depending on what you need. Below, we'll go over what each of those items means.

  • Can only read letters they authored themselves: if this box is ticked, it means that anyone with a receptionist or power receptionist role will only be able to read letters that they have written. So, they won't be able to view letters written by any other users on your account. We recommend turning this setting on if the letters that practititioners write to patients include confidential information that should not be viewed by reception staff.
  • Can view patient file attachments: if this box is ticked, it means that anyone with a receptionist or power receptionist role can actually see a file attachment—so not just the fact that the file exists, but the actual content of it. We don't recommend turning this setting on if your patients' file attachments contain confidential information that should only be privy to their practitioners.

Keep in mind that receptionists and power receptionists will still be able to write letters and view the general list of file attachments, but if you turn either of these settings on, the permissions will change accordingly for every user that is equipped with that role.


For more information on customising user permissions, head over here!

Did this answer your question?