Get started with the web client

Here you can read about the requirements and what you need to do before you start using Monitor's web-based client.

Monitor's web-based client solution consists of two main components: Monitor Application Server (backend) and Monitor Frontend Server (web server).

When reviewing the system requirements and preparations, it is important to determine whether the web client should be used within the internal network or exposed to the internet.

Differences

Differences in interface and sign-in

See this short presentation (in English) covering:

  • The main interface differences
  • Signing in/Logging in to multiple companies within the same Monitor system

Authentication

Passwordless sign-in is not supported. Each user must have a password configured in order to sign in/log on.

The web client supports authentication through Entra ID.

Regional settings

Web applications cannot read the local regional settings of the computer or device on which they are running. Therefore, it is important that regional settings are configured in Monitor ERP for each user. This can be done individually for each user in the Users procedure, or updated for multiple users at the same time using the User list procedure.

E-mail methods

The web client requires server-based e-mail methods. Client-based e-mail using Microsoft Outlook is not supported because web applications cannot access locally installed software on the computer.

Supported methods:

  • Server based, via Microsoft Exchange
  • Server based, via Microsoft Exchange Online
  • Server based, via SMTP

File management

The web client supports the following path types for file management:

  • Local paths on the Monitor server.
  • UNC paths configured on the Monitor server.
  • SharePoint Online.

The web client does not have permission to access local paths on the client side. However, files can be selected from a local computer and imported into Monitor.