> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-admin/installation.md).

# Installation

1. Download the resource from [Cfx Keymaster](https://keymaster.fivem.net/) and put the `daddy-admin` folder in your `resources` directory.
2. Add it to `server.cfg` after ox\_lib, oxmysql and your framework:

   ```cfg
   ensure oxmysql
   ensure ox_lib
   ensure qbx_core        # or qb-core / es_extended
   ensure daddy-admin
   ```
3. Start the server once. Missing tables are created from `sql/install.sql` automatically (`Config.Database.AutoInstall`). The console prints `SQL install complete` the first time.
4. Become owner: while the server has no owner, a one-time code is printed in the server console. Join, type `/adminclaim` and enter the code. Then create roles on the Staff page, see [Roles & Permissions](/daddy-studios-docs/scripts/daddy-admin/permissions.md).
5. Join and press `F9` (or type `/admin`) for the quick menu, `/adminp` for the full panel.

## What is detected automatically

The console shows what was found when the resource starts:

```
[daddy-admin] Compat: framework=qbx inventory=ox target=ox_target
```

If the detection picks the wrong resource, set it in `config/shared.lua`:

```lua
Config.Compat = {
    Framework = 'auto', -- 'auto' | 'qbx' | 'qbcore' | 'esx' | 'nd'
    Inventory = 'auto', -- 'auto' | 'ox' | 'qb' | 'ps' | 'lj' | 'jpr' | 'qs' | 'codem' | 'core_inventory' | 'tgiann' | 'origen'
    Target = 'auto', -- 'auto' | 'ox_target' | 'qb_target' | 'lib_fallback'
}
```

See [Integrations](/daddy-studios-docs/scripts/daddy-admin/integrations.md) for phones, appearance, billing, housing and the other optional scripts.

## Players

Every player can open a ticket with `/report` or `/support` and follow it under "My tickets". Staff get an alert for new tickets and replies.

## Updating from 1.x

Version 2.0.0 replaces ACE ranks with roles managed in the panel. The first start after the update resets the staff list and roles once and switches off scheduled console commands. Claim owner again with `/adminclaim`, then rebuild your roles. The admin `/heal` command is now `/aheal`.

## Checking the setup

`daddyadmin_doctor` in the server console lists the detected integrations, missing tables and installed scripts without an adapter.

## Escrow

`config/`, `locales/` and every file in `bridge/` are open in the escrow edition, so you can add a renamed resource or a custom table there.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-admin/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.