October 2026

■ New feature

Clock-out confirmation, now available to all customers

Available in: Web portal · TrackTik Guarding Application · TT-Shift · All customers

Note: Only available for Site Licenses and site schedules. Guards need a scheduled shift, and it isn’t available at zone level.

Release summary

Overview

Who benefits most: Operations managers and account admins who need a record of each guard acknowledging the end of their shift, for accountability, audits or compliance.

What drove the change: Clock-out confirmation first shipped in December 2025, but turning it on meant raising a request with Customer Success. That step is gone.

What's new

What it does

Guards acknowledge the end of their shift before they can clock out. Admins set it up in the portal:

• Acknowledgment Method: Signature capture (guard signs on screen before agreeing) or No confirmation required (no signature).
• Agree or Disagree: guards check the confirmation prompt, sign if a signature is required, then select Agree or Disagree. If they disagree, they’re asked for a reason, which shows on the Daily Activity Report.
• Custom Text Prompt (Boilerplate): the message guards read at clock-out, up to 500 characters. Leave it blank to use the default message.
• Global, Region or Site level: Site overrides Region, and Region overrides Global. For example, if a region requires a signature but one site is set to No confirmation required, guards at that site don’t sign.
• In the mobile apps: TrackTik Guarding Application and TT-Shift. Guards see the prompt when they select Clock Out, after any shift-end steps. Changes reach devices within 24 hours, when a guard starts a new shift or refreshes shift data.
• In the Daily Activity Report: a Clock-Out Confirmation section shows the confirmation text, the acknowledgment (Yes / No), the decline reason if there is one, and the signature.
• Who can see it: users need Scheduling enabled plus the View Clock Out Confirmation permission (under View Scheduling Reports). Without them, confirmation data stays hidden even when the feature is on.
• Turned off (Require Confirmation set to No): the mobile apps ignore all saved settings and guards see no prompt.

Why it matters

Customers get a recorded acknowledgement, signed if they want it, from each guard at the end of every shift. When a guard disagrees, the reason is on file. And any admin can now turn it on without waiting on a support request.

How to access it

Site level: open the site > Settings > Clock-Out Confirmation Settings

The same settings are available at Region and Global level: Settings > General > Clock-Out Confirmation Settings

Screenshot 01

Clock-Out Confirmation Settings at site level: open the site > Settings > Clock-Out Confirmation Settings.

Screenshot 03

Acknowledgment Method: Signature capture or No confirmation required.

Screenshot 04

TrackTik Guarding Application: guards select Clock Out & Sign Out (or Clock Out & Stay Signed In), then confirm the prompt.

Screenshot 05

Guards sign, select Done, then choose Agree or Disagree.

Screenshot 06

TT-Shift: guards confirm, sign, then select I Agree or I Disagree.

Screenshot 07

To open the report: Site > Operation Reports > Summary By Shift > View.

Screenshot 08

The Clock-Out Confirmation section in the Daily Activity Report (Site > Operation Reports > Summary By Shift > View).

Screenshot 09

The View Clock Out Confirmation permission, under Scheduling > View Scheduling Reports.

Rollout and upgrade

■ New feature

Separate Create and Edit permissions for customers, positions and zones

Available in: Web portal · Admin Portal Roles · All customers

Release summary

Overview

Who benefits most: Account admins who manage roles, and organizations where managers or supervisors keep site and client records up to date but shouldn’t be setting up new ones.

What drove the change: Built in response to customer feedback. Managers who only needed to update existing records, like a site contact’s phone number or email, could also create sites because the permission bundled both. Sites were getting created that shouldn’t have been.

What's new

What it does

Three combined permissions in the Customer folder are now six separate ones:

• Create / Edit a Customer → Edit a Customer and Create a Customer
• Create / Edit Positions → Edit Positions and Create Positions
• Create or Edit a Customer Zones → Edit a Customer Zones and Create Customer Zones

How they work together

• Create includes Edit. A role with Create can still edit existing records, even if Edit is unchecked.
• Edit only: users can open and edit existing sites, clients, positions and zones. Create options are hidden (for example Add Zone and Create a Position), and so are Duplicate and delete on positions.
• Neither: users can’t create or edit that record type. Whether zones are visible at all is still controlled by View Customer Zones.
• Admin Portal Roles only. Staff Portal Roles and Client Portal Roles don’t change.

Why it matters

Admins can match access to the job. People who maintain existing records, like updating a contact number or adjusting a position, no longer get the ability to create new sites, positions or zones. That means fewer incorrectly created records to clean up.

How to access it

Settings > Roles & Security > Roles/Permissions > Admin Portal Roles > [select role] > Permission > Customer

Screenshot 10

The Customer folder before and after: each combined permission is now a separate Edit and Create permission.

Where each permission shows up. A blue outline marks what shows with Edit (Create includes Edit); an orange outline marks what needs Create and is hidden for edit-only roles.

Screenshot 11

Site > Edit: the Edit button on the site record shows with Edit a Customer.

Screenshot 12

Sites (Client) > Site List > New Site: hidden for roles with Edit a Customer only.

Screenshot 14

Site > Settings > Positions > Edit: edit-only roles can edit existing positions. Duplicate and delete need Create Positions.

Screenshot 15

Zone > Edit: the Edit tab on the zone shows with Edit a Customer Zones.

Screenshot 16

Sites (Client) > Site Zones (Groups) > Add Zone: hidden for roles with Edit a Customer Zones only.

Screenshot 17

Zone > Positions > Create a Position: hidden for roles with Edit Positions only.

Screenshot 18

Zone > Positions > Edit: same as at site level. Duplicate and delete need Create Positions.

Rollout and upgrade

■ New feature

Create contact and Edit contact permissions

Available in: Web portal · Admin Portal Roles and Staff Portal Roles · Sites and Zones · All customers

Release summary

Overview

Who benefits most: Account admins who manage roles, and organizations where some staff need to look up site and zone contacts without adding or changing them.

What drove the change: Until now, site and zone contacts weren’t covered by a permission. Anyone who could open a site or zone could add and edit its contacts, and admins had no way to limit that.

What's new

What it does

Two new permissions in the Customer folder of Admin Portal Roles and Staff Portal Roles control who can add and change site and zone contacts:

• Create contact: shows the Create Contact button on a site’s Other Site Contacts / Addresses tab and on a zone’s Contacts tab. Without it, the button is hidden.
• Edit contact: lets users change existing site and zone contacts. Without it, they can still see contacts but can’t edit them.

How they work together

• They work independently. Create contact doesn’t include Edit contact, and Edit contact doesn’t include Create contact. A role that should do both needs both checked.
• Same rule at site and zone level. One pair of permissions covers contacts on sites and on zones.
• On by default. Every existing Admin and Staff Portal role gets both permissions turned on, so nobody loses access on release day.

Why it matters

Admins decide who maintains contact records. For example, let supervisors correct a contact’s phone number or email without letting them add new contacts, or make contacts read-only for roles that only need to look them up. Fewer unexpected changes to contact details other people rely on.

How to access it

Permissions: Settings > Roles & Security > Roles/Permissions > Admin Portal Roles (or Staff Portal Roles) > [select role] > Permission > Customer

Site contacts: open the site > Other Site Contacts / Addresses > Create Contact

Zone contacts: open the zone > Contacts > Create Contact

Screenshot 19

The Customer folder before (left) and after (right). Create contact and Edit contact are added, checked by default. Same folder under Staff Portal Roles.

Screenshot 20

Site contacts: Create Contact appears only with the Create contact permission. Edit on an existing contact needs Edit contact.

Screenshot 21

Zone contacts: the same two permissions apply.

Rollout and upgrade

■ New feature

Permission to delete Activity Feed records

Available in: Web portal · Admin Portal Roles · Live Dashboard (main, site and zone) · All customers

Release summary

Overview

Who benefits most: Account admins who manage roles, and operations teams who rely on the Activity Feed as the record of what happened on site — who clocked in, who clocked out and when — for audits, payroll and billing questions, or client disputes.

What drove the change: Deleting an Activity Feed record is permanent and takes one click, and there was no way to stop a role from doing it. Records could be removed by accident, or by people who shouldn’t be editing the record of events.

What's new

What it does

Adds a new permission, Delete Event, in the Dashboard folder of Admin Portal Roles that controls whether a role can delete Activity Feed records:

• On (default): users see Delete next to each record’s timestamp and can permanently remove it, same as today.
• Off: users can still see the Activity Feed but can’t delete records from it. The Delete option is hidden.
• Everywhere the Activity Feed shows: the main Live Dashboard, and the Live Dashboard at site and zone level.

Why it matters

The Activity Feed is often what admins and clients point to when something is questioned. Admins can now make sure only the right people can remove entries from it, so records don’t disappear by accident or without oversight.

How to access it

Turn the permission on or off: Settings > Roles & Security > Roles/Permissions > Admin Portal Roles > [select role] > Permission > Dashboard > Delete Event

Where the Delete option appears (next to the timestamp on each Activity Feed record):

• Dashboards > Live Dashboard > Activity Feed
• Sites (Client) > Site List > [select site] > Security & Patrol > Live Dashboard
• Sites (Client) > Site Zones (Groups) > [select zone] > Security & Patrol > Live Dashboard

Screenshot 22

Delete sits next to the timestamp on each Activity Feed record. It only shows for roles with the Delete Event permission.

Screenshot 23

The same Activity Feed on a site’s Live Dashboard: Sites (Client) > Site List > [site] > Security & Patrol > Live Dashboard.

Screenshot 24

At zone level: Sites (Client) > Site Zones (Groups) > [zone] > Security & Patrol > Live Dashboard. Delete follows the same permission.

Screenshot 25

The Delete Event permission in the Dashboard folder. On by default; uncheck it to stop a role from deleting Activity Feed records.

Rollout and upgrade