Working in multiple LAAMP environments, or with multiple users

The recommended process is to open chrome, and an incognito window in chrome.  This can be done by selecting the three dots in the top right hand corner of chrome, and selecting the "Open New Incognito Window"

This will give you two Chrome Windows, which can be logged into different LAAMP environments, or logged in as two users in the same environment.  

An alternative approach is to use two seperate devices, with one for each environment.

General Tips and Tricks

• It is important to remember which window is logged into which user or environment.  The current user can be viewed either at a glance in the top right of the screen, or in additional detail on the top of the sidemenu on the left. 
• You may need to determine which Environment you are currently logged into on a window. There are steps to determine this available here.
• If you have multiple monitors available, It may be advantageous to keep one window on each monitor.
• Occasionally, it may be needed to hard-refresh the page to see the changes which you have made.  This is achieved by pressing Shift + F5 on PC or CMD + Shift + R on MacOS.
• Information regarding the meaning of different group types may be valuable, and Information on the different Group Types is available here.

Known Issues

While this type of work can be very helpful, use of Incognito mode is not currently fully supported.  As such, there are several issues which you may encounter while working in this manner.  They are not cause for alarm, and are generally minor cosmetic issues.

• When you switch your browser between environments, you may see the previous environment's dashboard icons. 
• When you switch your browser between environments, you may see the previous environment's details on the User, Competency, Sub-competency, or other pages.  This should clear after a few seconds, and you won't be able to access these items.
• If you are creating content, you may wish to test the changes.  If you have a testing user who has completed the Sub-Competency you are making changes to, that user will not be served the latest version.  Users are always given the version they completed.  You can force the user to be served the latest published version by either renewing the user's Sub-Competency, or by selecting to `publish and reissue` the Sub-Competency rather than just publishing it. 
• Changes to a user's permissions may not be reflected immediately on the list of user permissions located in the sidebar. You may have to clear the cache of chrome to see these changes be displayed.  Information on how to do this is located here.
• Undertaking assessments where evidence is uploaded may exhibit strange behaviour in Incognito windows.  We recommend that you do the testing of content in the regular window.

Moving Sub-Competencies between Environments. 

You may be interested in moving Sub-Competencies from one environment to another.  Below is some information relating to the recommended process for moving Sub-Comptencies.  Please note that any users who have completed this the moved Sub-Competency in one environment will not be marked as having completed it in the destination environment, and vice versa. 

If you're wishing to move Sub-Competencies from one environment to another, you may wish to make use of the Sub-Competency Import/Export functionality. By selecting the `Export` button on a Sub-Competency, you will receive a document containing the structure of the Sub-Competency. 

To import the Sub-Competency, you need a Sub-Competency which is in the draft state. This can be accomplished by either creating a new Sub-Competency, by selecting a published Sub-Competency and selecting the `Edit` button in the top right, or by selecting a Sub-Competency in the draft state. From here, you are able to select the `Choose File` button under the Import section, select your file, and then press the `Import`.  
Once this has been completed, you may wish to save the draft, or publish the Sub-Competency.