Customizing Log Sheets by Administrator

System setup is done in 4 stages:

1. 1Creating the hierarchy and list of production logs
   1. Defining the list of Companies
   2. Defining the list of Shops for each Company
   3. Defining the list of Logs for each shop or type of work
2. 2Creating system users
   1. Adding employees to the system
   2. Assigning an access level — deciding which logs each user can work with
3. 3Configuring the structure and rules of a production log
   1. Configuring the log’s general parameters
   2. Configuring the list of fields and the rules for filling them in
4. 4Configuring the voice-entry feature for the log
   1. Building the outbound-call scenario
   2. Configuring the voice settings of the bot

1. Entering setup mode

To start configuring the system, you need to switch to administrator mode (header will become green):

This feature is available only to users with the role of “administrator” or “owner”.

1. Creating the hierarchy and list of production logs

   After registering in Logsheets a Demo company is created by default. You can rename it and start working in it:

   

2. Defining the list of Companies

   If your operations are split across several legal entities, you can add additional companies (within the limits of your subscription).

   

3. Defining the list of Shops for each Company

   For convenience, you can set up a structure of shops or individual production areas in which a log is kept.

   

4. Defining the list of Logs for each shop or type of work

   You can decide for yourself which business logic to follow when building the structure of your production logs.

   Most often they are organised by type of work — for example: Health & Safety, Electrical work, Hazardous work, Equipment rounds and inspections, Production metrics, etc

   

2. Managing system users

To assign people responsible for keeping logs, you need to:

1. add them as users in the system,
2. and in the “Access” column set the value to “Full access” or “Read only”.

Note that responsibility for keeping logs can be assigned at three levels:

• at the Company level — the user can keep all logs across the Company
• at the Shop level — the user can keep all logs within that shop
• at the level of an individual log — then only that one log is available to them

3. Configuring the structure and rules of Production logs

Log settings are split into several sections.

1. General parameters

   

   Parameter	Purpose
   Title	The log title as it will be displayed to users
   Description	A detailed description of the log. May include the rules and requirements for filling it in.
   Status	You can manually set one of the following statuses: Active (default) — the active current log, available for record-keeping Read-only — the log is read-only; new entries cannot be added Inactive — inactive log. Available only to administrators
   Icon	Icon that will be used near log sheet name

2. Field configuration

   This is the main part of log configuration. Here you build the structure — the list of information you want to keep in the log.

   

   Here you can:

   1. + or + Add Field - add new column
   2. Delete fields
   3. Drag column header to change columns sequence
   4. Click on column header to change it settings

   

   For each field you can choose:

   Field parameter	Description
   Short field name	The main name of the field (also used on mobile devices)
   Long field name	A longer field name, which can be filled in for convenience on desktop
   Field type	Choice of data type. Can be: Text Number Date Yes/No checkbox Value from a list Attachment
   Value constraints	Depending on the field type, this section can contain additional validations or input constraints. For example: For numeric fields: minimum value, maximum value, number of decimal places, and unit of measurement. For list-based fields: the list of possible options.
   Required	Whether the system will require this field to be filled in before the entry can be saved
   Default value	If a default value should be filled in, you can specify it here (matching the field’s data type)