Contents - Index - Previous - Next

ProtoGenie Home Page

Protocol Security and Data Protection

Protocol Access Status
All protocols are designated Public or Private by the Principle Author.  Private means that no one but the principle author and people on their designated user lists (see below) can access the protocol.  

Every new protocol that is created from scratch has the default access status of "Private."  In other words, if the "Blank" startup option was used to create the protocol, then the access status is "Private."  However, if a new protocol is created by modifying a copy of a "Public" protocol, then the access status for that protocol will remain "Public."  If new authors want these protocols to be "Private," then they must manually change them to "Private."  See How to Make Public Protocols Private.  If the authors of protocols they have designated "Private," make copies, then the status of those protocols will remain "Private."

"Public" means that the protocol will appear in protocol searches by other ProtoGenie users and can be copied and it means that copies can be opened in the Composer/Editor, run, and edited.  When copies are made of public protocols to use as templates, they will have new titles and security status will be tied by log in to the new Principle Author.  

However, even when the security status is "Public," originals cannot be opened or modified in any way  This means that only the principle author or his designated users (see below) can view the original protocol and any results data associated with that protocol.

Only protocols designated "Public" will appear in the results of keyword searches by other ProtoGenie users.  Individuals must have an account with ProtoGenie in order to log in and use ProtoGenie.

Only the principle author can change the security status of a protocol from "Private" to "Public." For instructions on how to change the protocol security status from "Private" to "Public" or back again.

Exceptions to the "Private" Security Status
Obviously, there will be times when principle authors need to provide special access to their protocols to develop, test, and implement them.  Exceptions include Project Managers and Project Staff (testers and implementors).  These people are given access when they are added to the principle author's designated list of users.  When these additions are made, the level of access for each is clearly specified.  Levels of access are as follows:

View.  If designated users are permitted to "View" the protocol, they are authorized to open it in the Composer/Editor and see how it was set up.

Edit Copy.  If designated users are permitted to "Edit Copy" the protocol, they are authorized to make a copy of it and modify it to fit their needs.
Run.  If designated users are permitted to "Run" the protocol, they are authorized to execute it.  
Edit.  If designated users are permitted to "Edit" the protocol, they are authorized to make changes in the original.
Users.  This option allows the person with this permission to look at and modify the list of designated users.
Delete.  This permission allows the principle author and only the principle author to delete an original protocol.

Individuals other than the principle author cannot add other users to the designated user list.

Special (Run-Only) Access for Unsupervised (On-Line) Applications
Subjects in online surveys and experiments need enough access to RUN the protocol, but that is all they need.  Also, they should not see anything but the first screen of the protocol execution.  This is done is through the creation of a special URL that is opened online by the designated or volunteer subject and that takes him/her directly to the first screen of the run.  This special URL is created by clicking on the GET URL link at the top of the first page of the Composer/Editor.