Repository navigation
File Storage Locations Design
Raised by @vsc55 on PR #350 · Status: step 1 under way - progress in File stores - Developer Guide (Ed, 21 Nov 2026) · Related: Storage usage (5.6.0), Files storage
Today every module keeps its files in a fixed folder inside the application. This design lets an administrator choose a different folder for each kind of file - ticket attachments, documents, LMS content and so on - typically outside the web root, for example D:\Data\Ticket attachments. You move one store at a time: FreeITSM tests the new folder, you copy the files across, FreeITSM checks every file is there, then switches. You test, take a breather, and do the next one when you are ready. Nothing moves until you ask, and the old folder stays as your backup.
@vsc55 noticed that the files FreeITSM stores live in about ten folders spread through the application, and each new one has to be remembered in a Docker volume, a web-server guard, the storage list and two debug tools - forms/images and label-fonts had already been missed once. He proposed one data folder outside the web root, one helper that every piece of code asks for a path, and a careful, visible move.
Ed's view (16 Nov 2026): "a scary move and would need to be incredibly careful - hold off". On 21 Nov 2026 he picked it up again with one change: a separate location per store, so a move can be done one module at a time.
Every store except Files has its folder fixed in the code, worked out from the code's own position (dirname(__DIR__) . '/tickets/attachments'), and that is repeated in each file that needs it - 21 files for ticket attachments alone. Files is the exception: its location is already a setting (files_storage_root) with a safe move.
The good news is that most stores record their files in the database relative to their folder, so the folder can change without touching a single row.
| Store | Folder today | What the database holds | Layout inside | How the browser gets a file | Files that build the path |
|---|---|---|---|---|---|
| Ticket attachments | tickets/attachments |
email_attachments.file_path, relative - 12/12345/<hex>.pdf
|
{id/1000}/{email id}/ |
PHP (get_attachment.php, portal, chat media) |
21 |
| Change attachments | change-management/attachments |
change_attachments.file_path, relative - {change id}/<hex>.pdf
|
{change id}/ |
PHP (get_attachment.php, REST) |
5 |
| Documents | uploads/documents |
documents.storage_key, a file name |
flat | PHP (documents/download.php and portal) |
~8 |
| Files |
uploads/files (already a setting) |
files_versions.storage_path, relative - yyyy/mm/dd/<hex>.bin
|
dated | PHP (files/download.php) |
1 setting |
| Knowledge pictures | uploads/knowledge |
knowledge_images.stored_name, a file name |
flat | PHP (knowledge/image.php) |
2 |
| Emailed reports, API log archive, asset imports |
uploads/report-downloads, uploads/api-log-archive, uploads/asset-imports
|
a file name, or none | flat | PHP, or never downloaded | 1 each |
| Screen recordings | recordings |
ticket_recordings.file_path with the folder name in it - recordings/123/<hex>.webm
|
pending/, then {ticket id}/
|
PHP (get_recording.php) |
4 |
| LMS content | lms/content |
lms_courses.launch_url, relative to the course's folder |
{course id}/ + the package's own files |
4 | |
| RFP uploads | contracts/rfp-builder/uploads |
rfp_documents.file_path - C:\wamp64\www\...) |
flat | never downloaded | 4 |
| Branding | system/uploads/branding |
settings and tenants.logo_path with the folder name in it
|
flat + portal/, companies/
|
<img src>, CSS) |
~13 + 1 JS |
| War room | war-room/attachments |
warroom_attachments.stored_name, a file name |
flat | PHP | 1 (a constant) |
| Form pictures | forms/images |
{form id}/<hex>.png, inside a form field's settings |
{form id}/ |
PHP (forms/image.php) |
3 |
| Label fonts | system/uploads/label-fonts |
asset_label_fonts.stored_name, a file name |
flat | PHP (label_font.php) |
2 |
Four lists of these folders are kept in step by hand: storagePersistenceDirectories(), the Storage usage inventory, UPLOAD_HTACCESS_ROOTS and .gitignore - plus the Docker volumes, the nginx config and debug tool D009.
- RFP uploads store a full path in the database. It already breaks if the application folder moves, or between Windows and Docker. It must become relative (a one-off change in Database Verification) before anything else.
- Recordings and branding store the folder name with each file. Either strip it when reading, or rewrite the rows once - both are safe, and the rows keep working for an install that never moves anything.
- LMS content and branding are fetched by the browser straight from the folder. A folder outside the web root cannot be reached that way. Decided: they stay in the application folder for now and are revisited in a later release (serving them through PHP first).
- The war room clears its own folder: any file in it without a database row is deleted. Every store must therefore live in its own folder, never one shared with anything else - the screen enforces this.
-
Small gaps found on the way:
uploads/knowledgeis missing from the Storage usage list, D009 does not probeuploads/report-downloadsoruploads/asset-imports, LMS content has noweb.configfor IIS, and recordings and LMS course folders are never deleted when their ticket or course is.
Three steps, each useful on its own and each safe to stop after.
Every piece of code that saves, reads or deletes a file asks one function where that store lives, instead of building the path itself. In this step the function returns exactly today's folders, so nothing changes on disk, in the database or on screen. It is invisible to users - and it is what makes step 2 safe, because a setting read in 20 places but missed in the 21st would save a file in one place and look for it in another.
- FreeITSM's own store layer, built at its own pace. PR #361 (@cloudcogsio) has a similar layer for putting stores in S3; Ed decided (21 Nov 2026) not to use it, so the migration moves at a pace set here, one store at a time. The helper is one registry of stores - an id, today's folder, and the setting that can override it - with one function to get a store's folder, and it is converted store by store, each conversion its own small change with its own tests.
- The same step fixes the five problems above (relative RFP paths, the folder-name prefixes, the gaps), and replaces the four hand-kept folder lists with the one registry.
- A test fails if any file under
api/,includes/or a module builds a store path by hand, so a new feature cannot quietly add a 22nd.
Each store gets a location on System → Storage:
- In the application folder - today's, and the default. Nothing changes for anyone who never opens this screen.
- A folder on this server - one you choose, per store.
The screen recommends a structure - one parent folder with a subfolder per module, outside the web root:
D:\Data\
Ticket attachments\
Change attachments\
Documents\
Knowledge pictures\
Files\
Form pictures\
...
Inside each folder, the layout stays exactly as it is today (12\12345\... for ticket attachments, 2026\11\21\... for Files). A move copies the contents as they are, so no database row has to change. Reorganising every store by date would mean rewriting every row, for no gain.
A folder path read from the database needs care - it is exactly what a copied database would carry somewhere it does not belong. So:
- Only administrators with the Storage permission can set it, and every change is recorded (who, when, from where to where).
-
It is checked before it is accepted: an absolute path, no
.., the folder exists and FreeITSM can write, read back and delete a test file there; it is not inside another store's folder or the application's code; on Docker, it is on a volume (a folder that is not would be wiped by the next rebuild). A folder the web server would serve to the public is refused for stores fetched through PHP, which is all of them once step 1 is done. - A copied database cannot write into the wrong install's files. When a folder is chosen, FreeITSM leaves a small marker file in it naming this installation and the store. If the database is ever copied - to a test install, a restored backup, a new server - and points at a folder whose marker names a different installation or store, FreeITSM refuses to write there and says why on System → Storage, rather than mixing two installs' files.
- Storage usage shows the chosen folder for every store, so an unexpected location is easy to spot.
On System → Storage, a store's Move walks through:
- Choose the folder. The recommended path is filled in; change it if you like.
- Test. FreeITSM writes, reads back and deletes a test file, and runs the checks above. Nothing is moved and nothing is switched.
-
Copy the files - you do this. Copy the contents of the old folder into the new one, exactly as they are (Explorer,
robocopy,rsync). The screen shows the exact source and destination to copy. Copy, do not move: the old folder stays as it is. FreeITSM does not copy files itself (Ed, 21 Nov 2026) - its job is to verify. - Check. FreeITSM checks every file the database knows about for that store - not a sample - is in the new folder at the right size, and reports "4,812 of 4,812 found", listing any that are missing. Switching is not offered until every file is accounted for (a file already missing from the old folder is listed separately, so a gap that was there before the move cannot block it).
- Switch. From now on new files go to the new folder. Files that arrived while you were copying (mail is fetched every minute) are not lost: until you press Finished, a file not found in the new folder is read from the old one instead.
- Take a breather. Use FreeITSM as normal. Go back returns the store to the old folder in one click, because the old folder is still there.
- Finished. When you are happy, press Finished. FreeITSM checks again first and lists any file still only in the old folder - the ones that arrived during the copy - for you to copy across; Finished is only offered once there are none. From then on it stops looking in the old folder. FreeITSM never deletes the old folder for you; you delete it when you are ready.
Then the next store, whenever you choose.
Easiest and lowest-risk first, so the process is proved on something small:
- Form pictures, label fonts, war room
- Change attachments, documents, knowledge pictures, emailed reports, the API log archive and asset imports
- Screen recordings (after its folder-name fix)
- Ticket attachments - the biggest, and written to every minute by mail
- RFP uploads (after its full-path fix)
- Files keeps its own location setting on Files → Settings → Storage, shown on System → Storage as a row for completeness.
With one volume per store today, moving a store to a different folder inside the container needs that folder on a volume - the Test refuses one that is not. The simplest Docker setup becomes one volume for the recommended parent folder (/app/data) with every store chosen inside it, which is what @vsc55 originally proposed; installs that keep today's folders keep today's volumes.
- Any install that never opens the screen: same folders, same volumes, same everything.
- The layout inside each store's folder, and the database rows (apart from the one-off fixes in step 1).
- The web-server guards on today's folders stay, for every store still using them.
- Branding and LMS content stay in the application folder in this design (revisited in a later release).
- Branding and LMS content stay in the application folder; serving them through PHP so they can move is for a later release.
- S3 for these stores (PR #361) is not part of it.
- FreeITSM copying files itself - the administrator copies, FreeITSM verifies.
| Date | Decision |
|---|---|
| 16 Nov 2026 | Hold off: "a scary move and would need to be incredibly careful" (Ed). |
| 21 Nov 2026 | Go ahead with a design. A separate location per store, so stores can be moved one module at a time: update one, test, take a breather (Ed). |
| 21 Nov 2026 | The System screen recommends a structure (a parent data folder with a subfolder per store); you choose each store's folder yourself rather than one root that moves everything (Ed). |
| 21 Nov 2026 | Each move: FreeITSM tests it can write and read the folder, the files are copied, FreeITSM checks the files are there, then switches (Ed; refined here to check every file and to catch files that arrive during the copy). |
| 21 Nov 2026 | The location is found by one helper in the code; the administrator's choice is a setting it reads, empty meaning today's folder - never a path worked out once and saved, which a copied database would carry to the wrong install. |
| 21 Nov 2026 | Not built on PR #361 - Ed likes the idea but wants the migration handled at FreeITSM's own pace, so step 1 is FreeITSM's own store layer, converted one store at a time (Ed). |
| 21 Nov 2026 | Branding and LMS content stay where they are for now; revisit in another release (Ed). |
| 21 Nov 2026 |
Folders organised by module: today's single uploads/ folder holds several modules' files, so each becomes its own store and folder - Documents, Knowledge pictures, Emailed reports, API log archive, Asset imports. Documents stays one folder, because the same documents are attached across tickets, notes, assets, articles and projects (Ed; Documents noted here). |
| 21 Nov 2026 | The administrator copies the files; FreeITSM verifies - no Copy for me (Ed). |
FreeITSM — an open-source IT Service Management platform · github.com/edmozley/freeitsm · MIT licence
- Installation
- ⏰ Scheduled tasks (cron jobs)
-
Architecture
- ↳ 🧹 Root folder tidy (URL routing)
- ↳ 🔗 Database Integrity (FKs & constraints)
- ↳ 🛠️ Database Verification — Developer Guide
- ↳ 🧩 Service Layer (UI + API share code)
- ↳ 🪤 Code traps (the TRAP: comments)
- ↳ 📝 Commenting for the Engineering wiki
- ↳ 🛠️ Engineering wiki scanner - Developer Guide
- ↳ 📊 Service-Layer progress
- 🤝 Contributing (read before a pull request)
- 🧪 Developer tests
- 📄 PDF exports moved to PDFKit (#254)
- AI Providers
- Internationalisation (i18n)
- Timezones & Time Handling
- 📅 Date & Time Formats
- 💱 Currencies
- 🧭 The sidebar (optional module rail)
- 🧩 Preference templates
- 🔀 Display order (modules, Watchtower cards) — Developer Guide
- Theming & Dark Mode
- 🗂️ Recent — getting back to what you were doing
- ⌨️ Command palette (⌘K)
- 🔍 Searching inside tickets
- 📄 Attached documents
-
Mobile‑Friendly
- ↳ 🎫 Mobile: Tickets
- ↳ 💻 Mobile: Assets
- ↳ 📅 Mobile: Calendar
- ↳ 📚 Mobile: Knowledge
- ↳ 🚦 Mobile: Service Status
- ↳ 🗼 Mobile: Watchtower
- ↳ 🧩 Mobile: Problem Management
- ↳ 🔁 Mobile: Change Management
- ↳ 💿 Mobile: Software
- ↳ ✅ Mobile: Tasks
- ↳ 📝 Mobile: Forms
- ↳ 📄 Mobile: Contracts
- ↳ 📄 Mobile: Domains
- ↳ 📄 Mobile: People
- ↳ 🚀 Mobile: Projects
- ↳ 🗂️ Mobile: Files
- ↳ 🎓 Mobile: LMS
- ↳ 🗺️ Mobile: CMDB
- ↳ 🗺️ Mobile: Network Mapper
- ↳ 🧭 Mobile: Process Mapper
- ↳ ⚙️ Mobile: Workflow
- ↳ 🖥️ Mobile: System
- ↳ 📊 Mobile: Reporting
- ↳ 📖 Mobile: System Wiki
- ↳ 🙋 Mobile: Self-Service Portal
- ↳ 🧰 Mobile: Techniques & Tricks
-
Security
- Layer 1 — which modules you can enter
- ↳ 🧩 Module Access Control
- ↳ 🛠️ Module Access — Developer Guide
- ↳ 🔌 Switching modules off
- ↳ 🛠️ Module availability — Developer Guide
- ↳ 📐 Module availability — design (#217)
- Layer 2 — what you can administer
- ↳ 🎭 Roles & Permissions
- ↳ 🛠️ Roles — Developer Guide
- ↳ 🔤 Why capabilities are constants
- Layer 3 — the System module
- ↳ 🔑 Admin Access Control
- Hardening
- ↳ 📄 Security review response 2026-08
- ↳ 🛡️ Security hardening 2026-08
- ↳ 🛠️ Security hardening 2026-08 — Developer Guide
- ↳ 🛡️ Round three — plain English
- ↳ 🛠️ Round three — Developer Guide
- ↳ 🛡️ CSRF protection (S4) — Developer Guide
- Single Sign-On (SSO)
- 🗂️ LDAP & Active Directory
-
🟦 Microsoft Entra ID
- ↳ 📥 Importing people and groups
- ↳ 💻 Intune: assets to their primary user
- ↳ 🏢 Organisation chart
- ↳ 🛠️ Entra directory sync — Developer Guide
- ↳ 🛠️ Entra import - review (#235)
- ↳ 🛠️ Entra follow-ups - review (#237-#240)
- ↳ 🛠️ Intune primary user - review (#236)
- ↳ 🛠️ Intune after an Entra import - review (#334)
- ↳ 🛠️ Intune primary user history - review (#338)
- ↳ 🛠️ Intune asset types - review (#339)
- ↳ 🛠️ Intune scheduled syncs - review (#344)
- ↳ 🛠️ Microsoft 365 in Integrations - review (#352)
- ↳ 🛠️ Organisation chart - reviews (#242, #265)
- 📇 CardDAV contact sync
- Browser Extension
- API Reference
-
🔌 REST API — how it works
- ↳ 📜 Script library (PowerShell + Python)
- ↳ 📋 Proposal: custom fields, inventory import and change evidence (#194)
- ↳ 🛠️ Custom fields, evidence + inventory - review (#195-#197)
- ↳ 🛠️ Long forms in a task's Work view - review (#198)
- ↳ 🛠️ Empty Procedures fold - review (#247)
- ↳ 🎫 REST API: Tickets
- ↳ 💻 REST API: Assets
- ↳ 🔴 REST API: Problems
- ↳ 🟠 REST API: Changes
- ↳ 📚 REST API: Knowledge
- ↳ ✅ REST API: Tasks
- ↳ 🗄️ REST API: CMDB
- ↳ 📜 REST API: Contracts
- ↳ 🗓️ REST API: Calendar
- ↳ 💿 REST API: Software
- ↳ 🌐 REST API: Domains
- ↳ 🚦 REST API: Service Status
- ↳ ☀️ REST API: Morning Checks
- ↳ 📝 REST API: Forms
- ↳ ⚙️ REST API: Workflow
- ↳ 🏷️ REST API: Cost centres
- ↳ 🏢 REST API: Companies
- ↳ 📒 REST API: Chart of accounts
- ↳ 📁 REST API: Projects
- ↳ 🛡️ API threat protection
- ↳ 🧑💼 REST API: Analysts
- ↳ 🗺️ REST API: Network Mapper
- ↳ 🧭 Using the API docs page
- ↳ 📐 OpenAPI specification
- ↳ ✅ OpenAPI: kept correct
- ↳ 🛠️ Maintaining the catalogue
- Watchtower
-
Tickets
- ↳ Reply subject and replying to one message
- ↳ 🔄 Live updates
- ↳ 🛠️ Watching a ticket - Developer Guide (1 of 2)
- ↳ ✉️ Ticket address suggestions - Developer Guide
- ↳ 🛠️ CSAT delay and reminder - Developer Guide
- ↳ 🛠️ Ticket checklist step types - Developer Guide (1 of 2)
- ↳ 🛠️ Right-click Attach checklist - Developer Guide
- ↳ 🛠️ Checklists in the REST API - Developer Guide
- ↳ 🔗 A ticket's related block and attachments - Developer Guide
- ↳ 🛠️ Inbox.js map — Developer Guide
- ↳ 🛠️ Floating windows & the file viewer — Developer Guide
- ↳ 🛠️ Tickets settings — Developer Guide
- ↳ 📐 Simpler ticket and task forms - design (#218)
- ↳ 🗂️ The ticket workspace
- ↳ 📋 Forms on tickets
- ↳ 📊 The ticket table
- ↳ 📋 Rota copy and paste — Developer Deep Dive
- ↳ ✅ Checklists & SOPs
- ↳ ☑️ Mandatory fields
- ↳ 🧾 Custom ticket fields
- ↳ 🏷️ Ticket categories
- ↳ 🧾 A type for every new ticket
- ↳ 👥 Assigning tickets to a team, and escalation
- ↳ 🏢 One board across every company
- ↳ 🔎 Many companies: searchable lists (#358)
- ↳ 📊 Ticket dashboard — Developer Guide
- ↳ Mailbox Authentication
- ↳ 📤 Email send log
- ↳ ✉️ Emailed reports
- ↳ 📎 Attachment size limits and large emails
-
↳ Basic IMAP mailboxes
- ↳ 📐 Basic IMAP without the PHP extension (#257)
- ↳ 🛠️ Basic IMAP client — Developer Guide
- ↳ 🧪 Basic IMAP client — Testing and verifying
- ↳ 🛠️ Basic IMAP - Sent copy - Developer Guide (#270)
- ↳ 📤 PR #400 Sending through a relay without a login
- ↳ 🛠️ Verifying a mail folder — Developer Guide
- ↳ 🛠️ Mailbox providers — Developer Guide
- ↳ 🛠️ How Gmail mail collection works — Developer Guide
- ↳ Email rendering & images
- ↳ SLA Management
- ↳ WhatsApp channel
-
↳
✈️ Telegram channel - ↳ ⭐ CSAT company scope and filters — Developer Guide
- ↳ 👥 Microsoft Teams channel
- ↳ 🗨️ Mattermost channel
- ↳ 💬 Web chat channel
- ↳ 🟣 Slack channel
- ↳ 🔗 Linking tickets
- ↳ ⓘ Record previews
- ↳ 📝 Ticket notes: internal or shared
- ↳ 🗒️ Canned responses
- ↳ ✉️ Limiting replies to particular senders
- ↳ 📨 Telling the analyst a ticket is theirs
- ↳ ✍️ Email signatures
- ↳ 🌐 The public web address
- ↳ 🔢 Ticket numbering
- ↳ 🙋 Raising a ticket for someone else
- ↳ 🔀 Merging tickets
- ↳ 🔒 Confidential tickets
- ↳ 👥 Portal managers
- ↳ 👁 Who has seen a ticket
- ↳ 📜 Reading long tickets
- ↳ ✨ Reply Cleanup prompt and history
- ↳ ⑂ Splitting tickets
- ↳ ✅ Selecting several tickets
- ↳ 🗂️ The folder pane
- ↳ 🔽 Just my tickets, or no closed ones
- ↳ 🛠️ Snoozing tickets — Developer Guide
- ↳ 👥 Collision detection
- ↳ ⏱️ Time tracking
- ↳ 📄 Case reports - a ticket and its work as one PDF
- ↳ 📅 Scheduled work in your own calendar
- Problem Management
-
Tasks
- ↳ 🛠️ Task ID and hover card - review (#405)
- ↳ 🛠️ Task ID, Company column and hover card — Developer Guide
- ↳ 🛠️ Task board and subtasks — Developer Guide
- ↳ 🧑🤝🧑 People on a task ("Involved")
- ↳ 🔁 Repeating tasks
- ↳ 🏢 Moving a task between companies
- 🚀 Projects
-
Assets
- ↳ 🛠️ Asset list by type - review (#340)
- ↳ 🏢 Moving an asset between companies
- ↳ 📍 Shared asset locations
- ↳ 🧑💼 Assigning assets to analysts
- ↳ 📆 Warranty and lease alerts
- ↳ 📄 Leases
- ↳ 🔭 Saved table views
- ↳ 🖨️ Recording anything, and importing it
- ↳ 🧩 Asset type layouts
- ↳ 🕒 Inventory freshness
- ↳ 🔗 Linked configuration item
- ↳ 🔌 Connected assets
- ↳ 🔍 Asset review
- ↳ 📋 Missing information
- ↳ 📦 Consumables
- ↳ 🏷️ QR asset labels
- ↳ 📋 Who holds what, and handover documents
- ↳ 🖥️ The inventory agent (PowerShell)
- ↳ 🗄️ Proxmox VE servers
- ↳ ☁️ VMware Cloud Director servers
- ↳ 🪟 Hyper-V and Failover Clusters
- ↳ 🔗 Linking equipment to tickets
- ↳ ☑️ Follow-up tasks on a ticket
- Knowledge
- Change Management
- Calendar
- Morning Checks
- Reporting
- Software
-
Forms
- ↳ 🎨 The form designer — Developer Guide
- ↳ 📐 Layout & the grid — Developer Guide
- ↳ 🗂️ Collections — grouping submissions
- ↳ 📄 Submissions as PDFs
- ↳ ⚡ What happens next — a form's own actions
- ↳ 🛠️ Sections & conditional logic — Developer Guide
- ↳ 🛠️ Lookup fields — Developer Guide
- ↳ 🛡️ Catalogue request approvals
- People
- Starters & leavers
- Domains
- 🗂️ Files
- Contracts
- Service Status
- 🔔 Notifications
- 🚨 War Room
-
Self-Service Portal
- ↳ 🎨 Branding the portal
- ↳ 🙋 What people can do
- ↳ 📚 Help Centre
- ↳ 🚪 Landing page
- ↳ 🎨 Login screen designer
- ↳ 🛠️ Back to your page after sign-in - review (#407)
- ↳ 🛠️ Back to your page after sign-in — Developer Guide
- ↳ 🛒 Request catalogue
- ↳ 🔒 Portal privacy
- ↳ 👥 Portal managers
- ↳ 📇 Contact details
- ↳ 🛠️ Developer guide
- LMS
- Process Mapper
-
CMDB
- ↳ 🧱 Designing your CMDB
- ↳ 🛠️ CMDB — Developer Guide
- ↳ 🛠️ Impact analysis — Developer Guide
- ↳ 🛠️ Data quality — Developer Guide
- ↳ 🛠️ Record references — Developer Guide
- ↳ 🛠️ CMDB assistant - Developer Guide
- ↳ 🔗 Linked assets
- ↳ 📐 Linking an asset to its CI - design (#201)
- ↳ 📐 Discovery and redundancy-aware impact - design (#199)
- ↳ 🛠️ Relationship wording - review (#297)
- Network Mapper
-
Workflows
- ↳ 🔀 Branches: If / Otherwise and Choose by value
- ↳ 🛠️ Workflow engine — Developer Guide
- ↳ 🛠️ Workflows for tasks — Developer Guide
- ↳ 🛠️ Workflow notes on a ticket — Developer Guide
- ↳ 🛠️ Workflow category routing — Developer Guide
- ↳ 📐 Workflows in order, child tickets - design (#304)
- ↳ ⏰ Time-Based Triggers
- ↳ 🪝 Webhooks
- ↳ 💬 Webhook Message Formats
- ↳ 🔒 HTTPS Certificates & CA Bundles
- ↳ 🛠️ SSL Verification — the Global Setting
- ↳ 🐞 Workflow & Webhook Pitfalls
- Issue trackers (Jira, Azure DevOps)
- 📡 Zabbix (monitoring)
- 💬 Microsoft Teams alerts
- 📞 3CX (phone system)
-
System
- ↳ 🛠️ System cards by topic - review (#347)
- ↳ 🟦 Microsoft 365 (Entra ID and Intune)
- ↳ 🛠️ Preferences — Developer Guide
- ↳ 🗂️ Settings on one page
- ↳ 🧹 Maintenance
- ↳ 💾 Storage usage
- ↳ ✉️ Emailed reports
- ↳ 🔎 Finding people in the Analysts list
- ↳ 🚪 When an analyst leaves
- ↳ 🛠️ System → Branding — Developer Guide
- ↳ 🩺 Page health (D019) — Developer Guide
- ↳ ⭐ Feature Bingo
- ↳ 📍 Locations
- ↳ 🏷️ Cost centres
- ↳ 📒 Chart of accounts
- ↳ 📷 Photo Album
- ↳ Demo Data
- ↳ 🛠️ Demo Data — Developer Guide
-
Overview
- ↳ 📊 Progress tracker
- ↳ Concepts & vocabulary
- ↳ Email routing & mailboxes
- ↳ Settings: global vs per-company
- ↳ Users & self-service
- ↳ Staff cross-company access
- ↳ One company supporting another
- ↳ 🏢 One board across every company
- ↳ Worked examples
- ↳ Pitfalls & gotchas
- ↳ Scope: what it's for
- ↳ 🛠️ Developer Guide (make a module multi-company)
- ↳ 🗄️ Case study: CMDB (a linked graph)
- ↳ 🧪 Test harness (prove it's isolated)
- What this is
-
🐞 Bugs resolved
- ↳ 📖 #413 Reading pane too narrow on tablets
- ↳ 📱 #412 Sign-in card cramped on phones
- ↳ 🧭 #411 Header buttons out of reach
- ↳ 💱 #386 Project stuck in an old currency
- ↳ 🖥️ #393 Header ran off the screen
- ↳ 🖱️ #395 Ticket flyouts ran off the bottom
- ↳ 🔁 PR #401 Change editor used hardcoded priorities
- ↳ 📝 Knowledge drafts could not be published
- ↳ 🧩 #392 Project dialogs shared element ids
- ↳ 🖼️ #391 Knowledge images from your computer
- ↳ 🕗 #375 REST API wall-clock times
- ↳ 📅 #374 Calendar popup ran off the screen
- ↳ 🏢 #373 All companies: Changes, CMDB, Starters
- ↳ 🏢 #356 Assets People and All companies
- ↳ 🎓 #366 LMS demo data would not import
- ↳ 🔔 #362/#365 Team handover showed only a name
- ↳ 🔔 #365 The bell credited the wrong person
- ↳ 🗄️ #369 Inbox empty until Database Verification
- ↳ 🪆 #360 Links opened inside the ticket
- ↳ 🔗 #354 Workspace Links missed tasks
- ↳ 🔒 Task company checks in the API (5.5.0)
- ↳ 🔒 Asset holders through the API (5.4.0)
- ↳ 🔒 Files folder delete did not check inside (5.4.0)
- ↳ 🔒 The Intune tab did not check the company
- ↳ 📂 #332 Files viewer would not open
- ↳ 📎 #333 Note attachments downloaded
- ↳ 🪝 #326/#327 Form webhook Full record
- ↳ 📄 #325 Form PDF download failed
- ↳ 🔁 Small fixes in 5.1.0
- ↳ 🔁 CMDB relationships read backwards (5.1.0)
- ↳ 🔁 #301 CSAT delay was never applied
- ↳ 🔁 #281 Comments imported from Jira never arrived
- ↳ 🔁 #288 A change failed to open with Enforce approvals on
- ↳ 📚 Long non-Latin articles never got an embedding
- ↳ 🎫 #280 Email lookups scanned the whole table
- ↳ ✅ #266 Dragging a task told nobody
- ↳ 📚 #255 Article previews showed HTML codes
- ↳ 📚 #252 A link to a Knowledge article did not open
- ↳ 📄 #254 PDFs could not print Polish
- ↳ 📚 #250 Clicking a folder left the open article on screen
- ↳ 🎫 #260 The dashboard cog did nothing
- ↳ 🎫 #248 A department rule never matched on four routes
- ↳ 🔒 A directory account could be matched to someone else
- ↳ 🎫 #244 Reply went to the assigned analyst
- ↳ 🔒 Mailbox sign-in was not checked
- ↳ 🔒 Four weaknesses around signing in
- ↳ 🔒 A lookup answer could name any record
- ↳ 🎫 #227 A mailbox could not be deleted
- ↳ 🎫 #226 A picture on a note could not be closed
- ↳ 💻 #222 The Assets page never loaded in 4.3.0
- ↳ ⚙️ #214 A "contains" condition did not match capitals
- ↳ ⚙️ #216 A workflow email from a chosen mailbox always failed
- ↳ 🐳 The Docker image was missing PHP extensions
- ↳ 🌐 A failed DNS lookup read as a missing record
- ↳ 🔒 A link could change data
- ↳ 🔒 Access outlived its removal
- ↳ 🔒 Knowledge articles could run scripts
- ↳ 🔒 Knowledge writes ignored permissions
- ↳ 🔒 Company boundaries (Oct 2026)
- ↳ 🔒 Smaller gaps (Oct 2026)
- ↳ 🔒 Escaped text could leave its attribute
- ↳ 🔒 Task descriptions were not cleaned
- ↳ 🔒 Task documents ignored company scope
- ↳ 🔒 Repeating tasks ignored company scope
- ↳ 📬 #183 Mailbox checks overlapped
- ↳ 🌐 #188 Transfer lock shown off when unknown
- ↳ ✅ #184 Subtask names and Overdue
- ↳ 🧩 #186 Teams: the buttons did nothing
- ↳ 🔒 Text in a change could run script
- ↳ 🔒 AI settings changed without the AI permission
- ↳ 🚪 #178 Deleting an analyst failed
- ↳ 🎫 A team with no departments showed 0 tickets
- ↳ 🚀 Projects: adding a phase did nothing on Save
- ↳ 🔒 Leavers could still sign in
- ↳ 🖼️ Logo and courses broke on Apache with PHP-FPM
- ↳ 🔢 Chat tickets ignored your ticket numbering
- ↳ 📅 Dates shown as a dash, or in server time
- ↳ 🔒 Assets → Users showed people from other companies
- ↳ 🔒 Restricted analysts could read other modules' data
- ↳ 🖼️ Replies with a picture in the thread failed to send
- ↳ 📎 Reply attachments never reached the customer
- ↳ 🛠️ Outbound email attachments — Developer Guide
- ↳ 🔑 A global SSO provider was missing from the portal
- ↳ 🔀 Behind a proxy, the SSO redirect said http
- ↳ ✏️ The portal tagline moved when you saved it
- ↳ 🎨 The portal settings screen forgot what you saved
- ↳ 🛡️ The approvals inbox said "Error" and nothing else
- ↳ 📄 A table's answers were missing from the PDF
- ↳ ◉ A single-select column let you tick every option
- ↳ 📐 The portal ignored a form's field widths
- ↳ 📋 The tasks board stopped taking clicks
- ↳ 🗂️ #121 The index list is out of date after upgrading
- ↳ 📅 #133 The calendar subscription was empty
- ↳ 📋 #131 Tasks always reopened on the board
- ↳ 💥 #129 Every page returned HTTP 500 after upgrading
- ↳ 🐳 #127 A PHP warning above the System page
- ↳ 🕐 #126 Notes stamped with the server's clock
- ↳ 🌍 Storing every date in UTC
- ↳ 🚪 The portal was down for everyone signed in
- ↳ ⚙️ #120 Workflow notes could never be written
- ↳ ⚙️ #123 Three errors when running Database Verification
- ↳ 📝 #122 The description box was a stub in the corner
- ↳ 💣 Demo data deleted real accounts
- ↳ 🔐 #117 Sign-in redirected to the wrong address
- ↳ 🎨 #108 The priority dot was invisible
- ↳ ⏱️ #116 Time logged from the right-click menu
- ↳ 🔑 #114 API keys refused by our own guard
- ↳ 🗂️ #110 Assigning a task told nobody
- ↳ 🚪 #107 Signed out while still working
- ↳ 📎 #103 "Share with Requester" reached nobody
- ↳ 🔍 #102 Search found nothing for hyphens
- ↳ 🪟 #101 Source code editor opened behind
- ↳ ☑️ #88 Subtasks could not be ticked off
- ↳ 💻 #84 Asset deep link selected nothing
- ↳ 🎫 #79 A new ticket arrived with no status
- ↳ 📧 #79 A ticket from email did not say so
- ↳ 🔔 #78 Bell opened to nothing
- ↳ 📬 #77 Mail only collected from Inbox
- ↳ 🔐 #74 The default password could not be changed
- ↳ 🚦 #70 Renaming an impact level
- ↳ 📤 #67 App-only mailboxes could not send
- ↳ 📭 #45 Verify only ever worked for Microsoft
- ↳ 📭 #45 IMAP reported as not authenticated
- ↳ ✉️ An email template stopped escaping itself
- ↳ 🕐 The portal dashboard showed the wrong time
- ↳ 🔢 The folder said 99 and the list showed 96