Repository navigation
System Page Layout
Since 5.3.0 · Related: UI style guide §3 Full width, Help page house style
Every System screen uses one page layout, defined once and checked in a browser. Before this, each page carried its own container and heading rules, and they had drifted:
| Measured at 1600px, before | |
|---|---|
| Left gutter | 20, 24, 28, 32 or 40px - and 416px on Encryption and Docker (an 800px centred column) |
| Page title |
h1 or h2, 22 or 24px, weight 600 or 700, 62-98px from the top |
| Panels and intros | capped at 720-900px on 18 pages |
| Height | 20 pages ran 14px past the bottom of the window (sized as 100vh - 48px; the header is taller than 48px) |
| File | Role |
|---|---|
assets/css/system-page.css |
The layout. .sys-page, .sys-page-head, .sys-title, .sys-subtitle, .sys-actions, .sys-panel, and the desktop height rule |
system/includes/header.php |
Loads it - so every System page has it without its <head> remembering, and after the page's own <style>, so it wins a tie |
tests/system-page-layout.php |
Opens every System screen in headless Chrome and measures it (§4) |
<div class="xx-container sys-page"> <!-- the page's content box -->
<div class="sys-page-head">
<div>
<h1 class="sys-title">Cost Centres</h1>
<p class="sys-subtitle">What this page is for.</p>
</div>
<div class="sys-actions"> <!-- optional: primary buttons, on the right -->
<button class="btn btn-primary">Add</button>
</div>
</div>
<div class="sys-panel"> ... </div> <!-- optional white card -->
</div>- A page keeps its own class on the content box (
.cc-container) as well assys-page, so its own rules for things inside it - and mobile.css's rules for it - still apply. Only width, margin, padding and the title rules move to the shared file. - A back link or breadcrumb stays above
.sys-page-head.
-
Full width, one gutter.
.sys-pageiswidth: 100%; max-width: none; margin: 0; padding: 24px 32px 40px(16px on a phone). - One title. 22px, weight 700 (19px on a phone).
-
No cap of your own.
⚠️ This is the one that keeps coming back: a "tasteful" 760px reading measure on a panel or an intro is still a cap (it bit System → Search, Tickets → Indexing, Forms → Collections and System → Locations). Caps belong only on controls: a search box, a single input or select, a form group holding one input, a table cell, an image, a modal. Anything else that genuinely needs one says so withdata-sys-cap="why"- e.g. the portal mock-up on Self-service, the shared AI settings panel (includes/ai_settings_panel.phpcaps itself at 640px). -
Height. On a desktop, when
.sys-pageis the body's own child, the body becomes a flex column: the header takes its real height and the page fills the rest and scrolls (body:has(> .sys-page)). Pages with another wrapper (a.main-container, a.settings-shell) already did this themselves. Never size a page ascalc(100vh - 48px).
Every System dialog has the app's canonical header / body / footer look (the same as inbox.css's modal), whatever opens it. A page keeps its own overlay, its id and its open/close (.modal.active, .cc-overlay.open, [hidden] ...); the dialog box carries the classes:
<div class="xx-overlay">
<div class="sys-modal [sys-modal-wide|sys-modal-xl]" role="dialog">
<div class="sys-modal-head">Edit cost centre <button class="sys-modal-x">×</button></div>
<div class="sys-modal-body"> fields - this part scrolls </div>
<div class="sys-modal-foot"> Cancel Save </div>
</div>
</div>-
Widths: 520px (default), 820px (
sys-modal-wide, an import preview), 1000px (sys-modal-xl). Nothing in between. -
Look: 8px corners, an 18px / 600 title 24px in, body content at least 24px from the edges, footer buttons on the right 24px in; a note on the left of the footer goes in
.sys-modal-foot-left. -
A
<form>around body + footer gets.sys-modal-form, which makes it a flex column - otherwise the body never scrolls (the inbox.css trap: a plain form between the box and the body has no bounded height). - The new classes go alongside a page's old ones (
class="cc-modal sys-modal"), so JavaScript that looks for the old ones still finds them; only the old CSS for the box, head, body and foot is deleted. - The Locations editor (
assets/js/locations-tree.js) also runs on Assets → Settings, which does not load this file - its dialog carries both the canonicalinbox.cssclasses and these, which describe the same look.
Before this, about 34 dialogs were built eight different ways: titles missing, 16px or 18px, 600 or 700; corners 8 or 10px; padding 18-25px or none (Edit location had its fields flush with the edge); widths from 378 to 1100px.
FREEITSM_TEST_DATABASE=freeitsm_prtest FREEITSM_TEST_URL=http://localhost/freeitsm-prtest php tests/system-page-layout.php
FREEITSM_SPL_ONLY=cost-centres,sso/entra.php ... # just those
It finds the pages itself - every card in getSystemAreas() plus every other system/*/*.php and system/*/*/*.php that includes the System header - so a new page is checked the day it exists. Two levels down since 5.4.0, for the three Microsoft 365 pages in system/integrations/microsoft365/ (PR #352); a folder's own includes/ are parts, not pages, and are skipped (the Debug tools' d0NN/index.php pages do not include the header themselves, so they are not picked up). For each, at 1600px:
- the
.sys-pagefills the width it is given (the parent's inner width, scrollbar excluded); - its gutter is 32px;
- its
.sys-titlesits on the gutter at 22px / 700; - nothing inside is capped (a visible block 400px+ wide held narrower than the page by a
max-width, controls anddata-sys-capexcepted); - the page ends inside the window - no second scrollbar, the bottom reachable;
-
every dialog on the page, opened (animation off) and measured against §3a: a
.sys-modalwith a head and body, 520 / 820 / 1000 wide, 8px corners, the title 18px / 600 at 24px, body content 24px+ from the edges, the last footer button 24px from the right.
Pages that only open for a record get one: three temporary ZZ layout test sign-in providers (LDAP, Entra, CardDAV), removed in finally, and the first tracker in the integrations registry. Each Chrome run has its own profile, so two runs at once do not collide.
Not checked, on purpose ($APP_PAGES, with the reason printed): the Engineering Wiki and the API reference, which are document readers with their own navigation, and the help pages (system/help/, */help.php), which follow the Help page house style.
Use the markup in §2, put no max-width on anything but a control, and run the test with FREEITSM_SPL_ONLY=<your page>. Five passes and it is done.
A new card on the System landing needs a group - see §6. php tests/system-card-groups.php fails until it has one.
(5.3.0, PR #347 by vsc55, #346; review: System cards by topic - PR review.) The landing (system/index.php) shows its cards By topic - a heading over each group - or A-Z, by translated title. Each area in getSystemAreas() (system/includes/areas.php) names its group:
[
'icon' => 'currencies',
'url' => 'currencies/',
'group' => 'organisation', // a key of systemAreaGroups()
'title' => 'system.landing.currencies_title',
...
],systemAreaGroups() lists the groups in the order they are drawn, each with its heading's translation key: start, people, signin, portal, organisation, look, integrations, health, more - and other, the catch-all for an area with no group, drawn last. Within a group the cards keep the registry's own order.
-
The order is applied in the browser. The server prints every card with
data-group,data-index(its place in the registry) anddata-title(its translated title), and the groups as JSON on the grid (data-groups). The script draws a.system-group-headbefore each group, or sorts bydata-titlewithlocaleComparefor A-Z (Help & guides,data-pinned, stays first). The choice is inlocalStorage(system_cards_order). - The search hides a heading whose cards it has all hidden.
- Nothing else changes: the cards, their links and the search haystack are the same in both orders.
The guard. php tests/system-card-groups.php - no database, no config.php - reads the registry and lang/en/system.php and fails when an area names no group, names other, or names a group whose heading has no English text. It also pins two placements decided on merge: Search under health, Currencies under organisation.
When you add a System area, give it a
'group'fromsystemAreaGroups(). A new group needs a key there, its heading inlang/en/system.php(system.landing.group_<key>), and its translations.
(5.4.0, PR #352 by vsc55, #263; review: Microsoft 365 in Integrations.) System is for administrators, with Preferences open to everyone. When Intune moved here from Assets → Settings, the asset managers who set it up there - granted by a capability, not by being an administrator - had to keep it. That is the one exception, and it is one rule:
// system/includes/page_access.php
function systemPageAllowed(PDO $conn, int $analystId, string $page, ?array $grant): bool-
$page === 'preferences'→ allowed. -
analystIsAdmin()(asked of the database, not the session) → allowed. - The page declared a grant, and the analyst has that module (
analystCanAccessModule()) and that capability (analystHasCapability()) → allowed. - Anything else, or anything that throws → refused (fails closed).
Both doors ask it. system/includes/page_gate.php and system/includes/header.php each call systemPageAllowed() with the page's $current_page and $system_page_grant, so the gate and the header can never disagree. Refused → redirected to the app's home.
A page opts in by setting the grant before the includes:
$current_page = 'integrations';
$system_page_grant = ['module' => 'assets', 'cap' => Cap::ASSETS_INTUNE];Today exactly three pages do: system/integrations/microsoft365/index.php (which then shows a non-administrator only its Intune half), intune.php and intune_import.php.
-
The page gate is the screen, not the security. The endpoints behind a granted page must check the capability themselves - the Intune ones (
api/intune/*,api/settings/*) always did. System APIs stayrequireAdminJson(). - Do not grant a page lightly. The point of System being administrators-only is that one check covers it. A new exception needs a reason as good as "these people could already do this, on a page that moved".
-
The capability still lives with its module. The Intune tab stays declared in
asset-management/settings/manifest.phpwith'moved_to' => 'system/integrations/microsoft365/intune.php': the manifest is what lists the capability in System → Roles and owns theintune_*setting keys.settingsMovedTo()andrenderSettingsTabBar()(includes/settings_manifest.php) turn it into a link and redirect?tab=intune;settingsFirstTabId()skips a moved tab.
The test. tests/intune-system-page.php (FREEITSM_TEST_DATABASE, and FREEITSM_TEST_URL for the HTTP part): the manifest entry and its keys, the redirect, each Intune page saving only its own keys, and who may open what - an administrator, an analyst with Assets and the Intune capability, one without the capability, one with it but without Assets, and Preferences. Over HTTP, the Intune-only analyst opens the three Microsoft 365 pages - seeing no Entra ID or Also from Microsoft - and is turned away from every other System page, and with Assets switched off the Intune pages show one line instead of a form.
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