I am sorry that you are experiencing that.  We are not seeing systemically reports that users are getting kicked out.  When users are reporting getting 'logger off' or 'kicked out of SIRAS it is usually for one of these reasons:
 

1)    Always confirm a strong wifi connection assuming that they are using wifi; a weak wifi will always cause SIRAS to be unstable.  Your wifi in the lower right corner should look like this:    Anything less than 3 bars will cause disconnections.

2)    Do not click on the refresh, forward, back button located in the upper left corner of your browser.  After you click that button, the next click you will get ‘kicked out’.

            
3)    Concurrent usage – if some is on the record before you and making changes to the MIS Summary page or in the Goal Developer that latter to arrive person(s) will be locked out of the record until the other person leaves that record.   Now, if the user access the record about the same time (about a 1 minute window depending), if they are both making changes especially to the MIS Summary page of the Goals Developer, they may get ‘kicked out’.

4)    The possibility is that it is a bug.  Sometimes bugs are obvious and sometime not so obvious, they are called ‘exceptions’ which would crash SIRAS and you will need to log back in.  These exceptions can be difficult to find.   So if the user gets ‘kicked out’ of SIRAS, its important to remember what record they were on and exactly what they did and try to replicate the situation.  Then please email support step by step on how we can replicate so that the bug can be corrected. 

FYI, SIRAS will auto log you off if there has not been any buttons clicked in SIRAS for 60 minutes.

FYI, if you are in a form for more than 10 minutes, SIRAS will automatically generate a dialog box asking you to save the form.  So, if you are typing directly in the form the most you can lose is 10 minutes worth of work.  Which still sucks but the loss is limited.