Client System Requirements

1.    Browser

Lucidity is a Software as a Service (SaaS) application, which utilises a web browser on the client computer to allow access to the application.  The following browsers are tested and compatible with Lucidity Applications:

BrowserRelease / VersionVersion Check
Google Chrome (desktop)Latest Stable ReleaseCheck your version here
Microsoft Edge (desktop)Latest Stable ReleaseCheck your version here
Mozilla Firefox (desktop)Latest Stable ReleaseCheck your version here
SafariLatest Stable ReleaseCheck your version here

Mobile browsers including mobile version of the above are also supported, however due to the large range of platforms and OS, we don't conduct specific testing for each mobile browser release on each OS and platform.  If you encounter an issue we would encourage you contact us via our support portal.


2.    Flash, JAVA

Flash is not required for Lucidity to function correctly.  Customers may wish to upload Flash content to their CS Induction and CS Competency systems as presentation material, in which case the client computer / device will require Flash to view the content.  We suggest that HTML5 be considered as an alternate format in place of Flash.

JAVA is not required.

3.    Bandwidth

Bandwidth requirements are difficult to quantify - as with the internet in general, the more bandwidth that is available the better.

Bandwidth requirements can be broken into two categories:

  • Data entry / retrieval - online forms being completed, requests for information that is stored in the database for on-screen display
  • File uploads / downloads - Documents, PDFs, Excel files etc.

Data entry and retrieval has relatively low bandwidth requirements.  Users operating on limited bandwidth may experience a small delay while forms save or a long list is retrieved for on-screen display, similar to the delays the user would experience for general web browsing on a slow connection.

File uploads and downloads place a larger load on the connection.  The Lucidity help documentation and some parts of the system itself place file size recommendations or limits on what can be uploaded (and thus downloaded).  As an example, we recommend that 'best practise' for CS Competency Training Record attachments is to scan at 200dpi monochrome, resulting in a PDF file of around 100kB - 300kB per file.  This ensures that a slower connection such as a site office operating of a mobile connection will be able to download the file in a timely manner.

In general we do not recommend any file larger than 5MB is uploaded.  As a guide, if its unlikely to email then its not appropriate for online storage.  The exception is E-learning or CS Induction resources, which will typically stream and thus can be larger.

We provide a speed test on our server which can be used from any client computer to verify both upload and download bandwidth. A download speed of substantially less than 1 MB/s is likely to result in delays that are noticable by the User when accessing records or files.