# Clock on system

For standalone servers not able to use our ESX/QB-Core/vRP integration but still wanting the number of automatic fires to be relative to the amount of firefighters online, our clock on system is the solution.

Users can clock themselves on using the command _/clockfireon_ and _/clockfireoff_. Users are automatically clocked off if they disconnect from the server. If logging is enabled in your config, anyone that clocks on or off is also logged to the config.

To begin setting this up, navigate to the _automaticFires_ section of the _config.lua_ file. Once here, navigate to the _main_ section and then the `clockOnSystem = {` section.

```lua
 clockOnSystem = {
            enabled = false,
```

The clock on system is disabled by default. To enable this, set enabled to true.

Below this you are then able to enable the clock on and clock off commands if required. Alternatively, please see the later section on Server Exports and Events, as you may wish to instead clock users on using a menu or even integrate it in with a CAD system. Our _sv\_exports.lua_ file provides these exports and events.

The clock on command has the ability to use ace permissions only, as we have separate options for the three supported frameworks. The clock off command does not need ace permissions, as only those clocked on will be able to clock off and will already have had their permission checked, if setup.
