Document Actions
2.
Logging In
Up one level
Users must login before accessing the Load from OpenEngagement or Save to OpenEngagement dialogs. If users have not yet logged in, selecting these menu items will launch the Login dialog before the user proceeds to the corresponding dialog. The user will remain logged in until Working Papers is closed or the user specifically changes user account. The login dialog will not allow users to enter a username/password that is not registered with the OpenEngagement DMS. Users will use the same username and password they normally use to access the DMS through a web browser. When Working Papers is restarted later, the user may be prompted for their username and password again, depending on their selection for the two check-boxes in the Login dialog.
Users have two check-boxes in the Login dialog. The first allows users to save their username and password. The second specifies that they not be prompted again for their username and password. This second checkbox is enabled only if the first checkbox is checked. If the first, but not the second checkbox is checked, users will be prompted for their username & password each time Working Papers is restarted and they access an OpenEngagement dialog, but the Login dialog will default to the values they last entered in the Login dialog. If a user selects both checkboxes, they will not be prompted for their username and password again. However, if a user selects both checkboxes and later changes user account while using the Go-Between, the Go-Between will prompt them for their username and password the next time they start Working Papers, as it is possible the user wishes to save this new user account as their default.
Users are encouraged to check at least the first checkbox, in order that their username and password may be saved, and may be used when the Go-Between is used to open a Working Papers client file launched from a web browser interface to the DMS. This is explained later in this documentation.
The password will be saved in encrypted form on the same computer.
As with the web interface, each user has certain site-wide and local roles and these affect what they can do within the Go-Between. Specifically, it restricts which engagements they may download read-only, which they may download editable copies of, which they may upload to, and which Sections they may create Engagements within.