Repository navigation
[26.12]
Upgrading to 26.12
Update from Maintenance > Update — Queue Update hands the job to cron, which updates the files and applies this release's forty-four database changes (3.6.6 to 4.1.1) in the same pass. They add four tables for RMM providers and their alerts, a setting for API keys in the address, a column marking the emails the mail queue clears once sent, a column and a table for agent banners, two columns for ticket statuses with a setting for the "ticket assigned" message, a column on tickets with a setting for the "no response" message, a table for who a ticket's email replies go to, the settings for Quick tickets, columns on recurring tickets and recurring invoices for booking and making them ahead, two columns on ticket replies for when their time was worked, the settings for cron alerts, a table and a setting for labor costs, a column on users for API / service accounts, columns on tickets and recurring tickets for how long booked work takes, a column each on recurring tickets and calendar events for repeating on a weekday, three columns on agents' settings for their calendar color, what their calendar shows and their own time zone, a table for the agents helping on a ticket, three columns on quote lines with three settings for what a quote line costs and how it is priced, a column each on quote lines and products with a setting for their pictures, two settings and a column on tickets for keeping project tickets apart, a table for your other offices with a column each on agents and invites for which one they work from, three settings for the emails and notices your agents get about their tickets, three settings for sending and reading Microsoft 365 mail through Microsoft Graph, five tables, four settings and a role permission for purchase orders, five settings for switching Dispatch, Bookkeeping, Purchasing, Trips and the calendar on and off, and eight tables, three columns and two settings for the Knowledge Base, who can read its articles, what its readers think of them and their files, a column on documents for how often each is reviewed, a column on agents' settings for compact rows, a table for reply drafts, a table for which tickets each agent has opened, two columns on contacts for an email that bounces, a table for credentials' earlier passwords, a column on recurring invoices for a pause with an end, a column on calendar events, two columns on agents' settings and a table for reminders, four settings for the weekly summary, a table for related tickets, a setting for the first technician to reply to a ticket nobody is assigned to being assigned it, and two tables for your own asset types and their details. They change nothing that is there, except that audit log entries filed as Software, Software Template, Revenue and Account Transfer are renamed License, License Template, Income and Transfer. Nothing else is required, but it is a big release, so take a backup before you update. Purchasing starts off - switch it on in Admin > Settings > Modules - and so does the Knowledge Base's public help center, in Admin > Settings > Knowledge Base. This release has thirteen security fixes - see Security. On Apache, ITFlow's own .htaccess now sends security headers: if you show ITFlow inside a frame on another website, it will now refuse to load there. On nginx, add the same headers to your server block if you want them - see Developer Updates.
Security
-
API: send your API key in the
X-API-Keyheader. A key put in the address (?api_key=) was written to your web server's access log with every call, and to a proxy's in front of it - a header isn't. The address and a JSON body still work, so nothing that uses the API breaks, but move your scripts and integrations to the header, then give each one that sent its key in the address a new key and revoke the old one, as the old logs still have it. The API docs now send the key in the header throughout, and the New API Key window says where it goes. Admin > API Keys flags each key sent in the address in the last 30 days, and Admin > Settings > Security has Take API keys in the address - on if your ITFlow had API keys that still worked, so nothing stops when you update, and off on a new ITFlow. Once the flags have gone, turn it off, and a key in the address is turned away from then on. -
Credentials: a login saved with a piece of web page code as its username or password could run that code in the browser of an agent who followed a link made for the purpose. The address ITFlow's own pages use to fetch a login's username and password answered as a web page, so a browser sent straight to it drew what the login held instead of showing it as text - and the code then acted as that agent. It took someone able to get such a login saved - an agent who can edit credentials, or a person sent an Ask for a login link, once an agent had saved what they sent back - and then an agent with access to that login opening the link while signed in. The pages that list and show logins were never affected. That answer now says it is data, which no browser draws as a page, and so do sixteen like it that carried only text ITFlow had already made safe. Releases from 26.10 to 26.11.8 are affected, and there is nothing to do after updating.
-
Invites: with a login key required, the page behind an agent's invite link went on showing the sign-in address with the key in it after the invite had been cancelled or had run out. Someone whose invite was withdrawn could still read the key from their old link. The key signs no one in by itself - it only opens the agents' sign-in page, which still asks for an email and password. A cancelled or run-out link now leads to the plain sign-in page. Releases from 26.11 to 26.11.8 are affected. If you cancelled an invite because the person should never have had it, change the login key in Admin > Settings > Security.
-
Client access: an agent limited to some clients could read a few names belonging to the others, by putting a record's number in a page's address - a project's name on the tickets list, a site's name, a ticket's subject and an invoice's number on Trips and its export window, a vendor's name in the domains export window, and a client's name on Update Prices and in the message when an AI request was turned away. Nothing else of those records showed, and nothing could be changed. These names now show only for clients the agent can open. Releases from 26.09 to 26.11.8 are affected.
-
Tickets: a ticket moved to another client kept its link, so the old client's contact could go on opening it from an email they had - its details, its status and the new client's replies from then on - and a task approval emailed to them still opened, with the ticket's details. Moving a ticket now gives it a new link, and its tasks' approvals new ones, so those the old client was sent stop working; the new client gets the new link with the next email. The Change Client window says so. Every release before 26.12 is affected, and there is nothing to do after updating.
-
Tickets: a link in an email or a client portal reply could be written so that an agent who clicked it on the ticket opened a page from another website inside ITFlow, where it ran as that agent - able to do anything they could, such as reading the logins they have access to. It took someone sending such a message and an agent clicking its link. Links in tickets, and in documents, now open as ordinary links, and ITFlow's windows only ever load ITFlow's own pages. On an ITFlow without HTTPS, the key that unlocks a signed-in agent's saved logins is also kept out of reach of the page, as it already was with HTTPS. Releases from 25.12 to 26.11.8 are affected, and there is nothing to do after updating. Found by Mountaineer IT.
-
Client portal: turning the portal off, or archiving a client or a contact, now ends the portal sessions they already have - before, someone signed in stayed signed in until they signed out. Signing in with Microsoft 365 is refused while the portal is off or the contact is archived, as signing in with a password already was. Found by Mountaineer IT.
-
Ticket emails: anyone can put a ticket's number in a subject, and an email from someone who isn't the client's contact, a watcher or one of your agents reopened the ticket and added its attachments. It is now kept as an internal note marked as from a stranger: the ticket stays as it is, the attachments stay in the mailbox's ITFlow folder, and the assigned agent's email shows it as plain text. An email from one of your agents - answering an email about the ticket - is added as their internal note and reopens nothing. Found by Mountaineer IT.
-
Two-step sign-in: setting up an authenticator while one was already on replaced it without asking for the password - so anyone with a signed-in browser could swap it for their own and lock the owner out. It now has to be turned off first, which asks for the password. Found by Mountaineer IT.
-
Uploads: a file opened straight from ITFlow's uploads folder - an HTML or SVG file someone uploaded, say - could run scripts as ITFlow. Files there are now never run, and every page says not to guess a file's type, not to send its address to other sites, and not to be shown inside another site's frame. These are Apache settings; on nginx add them yourself. Found by Mountaineer IT.
-
Client portal: saving a card now only finishes the card setup the contact started, for their own client's Stripe customer. Found by Mountaineer IT.
-
Clients and contacts: Send Email to several clients or contacts needs Modify on clients, not View, and is no longer offered to agents who can only view. Found by Mountaineer IT.
-
Ticket email: with a mailbox set to TLS encryption (usually port 143), if the encrypted connection couldn't be set up - the server's certificate failed the check, say, or something on the network got in the way - ITFlow went on and signed in to the mailbox without encryption, sending its password as plain text. It now stops and says the encrypted connection failed. This came with the update to the library ITFlow reads mailboxes with, which also refuses message numbers and flags that carry extra mail server commands - ITFlow only ever sends its own, so that part is a precaution.
New Features & Updates
-
RMM Providers: Admin > Integrations > RMM Providers brings in devices from your RMM - Tactical RMM is the first it knows. Add it with its API address and an API key, then on its Clients page link its clients to yours: a client with the same name is suggested, one click links it, and Link the suggested does them all. A linked client's devices come in as its assets straight away, then every 15 minutes or with Sync now. A device is matched to the asset you already have for it - same serial number, or the only asset with its name - and only what that asset is missing is filled in. Otherwise a new asset is made: its name, type (laptop, desktop, server or virtual machine), make and model, serial number, OS, IP, CPU and storage, at the location named like its site in the RMM.
-
RMM Providers: more than one can be set up - two Tactical servers, say, each with a name of its own. A device both have is matched to the same asset, which shows what each says.
-
RMM Providers: what the RMM says about a device keeps its asset up to date, field by field - until you change that field in ITFlow, which then stays as you set it. A blank from the RMM never clears anything.
-
RMM Providers: an asset from an RMM shows whether the device is online, offline or overdue, beside its status. It also gets a card named after its provider: when it was last seen, who is signed in, its public IP and site, and whether it needs a reboot, has patches waiting or has checks failing. For Tactical RMM, Take Control opens its remote session, and its menu has Open in Tactical RMM and Remote Background. The quick look has the state and Take Control too.
-
RMM Providers: on the assets list, a dot after a device's name says how it is, and the RMM filter - named after your provider when you have one - shows the online, offline or overdue ones, every device in it, or the assets that aren't in it.
-
RMM Providers: a device the RMM no longer has keeps its asset, marked as no longer in it. If you delete an asset in ITFlow, the next sync doesn't make it again - Bring back on the client's row does. A client linked to another of your clients brings its devices in there. The assets already made for the first client stay, no longer kept up. Each change is in the asset's history.
-
RMM Providers: alerts can open tickets. In a provider's Edit, pick which - errors, errors and warnings, or every alert - and the category their tickets go in. A new alert on a device of a linked client opens a ticket on its client and asset within a minute: High for an error, Medium for a warning, Low for the rest, with what the alert says and a link to the device in the RMM. The same alert again on the same device goes on that ticket while it is open, reopening it if it was resolved, so a check that keeps failing doesn't fill the queue.
-
RMM Providers: when an alert clears, its ticket gets a note and is resolved - unless someone has written on it, it is in a status someone moved it to, or another of its alerts is still open. Then it gets the note and stays as it is. Alerts already open when you turn this on, or when you link a client, don't open tickets.
-
RMM Providers: for Tactical RMM, the alerts are the ones its dashboard shows - a check's or agent's Dashboard alert setting, or its alert template, decides which those are. Nothing needs setting up in Tactical, but the API key's user has to be able to list alerts. A device's open alerts and their tickets show on its card on the asset, and the providers list says which alerts open tickets, how many are open and whether the last look worked.
-
RMM Providers: bill per managed device. A recurring invoice line's Quantity from has Managed devices - the client's devices your RMM has - beside Users and Devices. Like Devices it can count only some types, Desktop and Laptop for a managed workstation, Server and Virtual Machine for a managed server, or only those with a tag. With more than one RMM it can count one of them. A device the RMM no longer has stops counting at the next invoice, and lost, stolen or retired ones never count.
-
RMM Providers: a product can be counted Per managed device, so it bills that way on any recurring invoice it is added to - in the product window, and as Per managed device in a product import.
-
RMM Providers: if the RMM provider a line counted is deleted, the line stays at the quantity it last billed, marked RMM provider gone, until another is picked. Deleting a provider says how many lines bill its devices.
-
RMM Providers: the RMM Sync job is on Maintenance > Cron, and so is RMM Alerts, every minute. Turning a provider off stops its syncs, and Delete forgets its links - the assets stay as they are either way. API keys are kept like other providers' keys and never shown again. A Tactical RMM key can do whatever its Tactical user can, so make it for a user whose role can see clients and agents, and do the device actions you turn on, and no more.
-
API: invoices can be made with their lines, changed, emailed, marked sent, cancelled and deleted, and their lines changed or taken off. Emailing one sends it to the client's primary and billing contacts, or the contacts you name, with its link to view and pay - or a reminder of what is still owed.
-
API: quotes can be made with their lines - billed once, or each month, quarter or year - changed, emailed, marked sent, accepted or declined, and deleted. An accepted quote can be invoiced as Invoice does on its page: its one-time lines on a new invoice, the rest on recurring invoices. A quote's lines can be read, added, changed and taken off.
-
API: recurring invoices can be changed, paused or resumed, and deleted, and their lines read, added, changed and taken off - a line can count its quantity from the client's users or devices, as in the line window.
-
API: expenses can be recorded, refunded, changed and deleted, with the same checks as the expense window. Services can be made, changed, archived and deleted, licenses made, changed and deleted, certificates changed, archived and deleted, and products made, archived and deleted.
-
API: tickets can be reopened and deleted, and replies edited and archived. Assets can be archived and unarchived, and documents, domains, networks and vendors deleted. Documents, domains, networks and vendors are archived before the API deletes them, as clients and contacts are, and a closed ticket is kept, not deleted. Deleting needs Full access. An admin's key can delete tags. A client's waiting portal invites can be listed and cancelled.
-
API: payments can be read, recorded on an invoice that is sent and still owed on - no more than is owed, into one of your accounts, with the client's receipt emailed - changed, deleted, and their receipt sent again, with the same checks as the payment window. A payment cleared on a reconciled statement keeps its date, amount and account. Payments need Financial, with Read on Sales. Card payments are still charged and refunded in ITFlow.
-
API: projects can be read - one with its tickets and its progress and time - started for a client or as internal work, with a project template's tickets, changed, completed once none of its tickets is open, reopened, archived, unarchived and deleted once archived. A template's tickets can be added to an open project. A ticket goes on or off a project with tickets/create and tickets/update.
-
API: a ticket's tasks can be read, added, changed, marked done or not done, and deleted, and an approval can be asked of the client or your team, given by the key's agent, and taken off. A task waiting on an approval, or whose approval was declined, can't be marked done.
-
API: recurring tickets can be read, made - from a ticket template, with its fill-ins answered and its tasks for those answers - changed, paused and resumed, raised now and deleted.
-
API: a network's documented IP addresses can be read, added - one at a time or a run of up to 256 - changed and deleted, with the same checks as the address plan: inside the subnet, not documented twice, and a DHCP reservation with its MAC.
-
API: an asset's interfaces can be read - with what each is plugged into - added, changed, made the primary, plugged in or unplugged, and deleted, with the same checks as the interface window.
-
API: a license's keys can be read, added, handed to the client's devices and users, and deleted, its seats can be set, and it can be renewed by a term or to a date. Reading licenses by software_key finds a license by any of its keys.
-
API: asset and contact notes can be read, added with one of your note types, archived, unarchived and deleted once archived.
-
API: racks can be read - one with what is mounted in it - made, changed, archived, unarchived and deleted once archived, and items mounted, moved and taken out, with the same checks as the rack page: an asset in one rack at a time, nothing else on that face, and a rack no shorter than what is in it. Rack photos are still added in ITFlow.
-
API: calendar events can be read - one with who is on it - put on a calendar for a client or nobody, once or repeating, changed, sent as invitations, skipped for a day of a series and deleted, with the calendar's rules: an event of no client is anyone's, a client's follows the Clients role. The calendars can be read.
-
API: trips can be read, logged, changed and deleted - anyone their own, someone else's with Financial - with the same checks as the trip window. One paid back for or billed is kept as it was.
-
API: accounts can be read with their balances, added, changed, archived, unarchived and deleted while nothing is on them; other income and transfers between accounts can be read, recorded, changed and deleted; recurring expenses can be read, set up, changed, paused and resumed, recorded now, moved on past missed runs and deleted. A line cleared on a reconciled statement keeps its date, amount and account.
-
API: contracts can be read - one with its prepaid hours and where its signing stands - added, changed, made active, renewed, cancelled and deleted, sent for signature or sent the link again, and the request withdrawn. Prepaid hours can be added, with a draft invoice for them, and deleted, done tickets' time drawn on them and a ticket's hours put back, and the recurring invoice that bills a contract made, linked or unlinked. Countersigning and contract PDFs stay in ITFlow.
-
API: a client's files can be read, uploaded, downloaded, renamed, moved, archived, unarchived and deleted once archived, and its folders read, made, renamed, moved and deleted - what is in a deleted folder moves up. An upload comes base64 in the request, so the server's upload size caps it.
-
Contracts: an hourly or after-hours rate of 0 is now a rate of nothing - time it covers bills at no charge - where 0 used to be taken as empty, so the default rate applied. Leave a rate empty for the default, as before. A plan that covers business-hours time and bills after hours, say, is a contract with an hourly rate of 0 and an after-hours rate. Unbilled Time and its reports show such a contract's tickets at its rate, not as having no rate, and the client's terms show the after-hours rate even when it is 0.
-
Imports: one Import window for clients, contacts, locations, credentials, networks, assets and products. Choose a CSV file and it lists the file's columns with a few of each one's values and what it imports as, matched by its heading in any order - change any of them, or set one to Don't import. Before anything goes in it shows what every row will do: be added, update one already here, be skipped, or not import and why. When it's done, the rows that didn't import download as a file with the reason in a last column, to fix and import again.
-
Imports: a record already here can be skipped or updated with the file's values - an empty cell leaves what it has - so a list can be exported, changed in a spreadsheet and imported back. Contacts are found by their email, else their name; products by their code, else their name; networks by their name and subnet; the rest by their name. A row for the same record as a row above it is skipped, and an archived record is never changed.
-
Imports: every list takes everything its export has, so an exported file imports as it is. A file separated by semicolons works too, files made from the old templates still import, and long notes are no longer cut off. Each list's Template has every heading and an example row.
-
Imports: clients take Lead, Tax Rate (one of your tax rates, by name), Tax Exempt with its certificate and expiry, Tags and Notes, besides what they took before. A phone number written with + and its country code keeps its country code. A client with no location or contact in the file no longer gets an empty one. Updating a client changes its primary location and contact; its rate and terms stay on its contract.
-
Imports: assets take Status, Primary IP (or DHCP), Primary MAC, Network, Link, Second Link and Client Link, Vendor, Order Reference, Install Date, Warranty Expire, Tags and any of their details, besides what they took before. Assigned To, Location, Vendor and Network are the client's own, by name - Assigned To by email too. A virtual machine's Host can be further down the same file.
-
Imports: contacts take Primary, Important, Billing, Technical, Tags and Notes, and keep a phone's country code; locations take Country, On-site Contact, Primary, Tags and Notes; credentials take URI 2, Favorite, Asset, Contact, Tags and Notes; networks take Site, Provider, Tags and Notes. A credential whose 2FA secret isn't one is not imported, rather than imported without its 2FA.
-
Imports: vendors, domains, certificates, licenses and services import too, from Import under the arrow beside each list's New button. Vendors go to the client whose vendors it's opened from, or are your own when it's opened from your vendors. A new domain is looked up, and a certificate with a host is checked, on its refresher's next run. A license's Assets and Contacts give it seats, and a service's Runs On, Vendors, People and Domains link it to them - by name, added to what it has. A license Type that isn't a software type yet is added.
-
Pictures: your picture, a user's and a contact's, and the photos of assets, locations and racks, show on their form as the picture itself with a camera on it - the person's initials, or a camera, when there isn't one. Click it to open the Picture window: drop, paste or choose a picture, crop it to fit the shape it's shown in - a circle for a person - by dragging and zooming, turn it a quarter at a time, and Use this picture, or Remove the one there is. Photos of assets, locations and racks can also be square, 4:3, 3:4 or the whole photo. What's kept is what's in the frame, at up to 512 pixels across for a person and 2048 for a photo, so a big phone photo goes in at a sensible size, the right way up, without its location or camera details. A person's initials follow their name as it's typed.
-
Receipts and logos open in the Picture window too: an expense's receipt (on its form, and on its quick look, where it's saved as soon as it's used) and your company's logo (Admin > Settings > Company details, and the setup wizard, where your own picture works the same way). They have no set shape - drag the frame's corners and edges in to just the receipt or logo. Trim the edges cuts the empty or plain-coloured space round a logo, and a PNG logo keeps its see-through background. A receipt can still be a PDF, which goes in as it is. A receipt is kept at up to 2400 pixels, so it stays readable, and a logo at up to 1200.
-
Mail queue: a sent email keeps what it said, its attachments and its calendar file, so you can open it in Admin > Mail Queue and see exactly what went - until it's deleted after 90 days, as before. Until now every email was cleared as it was sent. An email with a link or code that opens something - a shared login and its code, a client portal or agent invite, a password link, a contract to sign or a task to approve - is still cleared once it's sent, and a day after it was queued if it failed or was cancelled. One cleared like that can't be retried: send a new one from where it came from. Emails sent before this update stay cleared.
-
Mail: Microsoft 365 can send email and read your support mailbox through Microsoft Graph instead of SMTP and IMAP, so the mailbox doesn't need SMTP AUTH, which Microsoft switches off by default. In Microsoft Entra, give the app on the OAuth tab Microsoft Graph's Mail.Send and Mail.ReadWrite permissions - with Mail.Send.Shared and Mail.ReadWrite.Shared for a shared mailbox - and grant admin consent. ITFlow then uses Graph for whichever it has permission for, and SMTP or IMAP for the rest, with nothing to switch on. The OAuth tab says which way email goes, and on Tests, Test IMAP checks the mailbox through Graph and Test OAuth Token Refresh says what Graph can do. An email too big to send in one go - big attachments - is sent in parts. From Mountaineer IT's build of ITFlow.
-
Dashboard: Cash flow runs January to December - of this year, or of the year picked at the top right - with what's expected for the months still to come. It showed the last 12 months and the next 3.
-
Reports: Geography shows where your clients and their locations are, on a map. It opens on your own country, shaded by how many clients - or locations - are in each place: the US state by state, Canada province by province, and any other country as a chart of its regions. All countries shows the world map. Click a state, or pick it at the top, to list its cities and every location in it, and a city for its locations. Incomplete addresses counts the locations it couldn't place - no city, or a country, state or province it doesn't recognise - and a location with no country counts in yours. Leads can be included, and each table prints and exports. The maps are part of ITFlow, so nothing is sent anywhere to draw them.
-
Reports: every report exports as a PDF that looks like the page - Export > PDF. It has the dark bar with the report's name and dates, your company and who printed it, the figures along the top, and each section as you see it: the charts and the map, the tables with their colours, badges and bold, and the notes under them. Tables come out with all their rows rather than the first few. Client Review makes a PDF to hand a client at a business review. The PDF is in the light colours of paper even when you use dark mode, on Letter paper in the US and Canada and A4 elsewhere, and on its side when a table is wide. Export still has each table as a CSV.
-
Reports: Tax Package, under Finance, gathers what your accountant asks for at year end for one tax year - profit and loss by category a quarter at a time, the sales tax charged at each rate on payments received and on invoices sent, each account's balance at the start and end of the year, the invoices unpaid at year end, for a US company the vendors paid enough to need a 1099 (with what was paid by card apart), the mileage, and the expenses with no receipt. The year starts in January, or in the month you pick - April in the UK, New Zealand and India, July in Australia and March in South Africa to start with. Download package makes one ZIP: the page as a PDF, each table as a CSV, every payment, expense, invoice and trip of the year as spreadsheets that add up to the summary, and every expense's receipt, named by date, vendor and amount.
-
Tickets: checking off a task, or marking it not done, no longer reloads the page and sends you back to the top - the list, the count and the Resolve button update where you are, so you can work down a long list. The "Completed Task" note shows in the conversation the next time the page loads.
-
Banners: a note your team sees along the top of their pages - for one client, such as "On credit hold - no work without approval", or for every client. A client's shows on its pages, and on its tickets, invoices, quotes, recurring invoices and projects however they're opened. Anyone who can edit a client adds one from New Banner in the client's ⋮ menu, which lists its banners below to change, archive or delete. Admins add them for every client, and see them all, in Admin > Agent Banners. Each is a Notice, Heads up or Urgent, and shows between its start and end like a portal announcement. Anyone can hide a Notice or Heads up until it's changed; an Urgent one is big and red, first on the page, and can't be hidden. Clients never see banners.
-
New Ticket: pick the Status a ticket starts in, and book the work as you make it - a date and time, remote or onsite, under Schedule. The booking goes out as it does from the ticket's Schedule window: the assigned agent, the contact and the watchers are emailed the time with a calendar invite, and it is noted on the ticket. Left as it is, a ticket still starts as New, or Open once it is assigned. From Mountaineer IT's build of ITFlow.
-
Ticket Statuses: When the client replies can move a ticket to another status - a "Client responded" status, say, so the tickets with a new answer from the client stand out. It can be set on New, Open, On Hold and Resolved as well as your own statuses, for replies by email, in the portal or by text; back to Open is still the default. From Mountaineer IT's build of ITFlow.
-
Ticket Statuses: a status can count as the first response. An agent moving a ticket nobody has answered yet into it - setting it by hand or in a reply, or assigning a new ticket, which opens it - meets (or misses) the SLA's response target then. It can count quietly, or once the contact and watchers are emailed a "ticket assigned" message, kept on the ticket as a public note - an "Assigned" status, say. The message is set in Admin > Settings > Tickets, under Messages to clients. A client's own reply moving a ticket never counts. From Mountaineer IT's build of ITFlow.
-
Tickets: Resolve - no response, on the arrow beside a ticket's Resolve button, is for a client who never answered after several tries. It shows the message from Admin > Settings > Tickets filled in for the ticket, to change before it goes; the message goes on the ticket as a public note and, with client emails on, to the contact and watchers in place of the usual "resolved" words. The ticket is resolved and closes on its own as usual, but without the email asking how we did. If they reply before then, it reopens. From Mountaineer IT's build of ITFlow.
-
Tickets: Email reply has a To line. It starts with the contact, the watchers and anyone at the client who asked for every update on their company's tickets; the technician it's assigned to, the client's other contacts or any email address typed in can be added, and anyone taken out. Everyone in To gets the email, each told why. What was changed is kept for the ticket, so its next email reply starts with the same people - taking a watcher out of To doesn't stop them watching. A reply sent to several tickets at once still goes to each one's contact and watchers. From Mountaineer IT's build of ITFlow.
-
Tickets: Quick ticket - the + in the top bar, on every page - is for a call or someone at your desk: the client (on a client's page, that one), the contact, found by name, email address or phone number, and what the issue is. The contact's tickets still open are listed first, with who has each, so the same problem isn't raised twice - Work on this one goes to one of them instead, with its timer running. Make ticket raises it as New Ticket would and opens it with its timer already running. Admin > Settings > Tickets, Quick tickets, sets what these tickets start with: who they go to, the status, priority, category and billing, when the timer starts, whether the contact starts on the client's primary and whether they're emailed. From Mountaineer IT's build of ITFlow.
-
Tickets: a stopwatch in the top bar shows the ticket timers running or paused in your browser, pulsing while one runs, so time isn't lost on a ticket you moved away from. It lists each ticket and its time, to go back to it, pause or resume the timer, or throw its time away. From Mountaineer IT's build of ITFlow.
-
Tickets: a note with time worked keeps when the work was done. Under Time worked, When it was worked has the date, start and end - filled in from the timer, ending now, until you type them, and typed times set the time worked, for a visit or a call written up later. The conversation shows it beside the time ("25m (Tue Nov 17, 2:05 - 2:30 PM)"), and Edit changes it: new times set the time worked, and a new time worked alone moves the start. An end before the start runs past midnight. A note with time worked needs a date, start and end to send. From Mountaineer IT's build of ITFlow.
-
Recurring tickets: on Schedule, Book the work for takes a time and Remote or Onsite - each ticket raised is booked for its run day at that time, with the emails, calendar invite and note booking it on the ticket gives. Make it ahead raises each ticket so many days before its run day, which stays the day the work is for - or so many days before the 1st of its month, so every run in a month is raised on one day (monthly and longer repeats). The window says when the next one will be made, and the list shows the time and days ahead. Raise now books the ticket for its run too. From Mountaineer IT's build of ITFlow.
-
Recurring invoices: Make it ahead makes each invoice so many days before its date, dated the day it's made, and Due, when made ahead sets it due on its date plus the client's terms, or on its date. With 0 days nothing changes. From Mountaineer IT's build of ITFlow.
-
Maintenance > Cron: the new Cron Watch job, every 5 minutes, emails your admins when a job fails, gets stuck or falls behind - once when it starts, again once a day while it lasts, and once more when it's fixed. The Alerts card turns the emails off, sends them to other addresses instead, and sends a test. From Mountaineer IT's build of ITFlow.
-
Maintenance > Cron: an email can't say cron has stopped, since cron sends it. The Alerts card has a private health address for an uptime monitor such as Uptime Kuma or UptimeRobot: it answers OK while all is well and an error when cron isn't running or a job is in trouble. Check it every 5 minutes. Make a new address if the old one gets out. From Mountaineer IT's build of ITFlow.
-
Development mode, for a test copy of your ITFlow: turn it on in Admin > Backup before you restore production's backup onto a test server, and nothing reaches your clients, your team or the systems production talks to. Every email goes to a test inbox you give, with who it was for at the front of its subject. Texts wait in the queue, the ticket mailbox isn't read, AI Triage doesn't run, Stripe charges nothing (autopay included), log entries aren't sent to your syslog server, a managed ITFlow doesn't check in with its manager, and telemetry isn't sent. A red DEVELOPMENT badge shows in the top bar for everyone. It's kept in config.php rather than the database, so a restore can't turn it off. Never turn it on in production. From Mountaineer IT's build of ITFlow.
-
Maintenance > Backup: restore a backup from the page - Restore in a backup's menu, or upload one under Restoring, from another ITFlow say, with its key. An upload of up to 5 GB goes up in pieces, joins the list as Uploaded and opens its Restore window. That window says what's in the backup and refuses one from a newer version, and you confirm with your password and by typing RESTORE. Cron does it within a minute: ITFlow backs itself up first, kept as Before restore so the restore can be undone, then restores the backup and brings its database up to this version. The top of the page shows it waiting (with Cancel), running, and how it went. The command line restore is still under Restoring, for a backup of any size. From Mountaineer IT's build of ITFlow.
-
Admin > Labor Costs, under Lists: what an hour of each agent costs your company - wage, payroll taxes and benefits - with the date each rate counts from, so a raise doesn't change what last year cost, and a company default for agents with none. Only admins see it, and the audit log never records the amounts. From Mountaineer IT's build of ITFlow.
-
Reports: Client Profitability, with labor costs set, shows each client's labor cost (their hours at the cost of the agent who worked them), parts cost (the products on their invoices, at cost), profit and margin, and for flat monthly fees the hours a month their fee pays for against the hours they take, marked Over when they take more. The totals along the top add labor, parts, profit, and how many clients lose money or go over. Paid and Invoiced switch income between money received, as before, and sales before tax on invoices dated in the period. Hours by agents with no cost and no default are flagged. From Mountaineer IT's build of ITFlow.
-
Users: an API / service account is a login that API keys act as - for your RMM or a sync. Turn on API / service account on a user's Sign in tab (a new one needs Set a password now, as it isn't invited). It keeps its role, so its keys work as before, but it's left out of the calendar, the assign pickers, the reports and the other agent lists, gets no notifications or admin alerts, and can't sign in to ITFlow - a session it has is ended. Admin > Users lists them under API accounts, with an API badge, and leaves them out of the other tabs but Archived. It still takes a seat where there's a limit on agents. From Mountaineer IT's build of ITFlow.
-
Tickets: booked work has an end. The Schedule window has How long - 15 minutes to a day, an hour unless picked - and an Agent picker, so booking someone else's ticket gives it to them and takes it off the old agent's calendar. New Ticket's Schedule and a recurring ticket's Book the work for take a length too. The calendar draws each booking at its length, and dragging its bottom edge changes how long it takes, after asking. The booking email, the calendar file, the ticket and the guest page say when it ends. From Mountaineer IT's build of ITFlow.
-
Tickets: the warning when an agent is booked twice now means it - it lists their tickets and timed events that overlap the booking, at their lengths, instead of anything within two hours. From Mountaineer IT's build of ITFlow.
-
Recurring tickets and events: a monthly, quarterly, twice-yearly or yearly recurring ticket, and a monthly or yearly event, can repeat on a weekday - the third Wednesday, or the last Friday - instead of the same date. Pick its date, then Repeats on offers what that date is: On the 16th, or On the third Wednesday. Moving the next run, or an event's start, keeps it on the same kind of weekday. The recurring tickets list, the event and its calendar invitations say which, and Google, Outlook and phone calendars that subscribe show it on the right days. From Mountaineer IT's build of ITFlow.
-
Calendar: every agent has a color, and their booked tickets and the events assigned to them are drawn in it - so whose work is whose shows at a glance. Each has one from the start; pick your own under Account > Preferences > Calendar color, or an admin picks one in Admin > Users. In the week, 7 days, day and list views the agent's first name sits beside the time. From Mountaineer IT's build of ITFlow.
-
Calendar: events are assigned to agents. New Event and Edit have Assigned to beside the title, and the client's contacts and anyone else by email go under Invite. Calendar is only asked for when you have more than one. An event added from someone's calendar - Whose set to them - starts assigned to them, and it shows on their calendar rather than yours. The event's quick look changes who it's assigned to without opening Edit, sending the cancellation to anyone taken off who had the invitation, and the invitation to anyone added when others have it. From Mountaineer IT's build of ITFlow.
-
Calendar: Left behind, under the calendar, lists open tickets booked on a day that has gone - the work wasn't done and nobody moved it on - longest left first, with how many days ago. Drag one onto the calendar to book it again, for as long as before, or click it for the quick look. Its old booking on the calendar has a dashed red outline. It follows Whose, so Everyone shows everyone's. From Mountaineer IT's build of ITFlow.
-
Calendar: a 7 days view shows seven days from any day, and its arrows move a day at a time, so a booking can be dragged across a weekend without leaving the view. Bookings at the same time now sit side by side instead of on top of each other. From Mountaineer IT's build of ITFlow.
-
Calendar: Holidays, under From ITFlow, shows the closure days from Admin > SLA, and is on to start with. From Mountaineer IT's build of ITFlow.
-
Calendar: what you have shown - calendars, sources, Whose and the view - is kept to your account, so the calendar opens the same way on every computer and phone. The first time, it opens on your own calendar. With Whose set to Everyone, To schedule lists everyone's open tickets that aren't booked, with who has each. From Mountaineer IT's build of ITFlow.
-
Tickets: more than one agent can work a ticket. Under Assigned to on the ticket, Additional agents adds others to help, while the ticket stays assigned to its lead. Each helper is booked at the same time as the lead - moving and cancelled with the lead's booking - at a time of their own, or not booked. A helper finds the ticket under Mine and on the dashboard, is emailed the client's replies as the lead is, and is sent their own booking with a calendar file that doesn't replace the lead's. The client's emails stay about the lead's booking. Click a helper to change their booking or take them off. From Mountaineer IT's build of ITFlow.
-
Tickets: link related tickets - the same outage at several clients, or a problem that keeps coming back. Link related tickets, in a ticket's ⋮ menu, picks any client's open tickets (or ones closed in the last 90 days), and Link together on the tickets list's Bulk Action links the ones ticked. Linking a ticket to one already related to others brings it in with them all. Each ticket's Related card lists the others with their client, status and who has them; its menu has Reply to all and Resolve all for the open ones, and the × takes one out. A related ticket shows a link and how many on the tickets list, and merging a ticket passes its related tickets to the one it goes into. An agent sees only the related tickets of clients they can open, and is told how many others there are.
-
Tickets: the contact's PIN is on the ticket's Contact card, as dots until you click the eye, with a copy button - to check a caller is who they say without leaving the ticket.
-
Tickets: the tickets list and board show +1, +2 after the lead when others are helping - Helping when one of them is you. A helper's booking is on the calendar in their color, can be dragged to a time of their own, shows in their calendar link, and counts when someone books them for something else at the same time. From Mountaineer IT's build of ITFlow.
-
Time zones: an agent who works away from the company can pick My time zone under Account > Preferences. The calendar, the ticket's booking, the Schedule window, New Event and Edit, and the event's quick look are then on their own clock, with a note saying so, and their booking emails give their time with the company's beside it. Bookings are still kept in the company's time, so the client's emails and calendar files, and everyone else's view, don't change. From Mountaineer IT's build of ITFlow.
-
Dispatch: a new page under Support puts each agent's booked work beside the tickets still to give out. The queue on the left has three tabs - No agent, Not booked (with an agent, nothing booked) and Left behind - most urgent first, with a search, a client and a priority filter. Day shows a column for each agent through the day; Week a row for each agent with a column for each day. Drag a ticket from the queue onto an agent and a time, or drag a booking to another agent or time, and the Schedule window opens with the agent, the time, how long and onsite or remote filled in - Schedule it gives the ticket to that agent and books it, emailing them the calendar file, the agent who had it the cancellation, and the contact and watchers unless you switch that off. Drag a booking back onto the queue to take it off the schedule. One-off events move the same way, to another time or agent. Workload shows each agent's open tickets (leading and helping), SLAs breached or close to it, tickets past due, not booked or gone quiet, and the hours booked today and this week against the working hours in Admin > SLA - flagged Falling behind, Watch, Overloaded or Has room against the team. Click an agent for their tickets, or drop a ticket from the queue on one to give it to them. Under it, This week shows tickets in and closed each day, against last week and the last four, the week's SLA results and each agent's share. Which agents show, the view and weekends are kept to your account, and an agent on their own time zone sees it on their clock. Seeing Dispatch takes Support in your role; booking from it takes Support at Modify. From Mountaineer IT's build of ITFlow.
-
Quotes: a quote line can carry what it costs you, and its price can come from that cost. In a line's Edit window, Your cost has Cost each, Price by - Markup (a % added to the cost), Margin (a % of the price) or Set price - and the %, with buttons for the ones you use most: the Price is worked out as you type, and says what the line makes each. Typing the Price yourself makes it a set price. A line added from a product takes the product's cost and keeps its price. On the quote, while it can be changed, each line with a cost shows it under its name with its markup or margin, and the quote's Margin counts each line's own cost. Only agents see any of it - never the PDF, the guest link, the client portal or the invoice made from the quote. Admin > Settings > Quotes has what a line is priced by to start with, its % and the quick picks. From Mountaineer IT's build of ITFlow.
-
Quotes: a quote line can have a picture beside its name - on the quote, the guest link, the client portal and the PDF. In the line's Edit window, which opens wider to fit it, click the picture box to open the Picture window - drop, paste or choose a picture, then crop it to just the product or trim its plain edges away - or paste a link: a picture, or the product's web page, whose main picture is taken. A product keeps a picture too, picked the same way in its Edit window, and a quote line added from it takes a copy; copying a quote copies them. ITFlow keeps its own copy of each, made smaller, and only fetches from public websites. Admin > Settings > Quotes can switch pictures off. From Mountaineer IT's build of ITFlow.
-
Projects: a project's tickets can be kept apart from the service desk - switch on Keep project tickets apart under Admin > Settings > Projects. A ticket in a project is then left off the tickets list's Open, Unassigned, Needs reply and other views - it has a Projects view of its own - and out of the dashboard's unassigned count, the count beside Tickets in the menu and the Dispatch queue, and has no SLA: the project's dates are what count. It stays under Mine, Mentioned me, Closed and All, in Dispatch's Workload and on the calendar and Dispatch, drawn in the project's calendar color with the project named under it and, on the calendar, a dot in the agent's color. A ticket taken out of its project gets its SLA back counted from then, so it isn't overdue at once - and so do they all when the setting is switched off. It starts off, on a new ITFlow too, so nothing changes until you switch it on. From Mountaineer IT's build of ITFlow.
-
Offices: if you work from more than one place, list the others under Admin > Settings > Company Details, Offices - each with its name, address, phone and email, and who works there. An agent's office can also be picked in Admin > Users, and given with an invite. A new trip starts from the driver's office, From offers every office, and changing the driver on a new trip moves From to theirs unless you typed it. Emails about a ticket show the office of the agent on it - the one assigned, else the one sending - at the foot: its address, and its phone and email, or the main office's phone and the ticket email address when it has none. Invoices, quotes and contracts keep the main address. Removing an office puts those who worked there back in the main one. With no other office, nothing changes. From Mountaineer IT's build of ITFlow.
-
Invoices: tick invoices on the invoices list and Bulk Action can now Mark Sent, Send by Email, Mark Paid, Cancel or Delete them - beside Set Category. Each does to every invoice ticked what its button on the invoice does, and only to those that button would be offered for: Mark Sent takes drafts, Send by Email drafts and unpaid invoices whose client has a primary or billing contact, Mark Paid unpaid invoices - one payment each of what is still owed, with the date, method, reference and account you pick and, if you like, one receipt to each client listing what was paid - Cancel all but paid and cancelled ones, and Delete all but those with a payment on a reconciled statement. The window lists which invoices it will do and which it leaves alone and why, and the message after says the same. An agent who can take payments but not change invoices can tick invoices to Mark Paid. Any number can be ticked, up to a page of 500. From Mountaineer IT's build of ITFlow.
-
Dispatch: drag down an agent's column over empty time on Day to raise a new ticket there - New Ticket opens assigned to that agent, with Schedule filled in from the time dragged over, and saving it books the work and brings you back to Dispatch on that day. A plain click on the board still does nothing. From Mountaineer IT's build of ITFlow.
-
Notifications: Admin > Settings > Notifications has Emails and notices to your team - switch off the bell notice or the email an agent gets when someone else assigns them a ticket or recurring ticket, or the copy of a client's reply that goes to the agents helping on a ticket (the agent it is assigned to is still emailed). All on to start with, as before. From Mountaineer IT's build of ITFlow.
-
Calendar and Dispatch: onsite work is easy to spot - a booking with a visit has an orange Onsite strip with a car across the top, an orange edge on the calendar's Month view and an orange line along the top on Dispatch's Week. Remote work looks as before. From Mountaineer IT's build of ITFlow.
-
Dispatch: the Schedule window lists the contact's other open tickets under the ticket - with who has each and when it is booked - so a duplicate is noticed before work is booked on it. Merge beside one keeps one ticket and closes the other with a note pointing to it, as the ticket's own Merge does, with a reason and the choice to move its replies over. A booking on the ticket closed is taken off first, so its agent and the client are sent the cancellation. From Mountaineer IT's build of ITFlow.
-
Purchasing: a new entry under Billing in the side menu - To Order, Purchase Orders and Receiving, as tabs across its pages - for buying from your vendors what you sell, install and keep on the shelf. It's off to start with: switch on Purchasing in Admin > Settings > Modules - it comes with invoicing. Give roles Purchasing in Admin > Roles: See them; Add items, make and send purchase orders, add tracking and receive; or Full, which also approves and cancels purchase orders and undoes a receipt. Admins have all of it. From Mountaineer IT's build of ITFlow.
-
Purchasing: To Order is the list of what needs buying. Add an item by hand - with its vendor, cost and the client it is for - or with Order on a product's page. When products are at or under their reorder level, the alert at the top adds them all in one go. Tick items, then Make a Purchase Order puts them on a new one for their vendor, or Put on a Draft adds them to one already started. From Mountaineer IT's build of ITFlow.
-
Purchasing: purchase orders are numbered PO-1, PO-2 and on - the prefix and the next number are in Admin > Settings > Purchase orders. While one is a draft, its lines can be added, changed and taken off, and Edit Details changes the vendor, where it ships - your main office, another of your offices or any address - the shipping and a note for the vendor. Download it as a PDF, or Email to Vendor sends it with the PDF attached and marks it ordered in the same step. Mark Ordered is for one placed by phone or on the vendor's website, with the date and their order number. From Mountaineer IT's build of ITFlow.
-
Purchasing: approval is off to start with. Switch on Purchase orders need approval in Admin > Settings > Purchase orders and give an amount: a purchase order over it, or with a line that has no cost, is sent for approval before it can be ordered. The admins and the agents with Full Purchasing get a notice and an email, and one of them approves it or sends it back with a note - whoever made it is told either way. Nobody approves their own purchase order, unless they are an admin or nobody else can. From Mountaineer IT's build of ITFlow.
-
Purchasing: add tracking numbers to an ordered purchase order, with when it should arrive. UPS, FedEx, USPS, DHL, Canada Post and Royal Mail numbers link to the carrier's tracking page. From Mountaineer IT's build of ITFlow.
-
Purchasing: Receiving lists everything on its way. Enter how many came in of each line: what was bought for your own stock goes on the shelf, and what was bought for a client becomes that client's assets - one for each unit, with the serial numbers you enter, the purchase order as the purchase reference, and the warranty from the product. Putting stock on the shelf takes Sales at Modify, and making assets takes Support at Modify. A short delivery leaves the purchase order part received until the rest comes in. A receipt entered by mistake can be undone on the purchase order, which takes its stock back off the shelf and deletes the assets it made - deleting assets takes Full on Support. From Mountaineer IT's build of ITFlow.
-
Purchasing: Record Bill on an ordered purchase order records the vendor's bill as an expense - the amount, vendor and description filled in from the purchase order - and links the two, along with the stock it put on the shelf. It takes Financial at Modify. From Mountaineer IT's build of ITFlow.
-
Purchasing: an agent who can only see some clients only sees the purchase orders whose lines are all for clients they can see. A purchase order's History shows who made, sent, approved, ordered, received and billed it, and it is in the audit log. From Mountaineer IT's build of ITFlow.
-
Menu: fewer entries to scroll past. Recurring Expenses is now a tab on Expenses, and Transfers a tab on Transactions, with the tabs across the top of each page. Purchasing is one entry with its pages as tabs, and its number is the purchase orders waiting for your approval - otherwise the items waiting to be ordered.
-
Client menu: Calendar, Racks, Certificates, Shared Links, Services and Trips stay out of a client's menu while the client has none of them, when two or more are empty, so the menu is shorter for most clients. More, at the bottom of the menu, shows them - to add a client's first rack, say. Each comes back as soon as the client has one, and always shows on its own page.
-
Admin menu: eight entries shorter, nine with texting set up. Templates is one entry under Lists & Templates, with Tickets, Projects, Canned Responses, Contracts, Vendors, Licenses and Documents as tabs across its pages. Logs, under Maintenance, has Audit Logs, Sign-ins and App Logs as tabs. Text Messaging has Setup and, once texting is set up, Messages, with the texts that failed to send in the last week counted on the menu. Where ITFlow points you to one of these pages, it now says where it is - Admin > Templates > Tickets, say.
-
Across clients: All Client Docs has moved from the main menu to the top bar, beside the menu button, and is now called Across clients. It opens a menu of what you can see for every client together - contacts, locations, assets, credentials and the rest - and takes you straight to the one you pick, instead of always to Contacts. Once you're there, the side menu is the same as before, headed Back | Across clients. On a phone it's just the icon, and the search box beside it narrows to fit.
-
Knowledge Base: one place for the how-tos, fixes and policies your team gives again and again, written once for every client - Knowledge Base, in the main menu. Each article has a title, a line saying what it's for, a category, tags and its content, written in the same editor as documents, pictures and all. An article is a draft until it's published. Every edit keeps what it said before, to look at or put back from its Versions. Say how often an article is reviewed - every year, to start with - and it shows Review due once it's that long since it was written, edited or marked reviewed. The list searches titles, summaries, the words in the articles and their tags, filters by category and tag, and has All, Published, Drafts, Review due and Archived views. Ticked articles can be put in a category, published, made drafts, archived, restored or deleted. Articles can be copied, and Copy to Knowledge Base on a client's document makes a draft article from it. Search everywhere finds articles too. Admins set up the categories, with an icon and color each, in Admin > Categories > Knowledge Base, and the tags in Admin > Tags. Reading the Knowledge Base takes Support; writing in it takes Support Edit, and deleting Support Full. Admin > Settings > Modules switches it off.
-
Knowledge Base articles for your clients: say who can read each article - your agents only (to start with), clients, or anyone. For clients, pick all of them, the ones with some client tags - every client tagged Managed, say - or some clients by name, or a mix. Once an article is published, those clients' contacts find it in their client portal under Help, a new item there once they have something to read: search, categories, a Print button, and Still stuck? Ask us, which opens a ticket about it. An article for anyone is in every client's portal too, and on a public help center - a page of its own with your logo, at /guest/kb.php, for anyone with the link and no sign-in, which you can put on your website. It starts off: switch it on in Admin > Settings > Knowledge Base, which has its link to copy. While it's on, the client portal's sign-in page links to it, and an article for anyone shows its public link to copy. Drafts and archived articles are never shown outside ITFlow. The Knowledge Base list has a Who can read it column and filter, and each article says who can read it and where they find it.
-
Knowledge Base on tickets: beside Canned response above a ticket's reply, Knowledge Base opens the published articles that look like they answer the ticket - counted on the button - with a search for the rest. Each says how the ticket's client could read it: Link puts a link to it in the reply - the public help center's, or their portal's - and Insert puts what it says in, pictures and all. Write up for the Knowledge Base, in a ticket's ⋮ menu, starts a draft article from the ticket, for agents only until it's read through: with AI set up for documentation, AI writes it as a how-to for any client, leaving out the client, its people and its systems; without, it starts from what the ticket asked. The ticket's history says it was written up. In the client portal, as a contact types a new ticket's subject, the Help articles that might answer it show under it, each opening in a new tab.
-
Knowledge Base feedback and upkeep: under each article in the client portal and the public help center, Was this helpful? - and for a No, what were they looking for. A contact has one answer an article; on the help center it's one a visit. Each article counts how many times it was read there, once a visit. The Knowledge Base list has a Readers column - reads, and the share who said it helped - sortable by reads, and a Needs a look view for the articles readers said didn't help that nobody has dealt with yet. On an article, Feedback lists what they said, who said it and when, each with Dealt with. Not found, at the top of the list, shows what readers searched Help and the help center for in the last 90 days and found nothing - where, and how many times - with Write an article, which starts one with those words as its title. The Knowledge Base in the main menu counts the articles due for review or said not to help. Viewing the portal as a contact counts nothing.
-
Knowledge Base articles: files - a script, a form, a vendor's guide - go with an article, added on its page, up to 20, of the kinds Files takes. Whoever can read the article can download them: your team, its clients' contacts in the portal, or anyone on the public help center. PDF on an article's page takes it as a PDF. With AI set up for documentation, Review with AI reads an article and says whether it looks good, needs work or is out of date, what to fix or check, and - for an article clients or anyone can read - anything about one client or its systems that shouldn't be in it, with a summary to use. Copying an article copies its files.
-
Invoices: an invoice a recurring invoice's autopay pays now says so - beside its number and under Payment on its page, and under its due date in the invoices list: which card and when (Autopay Dec 1), once it's sent for a draft, Autopay won't charge when the card runs out before the due date or the payment provider is turned off, and Autopay didn't pay it for one still owed after its due date, with why when the card was declined. An invoice that fell due before autopay was set up isn't marked. The client's link to the invoice says autopay will pay it, and when, so they don't pay it twice - as the client portal already did.
-
Documents: how often a document is reviewed can be set on the document itself, from How often beside its review - every 3 months to every 2 years, never, or as its template says. A document with no template can be reviewed on a schedule too; it shows Review due on Files, its client's overview and the reports like any other. Changing it doesn't count as reviewing it.
-
Files: drag a file or document onto a folder on the left to move it there - tick several first and drag one of them to move them all. A folder drags onto another to go inside it, with everything in it, or onto Top level to come out. Holding over a closed folder opens it, and the folders in the path above the list take a drop too. Files from your computer dropped on a folder on the left upload into it. Each move goes in the audit log.
-
Windows ask before closing when something typed in them hasn't been saved. A click outside the window, Escape, its X and Cancel all ask first; saving doesn't.
-
A list's filters that are on now stand out, tinted in your theme color, and an x at the end of the search box clears the search and every filter at once - on clients, tickets and projects too, in place of the chips that listed each filter under them. More filters on those three takes the same tint while one tucked under it is on, where it turned yellow.
-
Shift-click a list's tick boxes to tick, or untick, every row between two clicks.
-
Compact rows: Your account > Preferences can show lists with tighter rows, so more fit on screen.
-
Tickets: what you type in a ticket's reply box is kept as you write. Leave the page, close the browser or get signed out, and it's back next time with a note saying so - pick how to send it to carry on, or discard it. So leaving a ticket with a reply half written no longer asks "Leave page?" first.
-
Tickets: drop files onto a ticket's reply box to attach them to your reply.
-
Tickets: +15m, +30m and +1h beside Time worked add time in one click. The timer stops at the new total.
-
Tickets: on a billable ticket, sending a reply with no time asks first - Send without time, or Add time.
-
Tickets: Split into a new ticket, in the menu of a client's reply, makes a ticket of its own from a second problem raised in a reply - same client and contact, the reply as its details, its attachments with it. The reply leaves the first ticket, and a note on each points to the other.
-
Tickets: Copy as a new ticket, in a ticket's More actions, opens New Ticket with its subject, details, priority, category, billing, contact, asset and tasks - for the same client, or pick another.
-
Tickets: Apply a template, in a ticket's More actions, adds a template's tasks to a ticket already open (change them first if you like), asks what the template asks, and adds its tags and due time where the ticket has none.
-
Tickets: emailed replies now keep the email as it arrived, as new tickets already did. Read beside it shows who it was from and to, its headers and everything it said - the reply line trims what shows on the ticket - and the .eml downloads from there. The client portal no longer lists these copies.
-
Click a picture shrunk to fit in a ticket, document or Knowledge Base article to see it full size - in the client portal too.
-
Tickets: the tickets list keeps itself up to date. Once a minute, a ticket that changed - a reply, a new status, someone else picking it up - is updated where it is on the list, and a bar above the list says when tickets have come into the view or left it, with Show to load the list again. A ticket you've ticked waits for Show.
-
Tickets: a ticket the client has written on since you last opened it is in bold on the tickets list - a reply from them, or a ticket they raised by email, in the portal or by text. Opening the ticket or its quick look takes the bold away, and so does Bulk Action > Mark as read. Each agent has their own; tickets from before the update count as read.
-
Tickets: rest the pointer on a ticket's Activity on the tickets list to see its last reply - who, when and what it said.
-
The tickets list's browser tab shows how many open tickets are assigned to you, such as "(3) Real MSP - Tickets" - kept up to date in the background, so you see it from another tab.
-
Desktop notifications: turn on the Desktop notifications switch at the bottom of the bell's panel, and a ticket assigned to you or a client's reply on one of yours shows as a notification on your computer while you're away from ITFlow. Each browser has its own switch, and asks your permission first. The panel shows whether they're on, off or blocked in the browser you're using.
-
Documents: Edit opens a document on a page of its own, with the editor filling the window and its toolbar always in view - long documents no longer squeeze into a window over the page.
-
Documents: Copy, in a document's menu, copies it for the same client or another - content, summary, tags and pictures, out of the client portal and linked to nothing.
-
Documents: a document with three headings or more has a Contents list beside it, to jump to a section - Knowledge Base articles too.
-
Documents: the arrows beside each version, and beside Now, show what that edit changed - lines taken out and put in, the changed words marked, the rest folded away.
-
Documents: Favorite, in a document's menu, puts it on the client's overview under Favorites, with their favorite assets, licenses and logins. A star marks it on its page and in Files.
-
Files: Choose a folder in the Upload window - or drop a folder on it, or on Files - uploads the folder with the folders inside it, made as needed. A folder goes up 20 files at a time, up to 1,000 files and 2 GB.
-
Files: Download as zip, beside the folder's path, downloads the folder and everything under it - at the top level, all of the client's files. Bulk Action > Download as zip does the same for the ones ticked. Documents go in as web pages.
-
Files: rename a file or document from the list - the pencil beside its name - and press Enter.
-
Clients: rest the pointer on a client's name - on the tickets, invoices and other lists, on a ticket, or a link to the client anywhere - for a card with their primary contact's phone and email, their main site's phone and address, and their open tickets.
-
Clients: Offboard, in a client's menu, does what's left when you stop working with a client in one go - portal sign-in off and invites cancelled, shared links ended, recurring invoices stopped, recurring tickets paused and the client archived - with Export Data a click away first.
-
Contacts: a contact whose email bounces shows Email bounced, with when and what the mail server said. It goes when mail comes in from the address, when the address is changed, or with Clear.
-
Contacts: New ticket in a contact's row on the contacts list raises a ticket for them without opening them first.
-
Tickets and assets: the + beside Contact, Site and Vendor in New Ticket and Edit Ticket, and beside Location, Assigned to and Vendor in the asset form, opens the usual New Contact, New Location or New Vendor window over the form. What you make there is picked, and the form underneath stays as it was - no closing it to add one.
-
Clients: Merge into another client, in a client's menu, merges the same company added twice - every contact, ticket, invoice, document, file and the rest moves to the client you keep, whose own details stay, and the duplicate is left archived and empty. It says first what moves and which agents' access differs between the two. It takes Delete access to clients.
-
Assets: Copy details, on an asset's page and its quick look, copies what a vendor's support case asks for as text, ready to paste - make and model, serial, OS, its details, IP and MAC, warranty, dates, the site's address and where it is racked.
-
Racks: drag an item on a rack to another position, or across to the other side, and it moves there. Drag one of the client's assets from Not racked yet onto the rack and Add opens with it and where you dropped it filled in. While you drag, the rack shows where it would go, in red where something is in the way.
-
Credentials: Reused password, along the top of Credentials, picks out the logins whose password another of the same client's logins also has, each marked Reused, and a credential's quick look names the others. The passwords are compared as the page opens, with your vault key, and nothing about them is kept.
-
Credentials: a password that is changed is now kept as an earlier password, still encrypted. Earlier passwords in a credential's quick look shows when each was in use and who changed it, with the eye and copy buttons, and Put back makes one the password again when a change broke something. The newest ten are kept, agents with Delete access to credentials can delete one, and each one looked at is logged.
-
Recurring invoices: Pause can now pause until a day - the recurring invoice runs again by itself that day, from its next date after it, and nothing is billed for the runs in between. Leave the day empty to pause until resumed, as before. Paused ones say until when on the list and their page.
-
Recurring invoices: Copy to Another Client, in a recurring invoice's menu, makes the same one for another client - its lines, scope, category, discount, notes, how often and how it sends - starting on the day you pick. Lines billed per user or device count the new client's. A line counting license seats keeps its quantity, as the license is the first client's. Autopay isn't copied.
-
Recurring invoices: tick them on the list and Bulk Action pauses them (until a day, or until resumed), resumes them, or changes their next date or how often they bill.
-
Payments: Add Payment lists the client's other unpaid invoices, oldest due first, with what's owed on each and Pay this one - and says when some were due before this one. Batch Payment, beside them, pays several at once.
-
Invoices and quotes: Send has Also send to, for an address that isn't one of the client's contacts - their accountant, say. It's for this once and isn't saved. A client with no contact to send to can now be sent one this way.
-
Quotes: three days before a sent quote runs out with no answer, the people who can see quotes get a notification to follow it up.
-
Expenses: on a phone or tablet, the picture window has Take a photo, which opens the camera straight away - for a receipt, and for every other picture and photo in ITFlow.
-
Timers: the stopwatch in the top bar is always there now, and starts a timer before there is a ticket - for a call that may or may not need one. New ticket opens Quick ticket with the timer carrying on from where it is, and Add to a ticket finds one (your own open tickets until you type) and adds the time to its timer. Picking one of the contact's open tickets in Quick ticket adds it there too.
-
Timers: the timers panel says how much time you logged on tickets today and this week - the week starting on the day your calendar does.
-
Calendar: an event can remind you - when it starts, or from five minutes to two days before. The agents it's assigned to get a notification, or whoever made it when nobody is, and each time a repeating event comes round. Your account > Preferences has Remind me before work booked for me, for tickets booked with you, and Email me reminders too. Reminders need cron, and go within a minute.
-
Projects: a project has a Timeline - its booked tickets as bars in time, from its start to its due date, with now marked. A booking that is past and still open shows in amber, and two of the same agent's at the same time are flagged. Its open tickets with no booking are listed under it, with Book.
-
Pickers: long lists of clients, contacts, vendors, categories, locations, assets, technicians, projects, accounts and products start with the last five you picked in a field like it, under Recent, above All. Typing searches everything as before. Every dropdown in a window is now one of these pickers - the last plain ones, such as a line's tax and frequency, how long a booking is and whether it is onsite, and a ticket status's SLA setting, too.
-
Archived: Tools > Archived lists what was archived lately - clients, contacts, locations, vendors, assets, credentials, documents, files, domains, certificates, networks, racks, services, licenses, projects and products - newest first, with who archived each one, to restore one or several at once. The last 30 days to start with, or pick another time, a kind or a client.
-
Undo: archiving no longer asks "Are you sure?" - the message that says it's done has Undo instead, as do moves and changes to several records at once. The message stays up for ten seconds, or as long as the pointer is on it, and only its x closes it - set apart from Undo, so a click that just misses Undo doesn't lose it. Undo covers archiving one or several of every kind Archived lists, bringing back what archiving took with it - a contact's roles, a document's links, a client's recurring invoices; moving files, documents and folders, dragged or with Move; dragging kit on a rack; and the bulk changes to a ticket's priority, category or project, an asset's location, physical location, contact or status, a contact's location, department, phone number or roles, a client's industry or referral, a project's manager or due date, an invoice's or product's category, and an IP address's type. In Admin, Undo is on archiving tags and categories (one or several), canned responses, ticket, project, document, vendor, license and contract templates, roles, payment methods (a default it stopped being comes back with it), SLAs, custom links, portal announcements and banners, on archiving a tax, and on switching off a ticket status - those last two when nothing was moved to another. A payment method is archived without asking first now. In Admin, as everywhere else, the message after archiving, removing, unlinking or cancelling something is red and the one after restoring it or Undo is green. Undo works once and only for whoever made the change, and leaves anything changed again since as it is, saying how many. Archiving a client still asks first, and has no Undo when it withdrew a contract out for signing. Archiving a client (one or several), a ticket reply, an account or an SLA, and restoring anything archived, no longer asks first either - the ticket reply and the account have Undo too.
-
Client portal: one Search box in the top bar looks through the client's tickets - their subject, number and what was said on them - the documents you share with them and your Help articles at once, the first eight of each with See all. Nothing found offers Ask us, and a search with no Help article goes on the Knowledge Base's Not found list.
-
Client portal: a ticket says when to expect your first reply - We'll reply by and the time, from its SLA - until you reply, while it isn't on hold and the time is still ahead. New ticket says how soon you reply to each priority, beside the priority and under What happens next. Without SLAs nothing is promised.
-
Users: Invite several, beside New User, invites a list of people at once with one role (and office, and whether two-step sign-in is required) - one per line, as a name and email or just the email. Each gets their own invite email; anyone who already has an account is skipped and named. It needs email set up.
-
Tickets: Try an email, in Admin > Settings > Tickets under Email to ticket, says what the support mailbox would do with an email from someone with some subject - a reply on which ticket and as whom, a new ticket for which client, or left in the mailbox - step by step, without making or sending anything.
-
Weekly summary: Admin > Settings > Notifications can email the owners - every admin, or the addresses you give - early on the day you pick, how the last seven days went beside the seven before: tickets opened and resolved, SLAs missed, ratings, time logged and billable, new clients, invoiced and paid, the busiest clients, and what needs a look - open tickets nobody has, overdue invoices, and domains and certificates running out. Send me one now shows what it looks like, and it is among the email previews. Off to start with.
-
Tickets: a ticket opened from the tickets list, a notification or a search shows what its client owes on invoices past their due date, beside the client's name, to agents who can see invoices - with how many and how late the oldest is. It opens their overdue invoices. Opened from the client, the client header already shows what's due, so the badge isn't shown twice.
-
Invoices: a draft left more than a week says so on the invoices list, under its status, and Drafts left a week picks them out - In drafts counts them too. The nightly notice about drafts says how many have been left that long, and opens them.
-
Contacts and assets: an email already on another contact - now when changing a contact too - and a serial number or MAC address already on another asset are named as they're typed, with who or which, and where.
-
Modules: Admin > Settings > Modules has five more switches, to take out of ITFlow what your business doesn't use - Dispatch, which comes with Ticketing; Bookkeeping, Purchasing and Trips, which come with invoicing; and the Calendar. Each part is off while the one it comes with is, and shows faded under it. Switched off, a part leaves the menus, the dashboard, search, the reports and the API, and its pages and windows say it is off. Nothing in it is deleted - switched back on, it is all there. Dispatch, Bookkeeping, Trips and the Calendar start on, as before.
-
Bookkeeping: switch it off when your books are kept somewhere else. Accounts, Transactions, Transfers, Reconcile and the statement imports go, and nobody picks an account: payments and income go into the default payment account, and expenses come out of the default expense account - both in Admin > Settings > Defaults, or the first account when there's no default. An expense is paid by The business or Paid personally. The dashboard leaves out the account balances, and the Tax Package its Accounts section.
-
Calendar: switched off, the calendar, its events and the calendar feeds go - a subscribed calendar stops getting them. Tickets are still booked from the ticket and on Dispatch, and booked work still shows on the dashboard.
-
Updated the libraries ITFlow is built on: the one that reads ticket mailboxes, the one that sends email, the text editor, the one that cleans up email and document HTML before it is shown, Stripe, the page styling, the charts, the tables, the calendar and the phone number fields. Nothing changes in how they look or work. The text editor's update fixes a security problem in its media plugin, which ITFlow doesn't use.
-
Pages are a little lighter: five add-on libraries are gone - three ITFlow no longer used, and two swapped for ITFlow's own code. The IP and MAC address fields on assets and the QR codes for setting up MFA and for shared links work as before. The download is about 5 MB smaller too, without the text editor add-ons and icon font files ITFlow never used.
-
Lists: a row shows its tags only when it has some, so untagged rows are a line shorter. To tag one, use Tags in its ⋮ menu - its tags show on the row as you tick them, no reload. Cards on the tickets board and the Files grid have it in their menu too. To tag several together, tick them and use Tags in Bulk Action. A client's other pages show the client's tags without the +; change them on the client's overview or the clients list.
-
Lists: the page numbers stay on one row - the first and last page and the ones next to yours - however long the list, with the record count in the middle of the footer above them or beside them.
-
Tickets: Unassigned is amber, as the Unassigned view and the dashboard's tile are, and Not billable a light gray - red is kept for what is late.
-
Dashboard and client overview: when the last row of Needs attention is short, its tiles keep their width rather than one stretching across, and a count of one reads 1 Draft invoice, not 1 Draft invoices. A client's Open tickets line up their SLA, status and last activity down the card, as My tickets on the dashboard does.
-
Unbilled Time: the time logged is under the hours to bill rather than a column of its own, so the list fits beside Bill these clients.
-
Forms: the + beside a picker and the Cancel button look the same in every window, a vendor's What they are is Description as on other records, and a few notes under fields that only said where a value shows are gone.
-
Starter Content and the demo data are in US spelling - license, authorized, organization, fiber and the like. Where you loaded them before, nothing is added twice: the Authorised Contacts Only vendor tag and the Licence assigned canned response you have count as loaded, and bringing the starter canned responses up to date gives the response its new name. Bringing the starter ticket templates up to date has New Hire Onboarding ask for the License. Loading the demo data again, or removing it, still finds what an earlier load made.
-
Maintenance > Starter Content is laid out like Backup and Update: how much of the library you don't have yet, with Add all, at the top; each pack with how many it would add and how many of it you have, Pick which, its Add and its Update; the demo data under them; and the totals, how adding works and what to know about the demo data at the side. Update and Remove demo data ask first in the usual window.
-
Maintenance > Starter Content: Clear out unused, beside a pack's counts, archives what you have from the pack that nothing uses yet - a category no ticket, invoice, expense or product has, a tag on nothing, a template nothing was made from, a canned response never put in a reply, a product on no invoice, quote or asset. A window lists them, all ticked, and says how many are in use and stay; Undo puts them back, and Add doesn't make them again.
-
Tabs that don't fit across the screen go into More at the end of the row, instead of running off the edge out of sight or wrapping onto more lines - a list's views (the tickets list at most screen sizes), a record page's tabs (a contact's, an asset's, a location's), a quick look's, a form's, and the kinds in Admin > Categories and Tags on a phone. The tab you're on always stays out, and More shows a red or amber count when a tab in it needs attention, such as Overdue, Unassigned or a contact's open tickets.
-
Linking: Link - along the top of a record's page, on its tabs and in quick looks - opens a list right under it instead of a window. What's linked already is ticked: tick to link, untick to unlink, and it's saved when you click Done or anywhere else, with one message for what changed. It covers documents, files, assets, contacts, licenses, credentials, vendors, services, locations, domains and certificates, a contact's assets and credentials and an asset's credentials, a project's and a service's tickets, a ticket's services and its related tickets. A document's or file's Link lists every kind it can be linked to, in groups. Tickets are no longer added to a project by typing their numbers - tick them in the list (open ones and those closed in the last 90 days), or change the project on the ticket.
-
Sign-in codes: the 6-digit code - signing in with two-step sign-in, setting it up (yours, or a contact's in the client portal), and the code emailed for a shared link - goes in six boxes, three and three. Paste or let your phone or password manager fill it, "123 456" too, and it goes as soon as the sixth digit is in - no need to click the button. A wrong code turns the boxes red. On the sign-in page Remember this browser now comes before the code, so tick it first.
-
Browser autofill: Chrome, Edge and other Chromium browsers no longer offer your own name, email, phone or address in forms about clients - a new client's contact, a contact, a location - and Bitwarden, 1Password, LastPass and Dashlane no longer offer your ITFlow login in a credential's username and password, or anywhere else you type someone else's details or secrets, nor ask to save them. Your own profile, password change and two-step sign-in still work with your password manager.
-
Tickets: the first technician to reply to a ticket nobody is assigned to - with a public note, an email reply or a text reply - is assigned it, as Assign to me would, and the message after sending says so. An internal note doesn't assign it, so a ticket can be looked into, or someone @mentioned on it, without taking it, and a ticket already assigned keeps its technician. Admin > Settings > Tickets > Assigning switches it off - for a shop where someone answers new tickets before handing them on.
-
Dates: every date reads one way - Nov 13, 2026, with times as 2:30 PM and the day of the week as Fri, Nov 13 where it shows. The invoice, quote, recurring invoice, expense, income, trip and transaction lists and pages, an asset's and a license's dates, certificates, domains, invoice and quote PDFs, statements and the guest invoice and quote pages showed 2026-11-13; some times read 2:30pm or 14:30, and some emails put the day first, 13 Nov. Pointing at a "3 days ago" shows the date and time the same way. Date fields, exports and file names keep 2026-11-13.
-
Windows and buttons: a window that makes something new is called New ... and its button says Create, and an edit window is called Edit ..., with the record's name after it in lighter text, and its button says Save - the titles read Editing contact:, Tag:, Creating note: and so on, and the buttons said Add, Add Income, Add Expense, Log Trip, Set Up, Make Draft, Create Client, Save changes and the like. On list pages the button that opens it says New, as New Provider, New Model, New Instance and New Item had said Add. A window that adds to the record it's on - Add Tickets on an invoice, Add keys on a license - still says Add. Field labels sit the same distance above their fields in every window, the extensions on a new client, applying a project template and adding ticket templates to one have their icon in front like every other field, invoices have one icon everywhere, and deleting a client is a normal window with Delete at the bottom, turned on once the client's name is typed.
-
Menus, icons and questions: every More menu has the same ⋮ button, and Delete, Restore, Export, Copy and Show each have one icon everywhere, and a network's IP list says Bulk Action like every other list. The required-field star sits the same way on every form, and Incident response has the usual dark window with its warning in red. A question before an action names it on its button - Delete, Remove, Archive - rather than Yes. Resetting a ticket's timer, removing an approval request, redacting with nothing selected and a window that fails to open now use ITFlow's own question and message rather than the browser's. Every list's search box reads Search ..., with what it looks in shown when you point at it.
-
Dropdowns: the empty first choice reads the same way everywhere - - Select a client -, - Select an account - and so on where you pick one, - Any client -, - Any status - where a list is filtered, and - None -, - No contact -, - Nobody - where it can be left blank. They had said - Select Client -, - Pick a role -, - Which account -, - How it was paid -, - All Clients -, Not Assigned and the like.
-
Capitals: page and window titles, menu items and buttons are in Title Case - New Ticket, Mark Reviewed, Back Up Now, Turn Off Portal Access - and field labels, section headings, tabs and help are in sentence case - Postal code, Tax rate, Physical location - in the agent pages, Admin and the client portal alike. The settings pages in the menu are now Company Details, Invoices and Billing, Purchase Orders, Client Portal and Single Sign-on.
-
Lists: the first click on a column you aren't sorting by sorts names A-Z and dates, money and counts newest or largest first, and a second click flips it. It used to go the opposite way to the column you were on, so the first click could go either way.
-
Badges and blanks: every badge is a rounded pill, the menu counts included, and an empty value shows as a grey dash everywhere. A request that can't be done - credit over the balance, say - shows in red like every other error, and the client portal's search boxes read Search ... like the agent pages'.
-
Sizes and lengths of time: a file or backup size reads 512 B or 1.5 MB everywhere - some pages said 1.53 MB, a portal attachment never less than 1 KB, and setup bytes. Booking lengths, the dispatch board and how long a cron job ran are written 1h 30m like time logged everywhere else - they read 1 hour 30 min and 2 min 5 s - and hours as a number are 12.5 h, project hours included.
-
Forms: hints inside empty fields are plain examples - example.com, Contracts, Closing remarks - rather than e.g. ..., ex. ... and Enter a ..., and address fields bring up the web keyboard on a phone. New Location and New Network open at the size their Edit windows do, and the transactions list's amount filters take 1,000.00 like every other money field.
-
Messages: the message after a window closes matches its button - created after Create, saved after Save - where some said added, updated or edited. Copying an invoice says which invoice it was copied to, making one recurring names the new recurring invoice, a payment on several invoices says how many it paid and who the receipt was queued to, and attaching files to a ticket without a reply says so rather than Ticket updated.
-
Client portal and emailed links: what a client sees after accepting or declining a quote, approving a task or sending a file reads the same from an emailed link as in the portal - Thank you - quote QUO-79 is accepted and our team has been told, rather than Quote Accepted. Card payment problems are in plain words - Card payments are not set up, rather than Stripe credentials missing. A link that isn't right, online payment that isn't available, or a payment that can't be confirmed shows the same page as a mistyped invoice link, rather than an Oops line on an empty page.
-
Wording: a ticket task's approval picker says agent rather than technician, with the same blank choice as other pickers - - Select one - and - Select an agent - rather than Select... and - Select a user -. Pickers that fill in as you go read like the rest: changing a ticket's client offers - Select a contact - (or - No contacts -), a project with no client offers - Nobody -, and an asset detail or statement line with nothing picked shows - None - or - Not for a client - rather than a bare dash. The Tickets list's Billing filter starts at - Any -, record pages say Upload Files rather than Upload File(s), and Maintenance > Cron's log counts 1 problem rather than 1 problem(s).
-
Screen readers: every window's close button is read out as Close, and the arrow beside a list's New button and the ⋮ menus on record pages as More actions, rather than as a button with no name or just More.
-
Counts: the counts in menus, tabs, list headers and under every list - Showing 1 to 25 of 1,834 records - have a thousands separator, as the dashboard, reports and audit log already did.
-
Confirmations: archiving a credential from an asset, contact, vendor, service or license page no longer asks first, as archiving anywhere else doesn't - the message's Undo puts it back. Taking a related ticket off a ticket, or a ticket off a service's page, asks first, as the ticket page's other × buttons do. Hints under a few fields - a statement's From, a cron job's schedule, a quote's price per hour - look like every other field's.
-
Required fields: every field marked * has to be filled in before the window saves, and every field that has to be filled in is marked * - a few had one without the other, such as a credit's note, the comment when merging several tickets, the dates when activating, renewing or ending a contract, and the one choice in the windows that set a location, contact, status or referral on the ticked records. Hints under fields look the same in every window.
-
Starter content for the Knowledge Base: a Knowledge Base Articles pack of 29 how-tos and fixes for your clients' staff - passwords and MFA, phishing, Outlook, OneDrive, the VPN, printers, Teams, Wi-Fi, new starters and leavers - each under its category with tags, and reviewed once a year. They come in as drafts only your team can see, ending with how to reach you from Company Details: read each, make it say what your clients use, then publish it to the clients it suits. The Categories pack has twelve Knowledge Base categories and the Tags pack ten article tags. The demo data has a Knowledge Base of its own - articles for every client, by client tag, for one client and for anyone, ones for your team only and drafts - with reads, feedback, earlier versions, one due for review, searches that found nothing and links to them in ticket replies.
-
Your own asset types: Admin > Asset Types lists every kind of asset with how many there are of each, and adds your own - a Badge Reader, a Vehicle, a Hypervisor. Start one from any of ITFlow's types, then change its icon, color, group (its tab on the assets list, and how the client overview and portal count it), the fields it asks for, ITFlow's details it has and whether it goes in a rack, and give it details of its own: text, numbers with a unit, lists, and dates that are flagged and notified as they near. They work wherever ITFlow's do - the asset form and page, the Details column, exports and imports, products, receiving and the API. Renaming one renames it on its assets, and deleting one moves its assets to another type first. Any type but Other can be switched off, so the pickers stop offering the ones you never use while their assets keep them. Types on assets that aren't set up, from an import or the API, are listed there to set up in a click.
Bug Fixes
- Invoices, quotes and recurring invoices: leaving the page in the middle of typing a note asked "Leave page?" - even though the note saves as you go. It now saves on the way out instead.
- Email replies to tickets: a client who typed below the "Please type your reply above this line" line - or whose mail program puts replies under the email it quotes, as Thunderbird and Apple Mail can, and plain text replies do - lost everything they wrote, and the ticket got an empty reply. What they wrote below the quote is now kept, as well as anything above the line. When nothing was written above the line and their words can't be told from the quote, the whole email goes on the ticket with a note saying so, rather than nothing.
- Invoices: Copy Invoice and Make Recurring copied the Card Fee line of an invoice paid by card, so the copy or every invoice the recurring one made charged the fee before anyone paid - and a client who paid the copy by card was charged a second fee on top. The card fee ITFlow added is now left off, the total without it, and the Copy Invoice and Make Recurring windows say so. A line you typed yourself with that name is still copied. Releases from 26.11.4 to 26.11.8 are affected.
- Quotes: Copy Quote dropped each line's link to the product it came from, so the copy's Margin left those lines out. The copy now keeps it. Found by Mountaineer IT.
- Backups: restoring a backup rewrote the uploads folder's settings in a form Apache with PHP-FPM refuses - as HestiaCP, cPanel and Plesk run it - so your logo, avatars and photos stopped loading after a restore. Found by Mountaineer IT.
- Contacts: archiving several contacts at once left the client's primary contact in place, as it should, but archived its client portal login, so they could no longer sign in. Found by Mountaineer IT.
- Sign-in: an authenticator code of 000000 was taken as no code. Found by Mountaineer IT.
- Tasks: Mark all complete also completed tasks waiting for an approval, or declined, which the task list doesn't let you tick. Those now stay open, and a task waiting for approval can't be completed on its own either. Found by Mountaineer IT.
- Email parser: an email with a subject over 500 characters, or an attachment with a name over 255, was never taken - it was tried again every minute. An attachment name with an apostrophe was also saved with a backslash in it. Found by Mountaineer IT.
- SLAs: saving an SLA, the SLA settings or a closure day, or changing a ticket's priority, sent the "SLA breached" email again for every open ticket that had already been sent one, and the warning again for those already warned. A ticket keeps its alerts now unless the change gives it a new target to meet - one moved later is warned and breached again when it comes. Found by Mountaineer IT.
- Ticket emails: with Microsoft 365, cancelling a ticket's schedule left every "Ticket Schedule Cancelled" email failing with "SMTP Error: data not accepted", however often it was retried. The cancellation went in the email as a meeting cancellation with no organiser or attendees, which Microsoft 365 turns away. It's now attached as a calendar file, the same way the booking is, for the recipient to open and take the visit off their calendar. Event invitations and their cancellations, which have attendees, go as before.
- Mail queue: when the mail server turns an email away, Admin > Mail Queue and the failure notice now show what the server said, not only the step that failed - "SMTP Error: data not accepted. The mail server said: 554 5.2.0 ..." - which usually says why.
- Invoices, quotes and contracts: opening one from its link while signed in to ITFlow - View as Client - counted as the client viewing it. A sent one became Viewed, its history said the client had viewed it, and your team was told. An agent looking doesn't count now; the client opening it still does.
- Ticket emails: a picture of about 750 KB or more pasted into a reply, or into a ticket's details, left the email without its message - the picture went missing, and the words with it. The email has all of it now, whatever the picture's size. The same picture made a document come out empty in a client export, and a document template come out empty when it was exported or imported.
- Ticket emails: a picture pasted into a reply, or into a ticket's details, now goes with the email as a picture attached inline, where the message shows it, rather than as data inside the message. Gmail, among others, showed no picture sent the old way. The mail queue also keeps each picture once, instead of a copy inside every email it sends. Admin > Mail Queue still shows the email with its pictures.
- App Logs: the email parser wrote an entry every minute that mail came in or was left in the inbox ("Cron Email Parser executed in 0.16 seconds. Processed: 0 email(s), Unprocessed: 2 email(s)"), and the mail queue and email parser wrote one every minute while no mail server was set up. Neither does now. Each email is still a ticket or a reply, one that can't be is still left flagged and unread in the inbox, and an email that fails is still logged, once. With no mail server set up, Maintenance > Cron says so instead. The Mail Queue, Ticket SLA Monitor, Domain Refresher and Certificate Refresher also no longer log an error each time they run while cron is switched off - Maintenance > Cron says why they stopped, as the email parser already did.
- Assets: a virtual machine can have a vendor - the provider a hosted one or VPS is rented from - with its order reference and date, on the Purchase tab like other assets. Before, only one added from a vendor's page kept its vendor.
- Hosting panels: on a server where Apache hands PHP to PHP-FPM - as HestiaCP, cPanel, Plesk and most hosting control panels set it up - your logo, the favicon, avatars and the photos on contacts, locations, assets and racks didn't load, and the server answered them with an error. They load now. The folders kept private, such as backups and receipts, stay private. Installs made with the install script, which runs PHP inside Apache, were not affected.
- Tickets: a resolved ticket reopened by a reply - on the ticket page, in a bulk reply, from the client portal or through the API - kept its resolved time, and its resolution SLA stayed met, so however long it then stayed open, it was never warned or breached. Each of these now clears the resolved time and starts the resolution SLA again, as a client's emailed reply already did. Found by Mountaineer IT.
- Ticket emails: every email from the client on a ticket that was already open sent the resolution SLA warning again once the ticket was past its warning point. Only an email that reopens a resolved ticket starts the resolution SLA over now. Found by Mountaineer IT.
- Client portal: opening a ticket's Resolve or Close link directly could resolve a ticket that was already resolved, giving it a new resolved time, resolve one whose tasks weren't all done, or close one that wasn't resolved. Resolve now works only on a ticket that isn't resolved yet and has its tasks done, and Close only on a resolved one, as the ticket's page offers them. Found by Mountaineer IT.
- API: a reply could be added to a closed ticket, and a reply could set a ticket to New, Closed or a status that doesn't exist, or resolve it with tasks still open. These are now refused with a message saying why. A status set with a reply also pauses or restarts the SLA clock as it does on the ticket page, and changing a ticket's priority through the API picks its SLA again. Found by Mountaineer IT.
- Merging tickets: with Also move this ticket's replies onto it ticked, the replies moved but their attachments stayed behind on the merged ticket, so the replies showed without their files. The attachments go with the replies now. Found by Mountaineer IT.
- Payments: Charge Saved Card could charge a card twice. A double click on Charge, or two people charging the same invoice at once, made two charges at Stripe and recorded both. A second Charge now waits for the first and then finds the invoice paid, and the same window sent twice is one charge at Stripe. Found by Mountaineer IT.
- Payments: Add Payment checked the amount against the balance shown when the window opened, so a window left open, or two people recording the same payment, could take an invoice past what it owes. It also took a payment of 0 or less, and a payment on a draft or cancelled invoice. The balance is now worked out when you save, and only a sent invoice with something owed takes a payment. Found by Mountaineer IT.
- Payments: a Batch Payment that paid a client's invoices exactly could leave one of them Partial with nothing owed - with two invoices, about one time in four - because the amounts were worked out in fractions of a cent. It's worked out in whole cents now, against what the client owes when you save rather than when the window opened, and a payment of 0 or less is refused. Found by Mountaineer IT.
- Autopay: an invoice with part of it already paid wasn't charged on its due date at all. Autopay now charges what is still owed, read again just before the charge. Found by Mountaineer IT.
- Online payments: an invoice owing less than 1.00 couldn't be paid from its link. The card limit in Admin > Payment Providers also only hid the Pay button - the invoice's payment page still took a card for an invoice over the limit, or one marked non-billable. The page now says the invoice can't be paid online. Found by Mountaineer IT.
- Online payments: the payment page an invoice's link opens never showed why a card was declined, or any other problem, and its button gave no sign of working while a payment went through. The reason now shows under the button until the next try, and the button shows a spinner while it works.
- Emails: with mail sent through a Microsoft 365 or Google sign-in and no SMTP server filled in, a client paying from an invoice's link got no receipt and the paid notification address wasn't told, and the quote notification address wasn't told when a client accepted or declined a quote. Found by Mountaineer IT.
- Recurring invoices: Make Recurring on an invoice with a discount kept the discounted total but not the discount, so the recurring invoice showed no discount and lost it the next time a line was changed. The discount goes with it now. Found by Mountaineer IT.
- Lists: a page number of 0 or less in a list's address - an old bookmark, a link typed by hand - stopped the page part way, with no list. It shows the first page now. A custom date range with a start and no end matched nothing; it now runs on from the start. Found by Mountaineer IT.
- Client portal: a contact signed in to the portal who went to ITFlow's main address was signed out, rather than taken to the portal. Found by Mountaineer IT.
- Custom pages: every form on a page of your own under agent/custom stopped with an error, as the handler loaded a file that is no longer there. Found by Mountaineer IT.
- Maintenance > Cron: a job that stopped on an error - the email parser not reaching the mail server, an RMM sync or alert check that failed - showed as Skipped, as if it had nothing to do, and wasn't counted among the failures at the top of the page. It shows as Failed now, and the email parser's failure says what the mail server answered. Found by Mountaineer IT.
- Mail: with Microsoft 365 or Google mail, the mail queue fetched a new sign-in token for every email it sent once the old one ran out, rather than once. Found by Mountaineer IT.
- Updates: once an install was a hundred or so commits behind, the update check stopped with "Data too long" and the Update page no longer showed what was new. It keeps the newest 100 commits now, and counts them all. Found by Mountaineer IT.
- Restoring from the command line into a database with no settings yet - a new install stopped at the setup wizard, as Moving to a new server has you do - stopped with a time zone error before it began. Found by Mountaineer IT.
- API: a body that isn't JSON - a form post, or none at all - and a limit under 1 or an offset under 0 answered with a server error rather than a message. Deleting a client through the API left its files behind. Found by Mountaineer IT.
- Contacts: Anonymize missed a name with an apostrophe in it (O'Brien) in the logs and in the tickets the contact raised. Found by Mountaineer IT. It also took the first name out of an email address that starts with it before the address itself, leaving the rest of the address showing.
- Assets: moving assets to another client logged "created asset (via transfer)" without the asset's name. Found by Mountaineer IT.
- New client: the duplicate warning took % and _ in the name you typed as wildcards, so a name with them in it could warn of a duplicate that isn't one. Found by Mountaineer IT.
- Admin > Access Modules: the page stopped part way when sorted by a column it doesn't have, and its New Module button, and Edit and Delete on the AI module, went nowhere. Those are gone - modules are built in. Found by Mountaineer IT.
- Tickets: moving a ticket to another client left the old client's watchers on it, so they kept getting its emails. Watchers who aren't on your team or contacts at the new client now come off it, and the ticket's history says how many. Found by Mountaineer IT.
- Leads: clients marked as leads showed up in nearly every list of clients to pick from - new assets, contacts, credentials, documents, invoices, trips, expenses, events, contracts and the rest - and in the client switcher, the report and transaction filters and template use, crowding out the clients you work for. Leads are left out of those now. A lead still shows where it belongs: on its own pages, where anything you add is for it; in a record that's already for it; in the quote pickers, after the clients and marked Lead; and in global search, after the clients and marked Lead. Find the rest on the Leads tab of Clients.
- Across clients: as All Client Docs, it listed assets, credentials and the rest of the IT documentation with IT documentation switched off in Admin > Settings > Modules. It now has only Contacts, Locations and Vendors then, as each client's menu does.
- Email sent with Microsoft 365 or Google sign-in: when the mail server turned down ITFlow's sign-in, the email failed on its From address with "Authentication required" in Maintenance > Mail Queue, as if the address were the problem. It now fails saying the sign-in didn't work.
- Assets: a MAC address field holding a note rather than an address ("see label", say) was cut down to the letters in it that pass for hex - "EE:AB:E" - as soon as the asset was opened for editing, and saved like that. It's now left as it is, as the IP address field already was.
- Card payments: once a client's Stripe customer was deleted in Stripe - or the Stripe keys were changed to another Stripe account, or between test and live - every card payment for that client failed, and only an edit to the database put it right. The portal's card form never loaded, the invoice pay page showed Stripe's error, Charge Saved Card failed, and autopay failed every night. Now when Stripe says the customer isn't there, ITFlow forgets it along with the cards saved on it, which Stripe dropped too. A payment with a new card, from an invoice's pay link or the portal, still goes through. The client is asked to add their card again to save one, agents get a notification, and each recurring invoice whose autopay stopped says why. Reported on the forum.
- Windows: opening one put a focus ring round its X in the corner. Focus now goes to the window itself.
- Tickets: the tickets list and board showed how long ago a ticket's SLA was due, in grey, until cron next marked it breached, and showed the time left on one that had already missed its first response. A ticket past its deadline or that missed a target now says Breached, as the SLA breached view counts it.
- Dashboard: in Open and assigned to you, the SLA, status and last activity didn't line up from one ticket to the next - each row moved them by the width of its own status or time, and by whether it had an SLA. They now sit in columns down the card.
- Messages: archiving, restoring, deleting, favoriting or setting the category of several contacts, clients, assets or products said contact(s), client(s) and so on, an import of network IPs said IP(s), and the message after restoring clients started "You restored". They now say 1 contact, 3 contacts, with the number in bold, like the rest.
- Contacts: the button in the archive window read Arhive.
- Tickets: cancelling Reset the timer still marked the timer as stopped in that browser, so it showed as stopped after a reload while it was still counting.
- Browser tabs: many pages were named after their file - Kb, Ai Providers, Rmm Providers, Sla, Settings Ticket, Profit Loss - and one with & in its name showed &. Each tab now has the name the menu gives the page, and a rack, an instance and a ticket, document or project template show their own name.
- Client menu: a client's Domains count never turned amber or red for domains about to expire or expired, and the Certificates and Licenses counts carried two text colours at once.
- Audit Logs: income was filed as Income or Revenue, and transfers as Transfer or Account Transfer, depending on where they were made, so the Type filter listed each twice. Each now has one name, and licenses and license templates are License and License Template rather than Software. Entries already in the log are renamed when you update. Entries for RMM providers, collation repairs, the demo reset and Undo have their own icons.
- Payments: editing a payment said "Payment edited to amount ... added" in your company's currency rather than the payment's, and its audit log entry didn't say who edited it or which client it was for.
- Invoice links: asking to pay by card when card payments weren't set up went to a page that doesn't exist. It goes back to the invoice and says card payments are not set up.
- Assets: Bulk Action > Delete deleted the ticked assets straight away, without asking first as every other list's Delete does.
- Assets: moving the ticked assets to another client with no client picked moved them to no client at all. It now asks for the client.
- Contacts: Assign Location with no location picked took the ticked contacts' location away. It now asks for the location, as the same action on assets does.