AXIOS BODYCAM & DASHCAM
FiveM Server Resource
Version 1.1.0

Worthy of the mission.


OVERVIEW

axios-media connects supported bodycam and dashcam recording providers
with AXIOS CAD/RMS operational records.

AXIOS manages recording metadata, officer/unit association, CAD context,
record links, permissions, and audit history.

Actual video capture is performed by the configured recording provider.


REQUIREMENTS

- An active AXIOS CAD community
- AXIOS FiveM bridge installed and paired
- A supported or compatible bodycam/dashcam recording provider
- Server-side provider configuration completed by the server owner


INSTALLATION

1. Extract the axios-media folder into your FiveM resources directory.

2. Configure the resource before starting it.

3. Confirm your AXIOS FiveM bridge is already installed, paired, and
   reporting ready.

4. Add the following to server.cfg in this order:

   ensure axios-cad-bridge
   ensure axios-media

5. Restart the server or start axios-media.

6. Join the server using a linked AXIOS account and verify operation with:

   /axiosmediastatus


CONFIGURATION

Configuration files included in this build:

No separate public configuration file was detected.

Review the included configuration before enabling the resource.

Do not place AXIOS pairing secrets, provider passwords, access tokens,
storage credentials, or signing secrets into client-accessible files.


MEDIA STORAGE

Video footage does not need to be stored on the AXIOS CAD host.

Each community/server owner controls the media provider and storage
destination supported by their deployment.

Supported deployment models may include:

- FiveManage
- Discord-based media handling where technically appropriate
- Owner-managed or self-hosted storage/provider endpoints

AXIOS primarily maintains the recording metadata, provider reference,
officer/unit association, operational record links, access controls,
and audit history.

Provider availability and recording capabilities depend on the provider
selected by the server owner.


RESOURCE ORDER

ensure axios-cad-bridge
ensure axios-media


DIAGNOSTICS

Use:

/axiosmediastatus

The diagnostic output is intended to report safe operational information
such as bridge readiness, player linking, unit state, provider status,
recording state, and recent synchronization state.

Credentials and protected media URLs should never be exposed in normal
diagnostic output.


SECURITY

All privileged AXIOS operations must remain server-authoritative.

Do not expose:

- AXIOS server pairing credentials
- API credentials
- signing keys
- provider secrets
- storage credentials
- private or signed media URLs

Client-supplied officer, tenant, department, or permission information
must not be treated as authoritative.


SUPPORT

When troubleshooting, provide:

- axios-media version
- axios-cad-bridge version
- output from /axiosmediastatus
- provider being used
- relevant FiveM server/F8 errors with credentials removed

