System Overview

ForsetiDesk is a fully self-hosted IT service desk platform designed for teams that require complete control over their data and workflows. Unlike cloud-based solutions, ForsetiDesk runs entirely on your own Windows infrastructure — no external dependencies, no data leaving your network, no mandatory subscription fees.

ForsetiDesk was built by practitioners who lived the problem — born from years of frustration with rigid, uncustomizable service desk platforms. While designed for IT teams, ForsetiDesk is flexible enough for any service operation that needs accountability, workflow, and data ownership.

Key Features

• Complete ticket lifecycle management from creation through QA-verified closure
• Mandatory QA/QC review — technicians cannot close tickets without supervisor approval
• Configurable ticket ID numbering (auto, sequential, prefixed, custom)
• Hierarchical category system — up to 5 levels on Pro, 2 on Core
• Email notifications to clients on ticket events (new in 1.4)
• Email-to-ticket inbound mailbox — tickets auto-created from incoming email (new in 1.4, Pro)
• Self-service password reset — no admin needed for routine resets (new in 1.4)
• Canned responses — one-click reply templates for technicians (new in 1.4)
• Internal notes — private tech-only comments hidden from clients (new in 1.4)
• Knowledge base with markdown articles, attachments, and bidirectional ticket linking (new in 1.5)
• Public client-portal KB articles (new in 1.5, Pro)
• Ticket merging — combine duplicate or related tickets into a single primary (new in 1.6)
• Ticket-to-ticket linking — Related, Parent/Child, Blocks, and Duplicate relationships (new in 1.6)
• Automation rules — event-triggered workflow engine with condition/action builders (new in 1.7, Pro)
• Webhooks — HMAC-signed outbound HTTP POST on 12 ticket events with retry logic and delivery log (new in 1.8, Pro)
• Recurring tickets — template-based automatic ticket creation on daily, weekly, monthly, or custom CRON schedules (new in 1.8, Pro)
• Time tracking — per-ticket time entries with billable flag, global persistent timer bar, and analytics (new in 1.9, Pro)
• Per-organization SLA & QA policies — organization model with domain auto-matching, per-org SLA targets and QA requirement overrides (new in 1.9, Enterprise)
• LDAP / Active Directory SSO — authenticate users against your existing directory with auto-provisioning on first login (new in 1.9, Enterprise)
• Bring Your Own Database — point ForsetiDesk at your own external PostgreSQL instance instead of the bundled database (new in 1.9, Pro)
• Asset Management / ITAM — full lifecycle tracking (ORDERED through DISPOSED), structured location hierarchy, rack elevation diagrams, end user assignment, ticket linking, CSV import/export (new in 1.10, Pro)
• CMDB — CI relationship mapping with 5 relation types and interactive D3 topology graph (new in 1.10, Enterprise)
• Change Management — ITIL-aligned change requests with approval workflows, risk/impact scoring, and linked tickets/assets (new in 1.10, Pro)
• SLA management with visual breach indicators and alerts (Pro)
• Full analytics dashboard with custom widget builder (Pro)
• Data export: CSV, JSON, Excel (.xlsx), and TXT formats (Pro)
• PowerBI API integration for external dashboards (Enterprise)
• Custom fields — TEXT, TEXTAREA, DROPDOWN, MULTISELECT, DATE, CHECKBOX, CASCADE (Pro)
• Role-based access control — Admin, Tech, QA, Client
• Native Windows desktop application (all tiers)
• Database backup and restore (Pro)
• User audit log — tracks all admin actions (Enterprise)
• Problem Management — KEDB, Root Cause Analysis with 5 methods, and problem-to-incident linking (Pro)
• Service Catalog — configurable request forms with approval chains (Pro; catalog builder Enterprise)
• Service Request workflow — sequential multi-level approvals and fulfillment tracking (Pro)
• Dashboard customization — drag-and-drop widget layout with persistent save (all tiers)
• Asset and Change analytics charts — visual summaries of asset status and change activity (Pro)
• Change calendar view — Day, Week, Month, and Agenda modes for scheduled changes (Pro)
• Change export — CSV, JSON, and XLSX formats (Pro)
• Automation triggers for asset and change status events (Pro)
• Webhook events for assets, changes, problems, and service requests — 35 total events (Pro)

License Tiers

Getting Started

Accessing ForsetiDesk

ForsetiDesk can be accessed via the native Windows desktop application or through a web browser. Your administrator will provide the server address. The default URL is:

Logging In

Enter your email address and password on the login screen. Contact your administrator if you do not have credentials. On first login you will be required to change your password before accessing the system.

Forgot Your Password? NEW IN 1.4

If you cannot remember your password, you no longer need to contact an administrator. Use the self-service reset:

1. On the login screen, click Forgot Password? below the password field.
2. Enter the email address associated with your account and click Send Reset Link.
3. Check your inbox. A message from ForsetiDesk arrives within a minute or two containing a one-time reset link.
4. Click the link in the email. It opens the reset page where you set a new password (minimum 8 characters).
5. After setting the new password, log in normally with your new credentials.

Navigation

User Roles

End User Guide

Creating a New Ticket

Click the + New Ticket button in the sidebar or navigate to Tickets and click New Ticket in the top right corner.

Ticket Fields

Priority Levels & Default SLA Targets

Ticket Status Flow

Email Updates on Your Tickets NEW IN 1.4

If your administrator has configured email notifications and your ticket has a client email address set, you will automatically receive emails at the following points:

• When your ticket is first created — confirmation with the ticket ID
• When a technician is assigned to your ticket
• When the status changes
• When the ticket is approved by QA and closed
• If QA rejects the resolution and the ticket is reopened for rework

Each email includes the ticket ID, title, current status, and a direct link back to the ticket. If you stop receiving updates and you expect them, contact your administrator — email notifications can be toggled on or off per event by the admin.

Browsing the Knowledge Base NEW IN 1.5

Click Knowledge Base in the left sidebar to browse published articles your IT team has made available to you. Many common issues have a self-help article that may resolve your problem faster than submitting a ticket.

• Use the search bar at the top to find articles by keyword
• Filter by category to narrow the list
• Click any article title to read the full content, including any attached files like screenshots or PDFs

Merged Tickets NEW IN 1.6

If your ticket has been combined with another related ticket by the IT team, you will see a banner at the top of your ticket indicating it has been merged and providing a link to the primary ticket where work is continuing. Merged tickets are read-only.

Technician Guide

Working a Ticket

Click any ticket from the Tickets list to open the detail view. From here you can review all ticket information, edit fields, add notes, and track your work time.

Editing a Ticket

Click the Edit button on the ticket detail page. In edit mode you can modify:

• Title and description
• Priority and status (cannot set to Closed directly)
• Assigned technician and category
• Tags and custom field values
• Client name and email
• Troubleshooting notes — document your diagnostic steps clearly
• Resolution notes — describe exactly how the issue was resolved
• Start time, end time, and resolution date

Click Save to commit changes. All changes are logged in the Activity Log with your name and timestamp.

Submitting for QA Review

1. Ensure your Resolution Notes clearly explain how the issue was resolved.
2. Set the End Time and Resolution Date fields.
3. Click the Submit for QA button in the ticket detail view.
4. The ticket status changes to Pending QA and appears in the QA Queue.
5. If QA rejects the ticket, it returns to you as QA Rejected with notes explaining what to address.
6. Rework the ticket and resubmit when ready.

Activity Log

Every change to a ticket is automatically recorded in the Activity Log at the bottom of the ticket detail page. The log shows who made each change, when it was made, and what specifically changed — providing a complete audit trail.

Internal Notes NEW IN 1.4

Internal notes let you and your teammates leave private comments on a ticket that the client never sees. Useful for handoffs, vendor case numbers, behind-the-scenes context, or notes for the QA reviewer.

1. Open the ticket detail page.
2. Scroll to the Internal Notes panel (it sits beside the public Activity Log).
3. Type your note. Basic markdown formatting is supported.
4. Click Post Note. The note appears in the panel immediately, stamped with your name and the time.
5. To remove a note you posted, click the trash icon on it. Administrators can remove any note.

Ticket Merging NEW IN 1.6

When duplicate or closely related tickets arrive, you can merge secondary tickets into a single primary ticket. Merging closes the secondary tickets with a Merged status and preserves all history, internal notes, and KB article links.

1. Open the ticket you want to keep as the primary (surviving) ticket.
2. Click the Merge button in the ticket actions area.
3. In the merge modal, search for tickets to merge into this one. Select one or more tickets using the checkboxes.
4. Click Merge Selected into This Ticket. A confirmation dialog warns that this cannot be undone.
5. After merging, secondary tickets become read-only and display a banner linking back to the primary ticket.

What Happens When Tickets Are Merged

• Secondary tickets receive Merged status and cannot be edited further
• KB article links from secondary tickets are transferred to the primary ticket (duplicates are skipped)
• Internal notes from merged tickets are accessible from the primary ticket’s Merged Tickets section
• The Activity Log on both tickets records the merge action
• Merged tickets are excluded from analytics calculations (resolution time, tech performance)
• No email notifications are sent when tickets are merged — it is an internal housekeeping action

Ticket Linking NEW IN 1.6

Ticket linking creates typed, bidirectional relationships between tickets without closing or modifying either one. Use it to connect related issues, track dependencies, or flag duplicates you want to keep open separately.

1. Open any ticket detail page.
2. Scroll to the Linked Tickets section (below Linked KB Articles).
3. Click Link Ticket. In the modal, search for the ticket to link.
4. Select a link type from the dropdown: Related, Parent/Child, Blocks, or Duplicate.
5. Click the target ticket to create the link.
6. To remove a link, click the X next to it and confirm.

Link Types

Canned Responses NEW IN 1.4

Canned responses are pre-written replies that your administrator has set up for common issues. Insert one with a click instead of typing the same answer over and over.

1. On the ticket detail page, place your cursor in the field you want to add text to — usually Resolution Notes or Troubleshooting Notes.
2. Click the Canned Responses dropdown near that field.
3. Select the response you want. The text is inserted at your cursor position.
4. Edit the inserted text to fit the specific ticket before saving.

Canned responses are maintained by administrators. If a common situation is missing from the list, ask an admin to add it — it helps the whole team.

SLA Indicators

Note: SLA indicators only appear when a Pro license is installed.

Knowledge Base NEW IN 1.5

The knowledge base is a central library of articles documenting solutions, procedures, and reference material. Technicians and administrators author articles; QA reviewers can read and link them to tickets; clients see only articles that have been published and marked public.

Accessing the Knowledge Base

Click Knowledge Base in the left sidebar. The list page shows all articles you have permission to see, with filters for status, visibility, and category, plus a full-text search across titles and bodies.

Article Visibility & Status

Authoring an Article

Admins and technicians can create articles. QA reviewers and clients cannot author articles but can read those they have access to.

1. Open the Knowledge Base and click + New Article.
2. Enter a title. The URL slug is generated automatically from the title.
3. Choose a category (optional — uses the same category tree as tickets).
4. Set status to Draft while you are writing. Switch to Published when ready.
5. Set visibility:
   • Internal for tech-only reference material
   • Public for client-facing how-tos and FAQs (Pro license required)
6. Add comma-separated tags for additional filtering.
7. Write the body in the markdown editor. The editor supports headings, bold, italic, lists, code blocks, tables, links, and a live preview pane.
8. Click Create article. After the first save you can return to the editor to upload attachments.

Attachments

Articles support file attachments for screenshots, diagrams, PDFs, and supporting documents.

• Maximum file size: 25 MB per file
• Allowed types: PNG, JPEG, GIF, WebP, SVG, PDF, plain text, ZIP, and Microsoft Office documents (Word, Excel, PowerPoint)
• Files are stored under C:\Program Files (x86)\ForsetiDesk\kb-attachments\
• Original filenames are preserved for display and download; on-disk names are randomized to prevent collisions

To attach a file: open the article in the editor, click Upload file in the Attachments section, select the file. The upload progress shows briefly and the file appears in the attachments list. Click the X next to an attachment to remove it.

Readers download attachments by clicking them on the article view page.

Linking Articles to Tickets

Tickets and KB articles can be linked in both directions to surface the right reference material at the right time.

1. Open any ticket detail page.
2. Scroll to the Linked KB Articles section.
3. Click Link article, search for the article by title, and click it to attach.
4. The linked article appears on the ticket; the ticket appears under Linked Tickets when viewing the article.
5. Click the X next to a link to remove it.

Search

The search bar matches across article titles and body text. Combine search with category, status, or visibility filters to narrow results. Filters reset to page 1 automatically when changed.

Revision History

Every article maintains an append-only revision log capturing creation, updates, status changes, attachment additions and removals, and archive actions. Each entry records the user, action, and a brief detail string — useful for tracking who changed what and when.

Archiving Articles

Administrators can archive articles by clicking Archive on the article view page. Archived articles are hidden from default listings (apply the Archived status filter to see them) and become inaccessible to clients. Archiving is the recommended way to retire outdated content while preserving its history.

Role Permissions Summary

QA Reviewer Guide

Accessing the QA Queue

Click QA Queue in the left sidebar. This page shows all tickets submitted for review by technicians, displayed in chronological order with oldest submissions first.

Reviewing a Ticket

Before approving or rejecting, review the following on each ticket:

• Ticket description — does it clearly describe the original issue?
• Troubleshooting notes — did the technician document their diagnostic process?
• Resolution notes — is it clear and specific how the issue was resolved?
• Time fields — are start time, end time, and resolution date populated?
• Category — is the ticket properly categorized?
• Tags — are appropriate tags applied?
• Custom field values — are required fields completed?

Approving a Ticket

Click the Approve button on the ticket. You may optionally add approval notes. Once approved, the ticket status changes to Closed and is removed from the active queue.

Rejecting a Ticket

Click the Reject button. Rejection notes are required — you must explain why the ticket is being rejected and what needs to be addressed. The ticket returns to QA Rejected status.

Internal Notes for QA NEW IN 1.4

During review you can post internal notes on the ticket that the client never sees. These are useful for documenting QA observations that don't warrant a rejection, leaving context for the next reviewer, or recording why an exception was approved.

Open the ticket, find the Internal Notes panel beside the activity log, type your note, and click Post Note. Notes are stamped with your name and visible only to Admin, Tech, and QA users.

Administrator Guide

Accessing Admin Settings

Click Admin in the left sidebar. The Admin panel is organized into tabs: Users, Categories, Settings, Communications, Security (TLS/Certificates + LDAP/AD), Database, Automation, Asset Types (Pro), Locations (Pro), Approval Chains (Pro), Service Catalog (Pro/Enterprise). Sub-tabs group related settings within each top-level tab.

User Management

The Users tab allows you to create, edit, deactivate, and delete user accounts. A user count indicator shows current usage against your license limit (e.g., "3 of 10 users").

Creating a User

Click Add User and fill in the name, email address, password (minimum 8 characters), and role. Available roles are Admin, Tech, QA, and Client.

Managing Users

• Edit — modify name, email, role, or password
• Active/Inactive toggle — disable an account without deleting it; deactivated users cannot log in and existing sessions are immediately invalidated
• Delete — permanently remove a user (cannot delete yourself or the last admin)
• Reset Password — generate a temporary password; user must change it on next login

User Audit Log

The Audit Log button shows a complete history of all user management actions. Requires Enterprise license.

Category Management

The Categories tab manages the hierarchical dropdown used when creating tickets. Categories support up to 5 levels on Pro/Enterprise (2 levels on Core). Categories can be reordered and deactivated without deleting historical ticket data.

System Settings

Ticket Numbering Schemes

Email Notifications (SMTP) NEW IN 1.4

The Notifications tab lets you configure outbound email so clients automatically receive updates when their tickets are created, assigned, changed, closed, or rejected. Available on all license tiers.

Configuring SMTP

1. Go to Admin → Notifications.
2. Fill in your SMTP server details: host, port, username, password, from address, and TLS option. Common defaults are port 587 with TLS, or 465 with SSL.
3. Toggle the Enabled switch on.
4. Click Save. The mailer reloads automatically — no service restart needed.

Per-Event Toggles

Below the SMTP settings is a list of notification events. Each one can be turned on or off independently:

• Ticket Created — confirmation email to the client
• Ticket Assigned — notice when a technician picks up the ticket
• Status Changed — updates as the ticket moves through the lifecycle
• QA Approved — closure notification
• QA Rejected — notice that the ticket has been reopened for rework

Send Test Email

Once SMTP is saved, the Send Test Email button at the bottom of the tab lets you verify the connection. Enter any recipient address, click the button, and watch for the test message in that inbox. If it doesn't arrive within a minute, see the Troubleshooting section.

Base URL for Email Links

Notification emails include a clickable link back to the ticket. For these links to work outside your server, set APP_BASE_URL in secrets.cfg to the public URL of your ForsetiDesk install (e.g., https://desk.example.com). Without it, emails will link to localhost, which only works on the server itself.

Security Tab — TLS / Certificate Management NEW IN 1.11.15

The Security tab has three sub-tabs: Session (configurable session timeout and refresh), TLS / Certificates (HTTPS certificate management), and LDAP / AD (Enterprise). TLS enables HTTPS on your ForsetiDesk server so all communication is encrypted.

Certificate Status

The status card shows current TLS state: HTTPS Enabled/Disabled, certificate source (Self-Signed, Let’s Encrypt, or Custom), subject, issuer, expiry date, and SANs. A yellow warning appears 30 days before expiry; red when expired.

Generating a Self-Signed Certificate

1. Click + Generate Certificate → Self-Signed tab.
2. Auto-detected local IP addresses are pre-checked. Uncheck any that should not be included.
3. Add custom entries (domain names, public IPs) in the text field and click + Add.
4. Click Generate Certificate.
5. Enable the Enable HTTPS toggle.
6. Restart the ForsetiDesk service.
7. Distribute the CA certificate to client devices (see Distributing the CA Certificate below).

Requesting a Let’s Encrypt Certificate (Recommended for Public Access)

1. Ensure your domain’s DNS A record points to your server’s public IP address.
2. Ensure port 80 is accessible from the internet (temporarily during issuance; can be closed afterward).
3. Click + Generate Certificate → Let’s Encrypt (Trusted) tab.
4. Enter your fully qualified domain name (e.g., desk.yourcompany.com).
5. Enter your email address — used by Let’s Encrypt for expiry notifications only.
6. Click Request Certificate (takes 30–60 seconds).
7. Enable the Enable HTTPS toggle.
8. Restart the ForsetiDesk service.

Let’s Encrypt certificates are automatically trusted by all modern browsers, mobile devices, and operating systems — no CA distribution needed. Certificates auto-renew 30 days before expiry via a daily background check.

Distributing the CA Certificate (Self-Signed Only)

• Windows: Click Download CA Certificate. Double-click the .pem file → Install Certificate → Local Machine → Trusted Root Certification Authorities.
• Android: Settings → Security → Install certificate → CA certificate. Tap the downloaded file.
• iOS: Open the .pem link on the device → tap “Allow” to install the profile → Settings → General → VPN & Device Management → tap the profile → Install. Then Settings → General → About → Certificate Trust Settings → enable trust for ForsetiDesk CA.
• Mobile App: On the login screen, tap “Download & Install Certificate” to open the CA cert URL in the system browser.

Other Certificate Actions

• Replace Certificate — upload a custom PEM cert + key (and optional CA) from a commercial certificate authority.
• Revoke Certificate — deletes all certificate files; server reverts to HTTP after restart.
• Renew Now (Let’s Encrypt only) — forces immediate renewal before the 30-day auto-renew window.

Push Notification Settings NEW IN 1.11.9

Below the SMTP event toggles, a Push Notifications section lets you control which events trigger mobile app push notifications (Pro license required).

• Ticket Assigned — notify assignee immediately
• Status Changed — notify when ticket status changes
• New Internal Note — notify relevant tech/manager
• SLA Breached — notify assignee and manager
• QA Approved / QA Rejected — notify the submitting tech
• Escalated — notify the receiving manager
• Routed to Team — notify team lead or dispatcher
• Service Request Approval Needed — notify the approver
• Service Request Approved / Rejected — notify the requestor
• Emergency Change Created — notify all admins and managers

Email Inbox (Email-to-Ticket) NEW IN 1.4 — PRO

The Email Inbox tab connects ForsetiDesk to an IMAP mailbox so that messages sent to that address are automatically converted into tickets. This is the standard way most IT teams accept ticket submissions. Requires a Pro license.

Setting Up the Inbox

1. Provision a dedicated mailbox — for example [email protected]. Use a dedicated mailbox, not a personal account.
2. Go to Admin → Email Inbox.
3. Fill in IMAP server details: host, port (typically 993 with TLS, or 143 without), username, password, folder (usually Inbox), and the TLS option.
4. Set the Polling Interval — how often ForsetiDesk checks for new mail. The default is 5 minutes; minimum is 1 minute.
5. Choose a Default Category for tickets created from email. You can re-categorize tickets individually after creation.
6. Toggle Enabled on and click Save.

What Happens to Incoming Mail

On each poll cycle the system fetches unread messages from the configured folder and turns each one into a new ticket using these mappings:

After successful processing the message is marked as read on the mail server so it isn't picked up again. The Message-ID is also recorded internally as a second safety net — the same email cannot create two tickets.

Test Connection & Poll Now

Two buttons sit at the bottom of the tab. Test Connection tries to log into the IMAP server and reports success or the exact error. Poll Now triggers an immediate poll cycle, bypassing the schedule — useful for verifying setup without waiting.

Status Indicator

The tab shows the most recent poll time and a status of ok, error, or idle. If poll status shows error, click Test Connection to see the underlying message.

Canned Responses (Templates Tab) NEW IN 1.4

The Templates tab is where you build and maintain the reply templates (canned responses) that technicians insert into tickets with one click. Available on all license tiers.

Creating a Canned Response

1. Go to Admin → Templates.
2. Click + New Response.
3. Enter a Title — this is what technicians see in the dropdown picker.
4. Enter the Body — the actual text that gets inserted. Markdown formatting is supported.
5. Optionally tie the response to a specific Category so it only appears for matching tickets.
6. Set Sort Order to control where it appears in the dropdown (lower numbers first).
7. Click Save.

Managing the Library

• Edit — modify the title, body, category scope, or sort order at any time.
• Active toggle — temporarily hide a response without deleting it. Inactive responses don't appear in the tech picker but preserve any past usage records.
• Delete — permanently remove a response.

Analytics & Reporting

The Analytics page provides comprehensive visibility into service desk operations. Access it by clicking Analytics in the sidebar. Full analytics features require a Pro license.

Date Range Selection

All analytics are filtered by a date range. Select from preset ranges (Today, This Week, This Month, This Year) or choose a custom start and end date and click Apply.

Key Metrics

Available Charts

• Opened vs Closed — line chart showing daily ticket volume trends
• SLA Compliance by Priority — bar chart showing compliance rate per priority level
• Tech Performance — tickets assigned, resolved, and average resolution/response times per technician
• Top Issue Categories — expandable category tree showing most common issue types
• Repeat Faults by Client — clients with recurring issues in the same category
• MTBF by Category — Mean Time Between Failures for each issue category
• Time by Technician — total and billable hours per technician with switchable Bar, Horizontal Bar, and Pie views (new in 1.9)
• Time by Category — total and billable hours per category with switchable chart types (new in 1.9)

Custom Widgets

Build your own metric cards. Click + Add Widget on the Custom Widgets tab:

Exporting Data

SLA Management

Service Level Agreement (SLA) management tracks commitments to respond to and resolve tickets within defined timeframes. SLA features require a Pro license and must be enabled in Settings.

How SLA Works

When a ticket is created, ForsetiDesk automatically calculates two deadlines based on the ticket's priority and your configured SLA targets:

• Response Deadline — when the ticket must first be acknowledged or assigned
• Resolution Deadline — when the ticket must be fully resolved and submitted for QA

SLA Status Badges

Acknowledging SLA Breaches

Admins and QA reviewers can acknowledge SLA breaches to log that the breach has been noted. Click Acknowledge on the breached ticket in the dashboard alert, optionally add notes. The acknowledgment is logged in the ticket's activity history.

Configuring SLA Targets

Go to Admin → Settings → SLA Targets. Set response and resolution hours for each priority level. Click Save SLA Targets to apply. New tickets created after saving will use the updated targets.

License Management

ForsetiDesk uses a cryptographically signed license key system to unlock Pro and Enterprise features. The Core tier is free with no license required.

Installing a License

1. Go to Admin → License.
2. Click Generate License Request to create a license request file and send it to your vendor.
3. Once you receive your license key, paste it into the License Key field.
4. Click Install License. The system validates the key and immediately unlocks licensed features.

License Information

User Count Enforcement

The Users tab shows your current active user count against the license limit (e.g., "3 of 10 users"). When the limit is reached, new user creation is blocked until the license is upgraded or an existing user is deactivated.

Removing a License

Click Remove License to uninstall the current license. The system reverts to Core mode. Existing data is not affected, but Pro/Enterprise features will no longer be accessible.

30-Day Pro Trial

Fresh ForsetiDesk installations automatically include a 30-day Pro trial. No license key is required — all Pro-tier features are unlocked immediately after setup.

• The trial countdown begins on the date of first installation and cannot be paused or reset.
• A dismissible banner appears in the sidebar showing days remaining. The banner turns amber when fewer than 7 days remain.
• When the trial expires the system reverts to the Core tier (3 seats, 100 tickets). All data is preserved.
• Installing a valid license key at any time — including during or after the trial — immediately activates the purchased edition and hides all trial banners.
• The trial is bound to the machine and installation; reinstalling the application does not restart the trial period.

Export & PowerBI Integration

Data Export

All export options are available from the Analytics page via the Export dropdown. Exports include all ticket data within the selected date range. Export requires a Pro or Enterprise license.

PowerBI Integration

Setting Up the PowerBI Connection

1. Go to Admin → Settings and scroll to PowerBI Integration.
2. Click Generate PowerBI API Key.
3. Copy the full API key — it will not be shown again after you navigate away.
4. In PowerBI Desktop, click Get Data → Web.
5. Enter the connection URL shown on the settings screen.
6. Add the API key as the x-powerbi-key header or apikey query parameter.

API Endpoint Reference

Themes & Customization

ForsetiDesk includes multiple built-in color themes and a fully customizable color editor. Theme settings are accessible via the theme toggle in the app header or at Admin → Settings.

Built-In Themes

Custom Theme

Click any preset theme to load it as your starting point. Use the color pickers to adjust individual UI color variables. Click Apply Custom Theme to activate. Theme preferences are saved per browser session.

Backup & Restore

ForsetiDesk includes built-in database backup and restore functionality using PostgreSQL's native pg_dump and psql tools. Backups are stored as .sql files on the server.

Configuring Backup Storage

Go to Admin → Backup → Configuration. Enter the backup storage path and click Save. The default path is:

Creating a Backup

1. Go to Admin → Backup.
2. Click Create Backup.
3. ForsetiDesk runs pg_dump and saves a timestamped .sql file to the configured backup path.
4. The backup file appears in the backup list with size and creation date.
5. Optionally click Download to save a copy to your local machine.

Restoring from Backup

1. Go to Admin → Backup.
2. Find the backup file you want to restore from the list.
3. Click Restore next to that file and confirm when prompted.
4. ForsetiDesk runs psql to restore the database from the selected .sql file.
5. Restart the ForsetiDesk service after restoration completes.

Automation & Workflow Rules NEW IN 1.7

The automation rules engine lets you define event-driven workflows that execute automatically when ticket conditions are met. Rules eliminate repetitive manual tasks — assigning tickets to the right technician, escalating priority, adding tags, or firing notifications — without human intervention.

Accessing Automation Rules

Go to Admin → Automations. The tab displays all existing rules with their name, trigger event, active status, and sort order. Rules execute in sort-order sequence — lower numbers fire first.

Creating a Rule

1. Click + New Rule.
2. Enter a descriptive Name for the rule (e.g., "Auto-assign network tickets to NetOps").
3. Select a Trigger Event from the dropdown.
4. Add one or more Conditions using the condition builder.
5. Add one or more Actions using the action builder.
6. Set the Sort Order to control execution priority relative to other rules.
7. Toggle Active on or off.
8. Click Save.

Trigger Events

Each rule fires on exactly one event. The available triggers are:

Condition Builder

Conditions filter which tickets a rule applies to. All conditions must be true for the rule to fire (AND logic). Each condition consists of a field, an operator, and a value.

Add multiple conditions by clicking + Add Condition. Remove a condition by clicking the X next to it.

Action Builder

Actions define what happens when the rule fires. Multiple actions can be chained on a single rule.

Add multiple actions by clicking + Add Action. Remove an action by clicking the X next to it.

Managing Rules

• Edit — click a rule to modify its name, trigger, conditions, actions, or sort order
• Active toggle — disable a rule without deleting it; inactive rules do not fire
• Delete — permanently remove a rule
• Sort Order — controls execution sequence; lower numbers execute first

Example Rules

Webhooks NEW IN 1.8

Webhooks let ForsetiDesk push real-time notifications to external systems whenever key ticket events occur. Each webhook sends an HMAC-SHA256 signed HTTP POST request to a URL you configure, enabling integrations with chat platforms, monitoring tools, custom dashboards, and third-party APIs.

Accessing Webhooks

Go to Admin → Webhooks. The tab displays all configured webhooks with their name, URL, active status, and the events they subscribe to.

Creating a Webhook

1. Click + New Webhook.
2. Enter a descriptive Name (e.g., “Slack #helpdesk channel”).
3. Enter the URL that will receive the POST requests.
4. Select one or more Events to subscribe to from the checkbox list.
5. Click Save. A unique signing secret is generated and displayed once — copy it immediately. You will not be able to view it again.

Supported Events

Request Signing

Every webhook request is signed using HMAC-SHA256 with the webhook’s secret. The signature is sent in the X-ForsetiDesk-Signature HTTP header in the format sha256=<hex-digest>. Verify this signature on the receiving end to confirm the request originated from your ForsetiDesk instance and was not tampered with.

Retry Logic

If a webhook delivery fails (non-2xx response or network error), ForsetiDesk retries up to 3 times with increasing delays: immediately, after 30 seconds, and after 5 minutes. All delivery attempts are logged.

Delivery Log

Click any webhook to view its delivery history. Each entry shows the event, timestamp, HTTP status code, success/failure status, number of attempts, and the response body (expandable). Delivery records are automatically cleaned up after 30 days by a daily maintenance job.

Managing Webhooks

• Edit — modify the name, URL, or subscribed events
• Active toggle — temporarily disable a webhook without deleting it
• Regenerate Secret — generate a new signing secret (invalidates the old one immediately)
• Test Ping — send a test payload to verify the endpoint is reachable
• Delete — permanently remove the webhook and all its delivery history

Recurring Tickets NEW IN 1.8

Recurring tickets automate the creation of routine maintenance tickets, scheduled inspections, and periodic review tasks. Define a template once and ForsetiDesk creates tickets automatically on your chosen schedule.

Accessing Recurring Tickets

Go to Admin → Recurring. The tab lists all templates with their name, schedule, next run time, last run time, and enabled status.

Creating a Template

1. Click + New Template.
2. Enter a Name for internal reference (e.g., “Monthly server patching”).
3. Enter the Ticket Title. You can use interpolation variables:
   • {{date}} — current date (YYYY-MM-DD)
   • {{month}} — current month name
   • {{year}} — current year
   • {{day}} — current day of the week
   • {{seq}} — sequential run number
4. Enter a Description for the generated tickets.
5. Set Priority, Category, Assigned To, and Tags as desired.
6. If custom fields are configured, set their values in the template.
7. Choose a Schedule Type:
   • Daily — runs every day at the specified time
   • Weekly — runs on a selected day of the week at the specified time
   • Monthly — runs on a selected day of the month at the specified time
   • CRON — custom cron expression for advanced scheduling
8. Set the Time (24-hour format) for when the ticket should be created.
9. Toggle Enabled on and click Save.

How It Works

A background scheduler runs every 60 seconds. It checks all enabled templates and creates tickets for any where the current time has passed the calculated next run time. After each run, the next run time is recalculated based on the schedule.

At execution time, ForsetiDesk validates that the assigned technician and category are still active. If the assignee is inactive, the ticket is created unassigned. If the category is inactive, it is omitted. Generated tickets trigger automation rules, SMTP notifications, and webhooks just like manually created tickets.

Run Audit Log

Each template maintains a run history showing every execution: timestamp, whether it succeeded or failed, the created ticket ID (clickable link), and any error message. This provides accountability and makes it easy to verify that scheduled tickets are being created on time.

Manual Trigger

Click Run Now on any template to immediately create a ticket from that template, bypassing the schedule. This is useful for testing a new template or triggering an ad-hoc instance.

Managing Templates

• Edit — modify any template field including the schedule
• Enable/Disable toggle — pause a template without deleting it
• Delete — permanently remove the template and its run history

Time Tracking NEW IN 1.9

Time tracking lets technicians record the time they spend on each ticket. Entries can be marked as billable or non-billable, and a persistent global timer makes it easy to track time across navigation without losing your running clock.

Recording Time on a Ticket

Open any ticket detail page and scroll to the Time Tracker section (below Internal Notes). You can add time in two ways:

Manual Entry

1. Enter the time spent in the Minutes field. You can type plain minutes (e.g., 45) or use h:mm format (e.g., 1:30 for 90 minutes).
2. Optionally add Notes describing the work performed.
3. Toggle the Billable checkbox as appropriate (defaults to billable).
4. Click Add Entry.

Live Timer

1. Click the Start Timer button on the ticket’s Time Tracker section.
2. A persistent timer bar appears at the top of the screen showing elapsed time in HH:MM:SS format, along with a clickable link back to the ticket.
3. Navigate freely — the timer survives page changes and continues running.
4. When finished, click Stop on the timer bar. The elapsed time is saved as a new entry on the ticket. Click Cancel to discard the timer without saving.

Summary Bar

Above the time entries list, a summary bar shows the total time, billable time, and non-billable time for the current ticket.

Editing and Deleting Entries

Technicians can edit or delete their own time entries. Administrators can edit or delete any entry. All edits and deletions are recorded in an audit trail that captures the old and new values for changed fields.

Global Time Entries View

Administrators can access a global view of all time entries across all tickets via the Admin panel. This view supports filtering by technician, date range, and billable status, with pagination for large datasets.

Analytics Integration

The Analytics page includes two new charts when time tracking data is available:

• Time by Technician — shows total and billable hours per technician
• Time by Category — shows total and billable hours per ticket category

Both charts support switchable views: Bar chart, Horizontal Bar chart, and Pie chart.

Organizations NEW IN 1.9

Organizations enable MSP-ready multi-tenant support by letting you define client organizations with their own SLA targets, QA policies, default ticket settings, and contact information. Tickets are automatically matched to organizations based on the client’s email domain.

Managing Organizations

Go to Admin → Organizations. The tab lists all organizations with their name, domain, active status, and configured SLA/QA overrides.

Creating an Organization

1. Click + New Organization.
2. Enter the Name (must be unique).
3. Enter the Domain for automatic email matching (e.g., acmecorp.com).
4. Optionally configure Per-Org SLA Targets — response and resolution hours per priority. Leave blank to use the global SLA targets.
5. Set the QA Requirement using the three-state toggle:
   • Use Global — follows the system-wide QA setting
   • Require — always require QA review for this org’s tickets
   • Skip — allow techs to close tickets directly without QA for this org
6. Optionally set Default Priority and Default Category for new tickets from this org.
7. Add Contact details (name, email, phone) and Notes for internal reference.
8. Click Save.

Automatic Organization Matching

When a ticket is created with a client email address, ForsetiDesk extracts the email domain and matches it against configured organizations. If a match is found, the ticket is automatically linked to that organization and its defaults (priority, category, SLA targets, QA policy) are applied.

Global Organization Selector

A dropdown in the header bar (right side, near the user menu) lets you filter the entire application by organization. Selecting an organization scopes the dashboard, ticket list, analytics, and QA queue to show only that organization’s tickets. The default is “All Organizations” and the selection persists across navigation.

SLA & QA Resolution Order

• SLA targets: Organization-specific targets are used when set. Otherwise, the global SLA targets apply as a fallback.
• QA requirement: If the organization has a non-null QA override (Require or Skip), that takes precedence. Otherwise, the global QA setting applies.

Organization on Tickets

• Ticket create/edit: An Organization dropdown appears on the form. It auto-selects based on client email domain match.
• Ticket list: An Organization column is displayed and filterable.
• Ticket detail: An Organization badge appears near the client information.

Deactivating an Organization

Toggle the Active switch off to deactivate an organization. Deactivated organizations stop matching new tickets but existing tickets remain linked and unaffected. This is a soft delete that preserves history.

LDAP / Active Directory SSO NEW IN 1.9

LDAP/Active Directory SSO allows your users to authenticate with their existing corporate directory credentials instead of maintaining separate ForsetiDesk passwords. When enabled, users log in with their AD username and password, and ForsetiDesk verifies them against your LDAP or Active Directory server.

How It Works

When a user logs in and LDAP is enabled, ForsetiDesk performs a bind against your configured LDAP server using the user’s credentials. If the bind succeeds, the user is authenticated. On first login, the user account is auto-provisioned in ForsetiDesk — no manual account creation needed.

Configuring LDAP

Go to Admin → Settings and locate the LDAP/AD SSO configuration section. The following fields must be configured:

Auto-Provisioning

When a user authenticates via LDAP for the first time and no matching ForsetiDesk account exists, a new account is automatically created. The user’s name and email are pulled from the directory. The default role for auto-provisioned users is configurable (typically TECH or CLIENT). Administrators can change the role after provisioning.

Admin Local Auth Fallback

Even when LDAP is enabled, the built-in ADMIN account always falls back to local password authentication. This ensures you can still access ForsetiDesk if the LDAP server is unreachable. Other users must authenticate against the directory when LDAP is active.

Bring Your Own Database NEW IN 1.9

Bring Your Own Database (BYODB) lets you point ForsetiDesk at an external PostgreSQL instance you manage instead of using the bundled local database. This is useful for organizations that want to host ForsetiDesk’s data on a managed database service, a dedicated database server, or an existing PostgreSQL cluster with their own backup and HA strategy.

How It Works

You provide a standard PostgreSQL connection string pointing to your external database. ForsetiDesk connects and automatically creates the required tables and schema using its built-in migration tooling. Your existing data infrastructure handles backups, replication, and availability — ForsetiDesk just needs a valid connection.

Setting Up BYODB

1. Provision a PostgreSQL database on your target server. ForsetiDesk requires PostgreSQL 14 or later (17 recommended).
2. Create a dedicated database and user with full permissions on that database:
   CREATE DATABASE forsetidb; CREATE USER forsetiuser WITH PASSWORD 'your_secure_password'; GRANT ALL PRIVILEGES ON DATABASE forsetidb TO forsetiuser;
3. Ensure the ForsetiDesk server can reach the database host over the network (check firewalls, security groups, and pg_hba.conf).
4. On the ForsetiDesk server, edit secrets.cfg and update the DATABASE_URL:
   DATABASE_URL=postgresql://forsetiuser:your_secure_password@db-host:5432/forsetidb
5. Restart the ForsetiDesk service. On startup, the application detects the external database and automatically creates all required tables.
6. Log in and verify the system is operational. Check Admin → Database to confirm the table list shows correctly.

Important Considerations

• The external database must be reachable from the ForsetiDesk server at all times. If the connection drops, the application will be unavailable until connectivity is restored.
• ForsetiDesk’s built-in backup feature (Admin → Backups) uses pg_dump and requires the PostgreSQL client binaries on the ForsetiDesk server. For remote databases, ensure the connection string credentials have the necessary permissions for pg_dump.
• SSL/TLS connections to the remote database are supported. Append ?sslmode=require to the connection string if your database requires encrypted connections.
• Switching from a local database to BYODB (or vice versa) requires migrating data manually. ForsetiDesk does not provide an automatic migration between database instances.