Overview
ManageThe availableThemes webpage interface themes.
Usein Admin > OverviewThemes controls host-name based branding for the MiRTA PBX web interface. A theme can change the selected UI package, Smartadmin layout behavior, logos, login-page text, menu additions, custom templates, and switchboard access behavior.
Each theme is selected by matching the requested web host against Server Name Regex. Keep the most specific host patterns for branded domains and use a broad expression only for the default theme.
Working with themes
| Action | Explanation |
|---|---|
| Create | Use New Theme from the Themes list, complete the host pattern and branding fields, then save. |
| Edit | Select a theme from the list by clicking the server-name regex, theme name, or title. |
| Duplicate | Use the duplicate action when a new branded domain should start from an existing theme. |
| Delete | Delete only unused themes. Removing the active catch-all theme can leave the login page without the expected branding. |
| Validate host matching | Test each branded hostname after saving. Regex patterns are powerful, so a broad expression can unintentionally match more hostnames than expected. |
Theme editor
The editor is split into sections. The screenshots use fictional documentation values and should not be saved directly on a production system.
Field reference
| Field | Description |
|---|---|
| Server Name Regex | Matches the HTTP host name that should use this theme. Use a precise expression for a branded domain, or a broad expression only for a catch-all default theme. |
| Theme | Selects the installed UI theme package. The standard value is smartadmin. |
| Fixed header | Keeps the page header visible while scrolling. |
| Fixed navigation | Keeps the navigation panel fixed while page content scrolls. |
| Menu on top | Moves the main navigation from the side panel to a horizontal top menu. |
| Push content | Pushes page content when the mobile navigation is opened. |
| Force RTL (Right to Left) | Forces right-to-left layout for languages or deployments that require it. |
| Boxed layout | Constrains the page width instead of using the full browser width. |
| Hidden Menu | Collapses the navigation until the user hovers over the visible navigation area. |
| Minify Menu | Shows a compact icon-oriented navigation menu. |
| Bigger Font | Increases the interface font size. |
| Skin | Chooses the Smartadmin skin, such as light, default, or dark. |
| Color | Applies one of the predefined Smartadmin color themes or a custom color file. |
| Other Body Classes | Adds extra Smartadmin body classes for advanced layout customization. |
| Provisioning host name | Overrides the host name shown in provisioning-related pages and generated provisioning links. Leave empty to inherit the configured host. |
| Title | Sets the browser tab title. Enable Smart to information. |
| Top Title | Sets the title shown in the top application area. HTML can be used for custom branding when needed. |
| Bottom message | Sets the footer or bottom message shown in the interface. |
| Additional menu | Adds custom menu entries. The field can use variables such as tenant code, selected tenant, tenant name, and username. |
| Additional Configuration item menu | Adds custom entries under the Configuration menu. |
| Additional Status item menu | Adds custom entries under the Status menu. |
| Additional Status/Stats item menu | Adds custom entries under the Status/Stats menu grouping. |
| Additional Admin item menu | Adds custom entries under the Admin menu. |
| Additional Bread item | Adds custom breadcrumb content. |
| Additional Head entries | Adds custom HTML entries to the page head. Use only trusted markup. |
| Logo Path | Path or URL for the logo image used by the theme. |
| Favicon Path | Path or URL for the browser favicon. |
| Custom CSS | Path to an extra CSS file loaded by the theme. |
| Custom Javascript | Path to an extra JavaScript file loaded by the theme. |
| Custom Login tpl | Template file used to override the login page for this theme. |
| Do not apply CSP | When enabled, the login page for this theme does not receive the Content Security Policy header. This is useful for legacy custom login templates while they are being updated. Leave it disabled when the custom login page is CSP-compatible. |
| Custom topmenu tpl | Template file used to override the top menu. |
| Custom dashboard tpl | Template file used to override the dashboard. |
| Custom Webphone URL | Alternative webphone URL. Use %%NAME%% to substitute the extension username. |
| Custom Wallboard ProxyAPI URL | Alternative Proxy API base URL used by wallboard integrations. |
| Max number of menu items | Controls how many Configuration menu items are displayed before the interface condenses them. This is applied at login time. |
| Max number of destination items shown | Limits the number of items displayed inside destination selectors. |
| Max number of Data Table items shown | Controls when larger lists switch to a |
| Default number of Data Table items show | Default page length for DataTable lists. |
| No menu items | Hides the main menu for this theme. |
| No header | Hides the page header for this theme. |
| Language | Forces a language for this theme, or leaves it on automatic browser detection. |
| Company | Company name shown on the login page. |
| Company Message | Main message shown on the login page. |
| Company Sub Message | Secondary login-page message. |
| Multiple clusters portal | Adds the cluster portal link for deployments that expose several clusters. |
| Switchboard login | Controls whether the login page shows a switchboard button, redirects to switchboard login, or shows no switchboard link. |
CSP and custom login templates
The Do not apply CSP option is intentionally theme-specific. It allows old or highly customized login templates to keep working while they are being made compatible with the login-page Content Security Policy. For a hardened login page, leave this option disabled and update the custom login template so all scripts, images, frames, and styles comply with the CSP rules.
Operational notes
Typicalshould Workflow
not access them.
Documentation Example
For documentationcertificate and testing,web-server useconfiguration namesstatus.
prefixed with Docs Demo. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.