Getting started with the Web client

Here you can read about the requirements and what you need to do before starting to use Monitors web-based client.

The Monitor web-based client solution consists of two primary components: the Monitor Application Server (backend) and the Monitor Frontend Server (web server).

When reading the system requirements and preparations it is important to decide whether the web client should be used on internal network or be exposed to the internet.

Differences

Differences in the Interface and Login

Watch this short presentation covering:

  • The main differences in the interface
  • How to log in to multiple companies within the same Monitor system.

Authentication

User login without a password is not allowed, each user must have a password set in order to login.

Web-based client supports authentication via EntraID.

Regional settings

Web-based applications cannot read the local regional settings of the computer or device it runs on. Therefore, it is important that regional settings for every user is configured in Monitor ERP. This can be done for each user via the Users procedure, or it can be mass updated via the User list.

E-mail methods

Web-based client requires server-based e-mail methods to be used. Client-based e-mail method via Microsoft Outlook is not supported since 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

Web-based client supports below path types for file management:

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

Web-based client does not have permission to use local paths on client side. However, files can be selected and imported into Monitor from a local computer.