# Overview

The **Custom Files** page uploads custom provisioning files matched to phones by user-agent rules. Open it from **Configuration > Provisioning > Custom Files**.

The page works against the tenant currently selected in the top bar. The screenshots and demo rows were captured in the **Canistracci OIL** tenant.

<figure id="bkmrk-custom-files-list-pa">![Custom Files list page in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/c0rcustom-files-list.png)<figcaption>Custom Files list page in the Canistracci OIL tenant.</figcaption></figure>## Working with objects

<table id="bkmrk-taskhow-to-do-it-add"><thead><tr><th>Task</th><th>How to do it</th></tr></thead><tbody><tr><td>Add</td><td>Select the New custom file action, complete the form, and select Save.</td></tr><tr><td>Edit</td><td>Open the custom file from the list by selecting its name, number, or row action. Change the form and select Save.</td></tr><tr><td>Delete</td><td>Select the row checkbox and use Delete Selected, or open the custom file and select Delete, then confirm.</td></tr></tbody></table>

## Page functions

<table id="bkmrk-actiondescription-ne"><thead><tr><th>Action</th><th>Description</th></tr></thead><tbody><tr><td>New Custom File</td><td>Opens the creation form for a new custom file.</td></tr><tr><td>Delete Selected</td><td>Deletes the selected rows after confirmation.</td></tr></tbody></table>

## List columns

<table id="bkmrk-columndescription-na"><thead><tr><th>Column</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in lists and references.</td></tr><tr><td>Description</td><td>Administrative note shown in lists and reports.</td></tr><tr><td>User agent regex</td><td>Object setting shown by the form.</td></tr><tr><td>Size</td><td>Object setting shown by the form.</td></tr></tbody></table>

## Demo records

The tenant contains 1 documentation demo record for this page: Docs Demo Custom File 1.

## Deleting records

Before deleting a custom file, check references from call flows, destinations, schedules, reports, or provisioning objects. MiRTA PBX asks for confirmation before the delete is submitted.