ARN Smart

BRANDING, GOVERNANCE AND SELF-HOSTED CONTROL

Administration

Ticketix administration covers portal branding with your name, logos, color, footer and page images, English, Turkish and Arabic interfaces, ticket forms with custom fields, agent and customer management with role-based access and two-factor authentication, and a self-hosted deployment with a scheduled task, license activation, updates from the Updates screen and diagnostic tools.

Branding

Make the portal look like your organization, not like a vendor.

Setup → Portal → General sets the system name, logos, primary color, footer text and support email. Removing the ARN branding leaves a clean footer, so the portal presents only your identity.

System name and company details. The name shown in page titles, the menu and emails, plus company name and mail domain.

Portal and admin logos. Separate logos for the customer portal and the agent area, uploaded or linked by URL.

Primary color. One color applied across buttons, links and highlights.

Footer and white label. Your own footer text; "Remove the ARN branding from the footer" drops the default "Powered by" line.

Support email. The address customers see for support.

Portal Content

Write the words and links customers see on each portal page.

Each portal page can carry its own background image, and an empty one falls back to the main image. The homepage cards and the administration menu are edited in the same setup area, and the headings and texts of the portal are interface texts that the translation editor changes per language.

Element Where it appears
Main image The portal homepage and the fallback for every other page.
Knowledge Base page image The knowledge base pages.
Community page image The community pages.
Search page image The search results page.
Announcements A band on every portal page and, for a product, a notice on its ticket form, shown for the time you set.
Homepage cards and menu links Label, address, icon, order, description and visibility. Login, Sign up, Submit Ticket and Track a Ticket keep their address and icon; they can be hidden and get a label and description for each portal language.
Footer The bottom of every portal page.

The resulting pages are described in Support Homepage.

Mobile & Responsive Experience

Serve customers and agents on any screen, in their language.

The portal and the agent area use a responsive layout, so menus and tables adapt to small screens. Three interface languages are built in, with right-to-left layout for Arabic.

Responsive layout. Ticket submission, replies, articles and community pages work on a phone.

English, Turkish and Arabic. Users switch the language from the header; Arabic turns the layout right-to-left.

Language settings. Choose the default language and which languages the portal offers.

Translation editor. Override any interface text per language without editing files.

Light and dark theme. The portal and the administration have light, dark and system themes.

Accessible navigation. A skip-to-content link, keyboard shortcuts for search and keyboard-closable dialogs.

Ticketix runs in the browser; it does not install as an app on the device.

Administrative Workspace

Run the whole platform from one menu.

The administration opens with a dashboard and a menu in four groups that the administrator can arrange; a search window (Ctrl K) finds tickets, articles, topics, customers and setup screens. Agents see a shorter menu than administrators.

Menu group What it opens
Work Dashboard with the figures of the day, what needs attention and staff notes; Tickets with views, bulk actions and New Ticket; Customers with accounts, invitations and context.
Content Knowledge Base, Community with its moderation queue, Canned Replies and Announcements.
Insights Reports: overview, content gaps, saved reports and roles and departments.
Setup Settings, Forms, Mail, Team and SLA, Automation, AI and Tools and updates, with a sub-menu for Portal, Support, Mail, Team, Automation and System.
User menu My Profile, two-factor authentication, theme and sign-out.

Agents see Dashboard, Tickets, Customers, Knowledge Base, Community, Canned Replies and Reports. Announcements and the whole Setup group, including the email templates, open only for administrators. Staff notes on the dashboard are visible to their author only, to chosen people or to all staff, can be assigned with a bell notification, linked to a ticket, article or topic and given a reminder date. Mail configuration and diagnostics are described in Mailbox Processing & Diagnostics.

Forms & Custom Fields

Ask for the details each kind of request needs.

Custom fields add structured questions to ticket forms, and form templates decide which fields appear for a product, category or department. Answers are stored on the ticket.

Field types. Text, text area, number, dropdown, radio, checkbox, date and file.

Rules. Required, minimum and maximum length, options and conditions in JSON that show a field only when another answer matches.

Visibility. Fields visible to customers or internal-only fields that only agents fill in.

Form templates. Versioned templates with an ordered field list, chosen by product, category or department key.

Captured data on the ticket. Agents see and edit the answers on the ticket screen; customers see their submitted details on the portal ticket page.

Guest and portal forms both use the templates; see Guest Tickets & Tracking.

Ticketix New field form showing field type, validation, JSON conditions and role visibility.
Ticketix 2.0.1 field and form-template configuration before demo fields have been saved.

Users, Roles & Security

Decide who can do what, and check every request.

Ticketix separates staff and customers. Staff are Administrators or Agents, and customers sign in only to the portal.

Administrators. Full access to tickets, settings, AI, SLA, automation, forms, mailboxes, the Mail Center, email templates, announcements, application keys, release notes, Tools and the license. Only administrators delete or merge tickets.

Agents. Work on tickets assigned to them, shared with them or sent to them for review, and on knowledge and community. Agents close tickets but cannot delete them, and they add, edit and delete the shared canned replies under Content → Canned Replies, work with customers and keep staff notes.

Team members. Create agents, set role and status, reset passwords and two-factor authentication, and keep a signature per agent.

Two-factor authentication. Administrators and agents set up an authenticator app at their first sign-in and receive ten one-time backup codes; the admin area does not open before that. Customers can turn it on for their own account. A locked-out account can be recovered on the server with scripts/account-recovery.php.

Password reset. Forgot password? on the portal and the staff sign-in emails a one-time link that is valid for 60 minutes; the form does not reveal whether an address has an account, and requests are rate limited.

Customer management. Filters, products per customer, tags, context fields, internal customer notes, recent activity, duplicate detection with merge, and invitations limited to chosen products that expire after 72 hours by default.

Request protection. Every form carries a CSRF token, sign-in and public forms are rate limited, and passwords are stored hashed.

Audit records. Status changes, rule changes, SLA overrides and other sensitive actions are written to an audit record in the database.

The organization operating Ticketix remains responsible for access permissions, customer-data policies, retention and mailbox security.

Self-Hosted Operations

Keep the platform, its data and its schedule on your own server.

Ticketix is installed on infrastructure your organization controls, with a MySQL or SQLite database and file storage on the same server. One scheduled task runs mail, SLA, automation, report and maintenance work.

Area What it covers
Requirements PHP 8.3, 8.4 or 8.5 with PDO MySQL or SQLite, mbstring, OpenSSL, cURL, ZIP, fileinfo and Sodium; HTTPS; Apache rules included, Nginx rules set by the host, including PHP in the api folder of the ticket API.
Setup A browser-based setup writes the configuration, including the public address used in email links; subfolder installations are supported.
Scheduled task php scripts/cron.php fetches and sends mail, runs SLA monitoring, delayed and inactivity rules, scheduled reports, knowledge publishing, AI jobs, staff note reminders, the weekly content gaps email and auto-closing, and checks ARN for updates every 12 hours.
License Activation with the ARNA code issued for the product and domain, after the administrator has set up two-factor authentication; a temporary license service outage does not lock the platform for up to 24 hours.
Updates From the Updates screen: Ticketix checks ARN with its license every 12 hours or on Check for updates. A mandatory update installs itself; any other update waits until an administrator clicks Install version. The database and the files that change are backed up first and put back if the update fails; after a successful update the files of the previous version stay until the next update. The official update package can still be extracted by hand; an installation on 2.0.2, 2.1.0 or 2.1.1 updates once this way, and later versions install from the Updates screen again.
Tools Administrators only: system information, mail queue counts and whether SMTP and IMAP are on, search index rebuild and queue processing, storage and writable-folder report with maintenance and cleanup, log viewer, quick system checks and ticket deletion with its files.
Health endpoint health.php reports database, schema and storage status to administrators or to a monitor that sends the health secret.
Ticket API Application keys under Setup → Support → Application keys; POST /api/ticket-create.php opens a ticket with technical details. Keys are stored as hashes and shown once.
Backup and export Back up config.php, the storage folder and the database; administrators can export a full support package.

Updates from ARN need the PHP ZIP and cURL extensions and write access to the application folder and to storage; the Updates screen warns when one is missing or when the scheduled task has not run for a day, and the update package can then be applied by hand.

A Practical Administration Workflow

  1. Set the system name, logos, primary color and footer, and decide whether to remove ARN branding.
  2. Choose the page images, then arrange the homepage cards.
  3. Add products, a form template with the fields each product needs and the first agents.
  4. Configure the mailbox and confirm that the scheduled task runs on the host.
  5. Open Tools after the first day and review queue status and logs.

Questions About Administration

Can the portal hide that it runs on Ticketix?

Yes. Set your own system name, logos and footer text and turn on "Remove the ARN branding from the footer".

What does Ticketix need from the server?

PHP 8.3 or newer with the listed extensions, a MySQL or SQLite database, HTTPS and a scheduled task. Email needs a mailbox with IMAP and SMTP access.

Where is customer data stored?

In the database and the storage folder on the server where Ticketix runs. Text leaves the server only for your mail server and, when you turn AI on, for the AI provider you connect.

Can administrators limit what an agent can do?

Yes. Agents work only on tickets assigned or shared with them, see a shorter menu and cannot change settings, AI, SLA, automation, forms or the license. Announcements, the Mail Center, email templates, Tools, Updates and ticket deletion are also reserved for administrators.

Reviewed against Ticketix 2.2.1 source code · Last updated 9 November 2026