Online installation
Passwork is not resource-demanding, and the number of required servers depends on the number of active users, the amount of data stored and the system fault tolerance requirements.
See the full system requirements.
Open PowerShell as "Administrator":
When using Windows Server 2016, you must enable the TLS 1.2 security protocol using the command:
Get the PassworkModule.zip archive into the current directory:
In case of errors, the archive can be downloaded manually: https://repos.passwork.pro/repository/windows-powershell/PassworkModule.zip
Unzip the PowerShell module:
Start the online installation of Passwork:
The script will perform a user rights check and perform the download, installation and configuration of the components. If errors occur, the PowerShell shell will display the errors:

During execution, the script requests the certificate number from the customer portal:

Once complete, the address to connect to Passwork via a web browser will be displayed. This is what a successful installation looks like:

Once installed and configured, Passwork will be available at https://your_servername
By default, Passwork uses a self-signed certificate that is automatically generated during installation, so the first time you open the page you will see a message saying that the browser does not trust the certificate of the site.
As the first step, the system will offer to choose the interface language:

The checklist of parameters will show if all necessary components are installed on your server:

You must use the default MongoDB address to connect:

Passwork will generate a new key for server encryption. If Passwork is connecting to an existing database, specify the encryption key to be used.
Please use a key generated by Passwork. Using keys generated by third-party tools may cause errors.

You can download the license keys in your Passwork Customer Portal or request them from your managers.

By default, Passwork generates a self-signed certificate. After installation, you can switch to using full SSL certificates.
- For certificates issued by a trusted issuer.
- For certificates issued by domain certification authorities of your organization.
Open "Server Manager" → "Tools" → "Internet Information Services (IIS) Manager" → "Server Certificates" → and click "Import":

After importing, go to the Passwork website, open "Bindings" and select the imported web certificate for the HTTPS protocol:

If there is no domain CA (certificate issued by a trusted CA), but there is a public DNS name of the server, you can configure Let's Encrypt.
Passwork will be made available over HTTPS using a certificate from Let's Encrypt.
Background tasks are tasks that are executed by the scheduler in the background. For example, LDAP synchronisation, loading favicons, and other tasks that are time-consuming, persistent, or resource-demanding.
See a guide on setting up background tasks.