If you want to use the standalone version, you can either try it anonymously for 15 days without a license key (option A) or register a standalone license key (option C). You can get a license key either by purchasing a standalone license or by requesting a trial extension.

The setup guide will then help you create a new repository for your data or use an existing one.

Once the setup is completed, you may want to review the default settings (timer reminders, language, etc).

If you want to use the server version, you first need to decide which computer will run the server and which computers will connect to the server.

Once the setup is completed, you may want to review the default settings (timer reminders, language, etc).

A Fanurio server can encrypt communications to and from clients with SSL to protect your data from being intercepted by others. To do this, it needs to be configured with a keystore that contains your SSL certificates. Here's how to do it:

Before you learn how to create a keystore file to hold your SSL certificates so you can enable SSL for a Fanurio server, you need to understand the difference between CA-signed certificates and self-signed certificates:

This section shows how to create both types of certificates.

About Java keytool

To generate a keystore, you need a JDK installed and the keytool utility on your PATH. You can verify this setup by typing keytool at the shell prompt. You should see a list with all the keytool commands, similar to this:

$keytool
Key and Certificate Management Tool

Commands:

 -certreq            Generates a certificate request
 -changealias        Changes an entry's alias
 -delete             Deletes an entry
 -exportcert         Exports certificate
 -genkeypair         Generates a key pair
 -genseckey          Generates a secret key
 -gencert            Generates certificate from a certificate request
 -importcert         Imports a certificate or a certificate chain
 -importpass         Imports a password
 -importkeystore     Imports one or all entries from another keystore
 -keypasswd          Changes the key password of an entry
 -list               Lists entries in a keystore
 -printcert          Prints the content of a certificate
 -printcertreq       Prints the content of a certificate request
 -printcrl           Prints the content of a CRL file
 -storepasswd        Changes the store password of a keystore

Use "keytool -command_name -help" for usage of command_name

Creating a keystore with a self-signed certificate

To generate a private key and add it to a keystore, you need to use the genkeypair keytool command. The following command creates a keystore file called fanurio.jks in the current directory.

keytool -genkeypair -alias fanurio -keyalg RSA -keysize 2048 -keypass changeit -storepass changeit -validity 365 -keystore fanurio.jks -ext SAN=DNS:localhost,IP:192.168.2.105,IP:127.0.0.1 -dname "CN=localhost, OU=Development, O=Fanurio Time Tracking SRL, L=Craiova, ST=Dolj, C=RO"

You can verify its contents using the list keytool command:

keytool -list -v -keystore fanurio.jks

The resulting keystore file contains a self-signed certificate that can be used to configure your server.

Creating a keystore with a CA-signed certificate

To create a CA-signed certificate for your server, you need a self-signed certificate (read above). Then you need to follow these steps:

The keystore file now contains a CA-signed certificate that can be used to configure your server.

There are four possible roles a person can have in Fanurio, each with their own level of permissions.

The following table outlines these roles and what they're allowed to do:

Roles with limited access work with a partial copy of the data available on the server. For instance, tasks are downloaded without their billing settings by users who don't have billing permissions. This ensures that sensitive information like billing details or personal information remains protected.

Admins can assign or change the role of other users from Business » Manage People (available only in server mode).

When the role of a user is changed, Fanurio notifies the user about it the first time he or she connects to the server to synchronize their data. When that happens, Fanurio also resets the local repository to download the data the user is allowed to access.

If there are any local changes that haven't been synchronized, Fanurio exports them to disk so they can be reviewed manually. Since reviewing local changes manually can be a laborious process, admins should ask their users to synchronize local changes before changing their role. If a user hasn't synchronized their changes, admins can revert their role temporarily so they can synchronize them.

Admins can grant and revoke project access to other users in two ways:

When access to a project is granted or revoked to a user, Fanurio notifies the user about it the first time he or she connects to the server to synchronize their data.