> For the complete documentation index, see [llms.txt](https://docs.17movement.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.17movement.net/conflict-tool/getting-started/installation.md).

# 📥 Installation

Setting up 17mov\_ConflictTool only takes a few steps.

### 1. Add the resource

Place the `17mov_ConflictTool` folder inside your server's `resources/` directory.

### 2. Add the required permissions

Open your `server.cfg` and add the following lines:

```cfg
add_unsafe_worker_permission 17mov_ConflictTool
add_unsafe_child_process_permission 17mov_ConflictTool
ensure 17mov_ConflictTool
```

Keep both `add_unsafe_*` permission lines **before** the `ensure` line.

We recommend keeping:

```cfg
ensure 17mov_ConflictTool
```

at the **very end of your `server.cfg`**. This makes sure all framework and bridge resources are already available when Conflict Tool starts.

{% hint style="warning" %}
The two unsafe permissions are required for the recommended apply mode. They allow Conflict Tool to modify files inside other resources.

Without them, scanning and reviewing conflicts can still work, but applying changes may fall back to a limited mode.
{% endhint %}

### 3. Configure access permissions

Only authorized players can open Conflict Tool and perform server-side actions.

If your server uses one of the supported framework bridges, Conflict Tool uses the framework's existing admin permission check automatically.

If no supported bridge is being used, the player needs the following ACE permission:

```
command
```

#### Giving access to a specific player

You can grant the permission directly to a player's FiveM license identifier in `server.cfg`:

```cfg
add_ace identifier.license:YOUR_LICENSE_IDENTIFIER command allow
```

For example:

```cfg
add_ace identifier.license:1234567890abcdef1234567890abcdef12345678 command allow
```

Replace the example identifier with the actual `license:` identifier of the administrator who should have access.

> 💡 **Tip**
>
> The server console always has permission to use Conflict Tool server commands, regardless of player permissions.

#### Custom permission checks

Conflict Tool's permission check can also be customized if you use your own administration or permission system.

The permission logic can be found in:

```
bridge/framework/[your_framework]/server.lua
```

You can modify the check there to integrate Conflict Tool with your own admin system.

### You're ready

Once the resource is installed and permissions are configured, restart your server.

Then continue with the Quick Start guide to run your first scan and learn the basic workflow.

[**⚡ Continue to Quick Start →**](https://docs.17movement.net/conflict-tool/quick-start)