Glossary
Plain-language definitions of Incident Tracker terms, from reports, categories and forms to rights, workflows, Alert Groups, Single Sign-On and SCIM.
On this page
Plain-language definitions of terms used throughout Incident Tracker and this documentation.
Reports#
Append β Adding notes or file attachments to a report that already exists. It adds to the report without changing what was originally written. Learn more
Drafts β Reports you have saved but not yet submitted, so you can finish them later. Only the person who created a draft can see or edit it. Learn more
Measured Unit β An optional extra field on reports for tracking a number, such as hours, miles, or cost. Administrators turn it on in Application Settings. Learn more
Report Actions β The menu inside an open report. You use it to edit the report, add attachments, or delete the report. Learn more
Report Sponsor β An email address linked to a report when it is submitted. The sponsor gets email alerts about activity on that report. Learn more
Organizing Reports#
Assignment (Assigned User) β Giving a report to a specific person to handle. Assignments must be turned on by an administrator, and the assigned person can be sent an alert email. Learn more
Category / Sub-category β Labels that describe what kind of incident happened. A sub-category is a more specific type within a category. Learn more
Form β An extra set of questions added to a report, such as text boxes, drop-downs, and checkboxes. Forms collect details that are specific to certain kinds of incidents. Learn more
Form Assignment β A rule that makes a form appear automatically when a report has a certain category, location, or both. If both are set, both must match. Learn more
Hidden (Locked) Form β A form marked as hidden still shows on the report, but with a lock icon, and its answers cannot be changed. An administrator can unhide it to allow edits. Learn more
Labels β The general name for a report's status, priority, and assignment. They can be set by staff or automatically by a workflow. Learn more
Location / Sub-location / Area-Room β Where an incident happened, in up to three levels. A location is the broadest level, a sub-location is a place inside it, and an area or room is a place inside a sub-location. Learn more
Priority β A label that shows how urgent a report is, such as high, medium, or low. Administrators can rename priorities and give them colors. Learn more
Section Headings β The names used for parts of a report, such as "Location," "People," or "Witness." Administrators can rename them to match their organization's wording, and the change applies everywhere. Learn more
Status β A label that shows where a report is in its life, such as open, pending, or closed. Administrators can rename statuses and give them colors. Learn more
Finding & Analyzing Reports#
Activity Hotspots β A tool that counts incidents by combinations of things like day, location, people, or category. It helps you spot patterns. Learn more
Advanced Search β A search tool that lets you filter reports by many fields at once and by date range. You can also exclude a value using the "NOT" checkbox. Learn more
Days Stale β The number of days since a report was last changed in any way. Use it in Advanced Search to find reports nobody has touched. Learn more
Heatmap β A colored map showing where reports happen most often on a picture, such as a campus map. It only works with forms that include an image map. Learn more
Trending Graphs β Line graphs that show how often a category of report happens over time. You can compare two time periods side by side. Learn more
Users & Access#
Admin Rights β The highest level of access. Administrators can change all site settings and users, and they also have every other right. Learn more
Manager β A person linked to a user as their manager. Each user can have only one manager, and managers can be used in workflows. Learn more
Native Account β A user account created and signed in to directly in Incident Tracker, with its own password. Administrators can reset passwords only for native accounts. Learn more
Restrictions β Limits on what a user can see, such as reports from certain categories or locations. Administrators set them with the padlock icon in Manage Users. Learn more
Rights β Permissions that decide what a user can do, such as submit, view, edit, or delete reports. Some rights include others; for example, Edit Rights include Append Rights. Learn more
User Group β A named group of users, such as a department, so you can manage them together. A user can belong to only one group at a time. Learn more
Automation & Notifications#
Alert Group β A named list of email addresses that receive notifications together. It can include Incident Tracker users and outside email addresses. Learn more
Notification Settings β Rules that decide which Alert Groups get emailed about new reports. Notifications can apply to all reports, or only to certain categories or locations. Learn more
Shoutbox β A message area on the home page where short notes can be shared with all users. Administrators turn it on in Application Settings. Learn more
Trigger Conditions β The details a report must match, such as its category, location, status, or priority, for a workflow to run. Learn more
Workflow β An automatic rule. When a report matches its trigger conditions, it can assign the report, set its status or priority, and send alert emails, including to Alert Groups. Learn more
Sign-in & Integrations#
Account Provisioning β Creating, updating, and disabling Incident Tracker accounts automatically from Microsoft Entra ID, so admins don't have to do it by hand. It can be set up with Microsoft Graph or SCIM. Learn more
API β A way for other software to read your Incident Tracker data automatically, for example to feed a dashboard. A developer connects to it using your API Key and Client ID. Learn more
API Key β A private key, found in Admin > API Settings, that lets software connect to the API on your organization's behalf. Treat it like a password. Learn more
Client ID β The number that identifies your workspace. It's the number right after the domain in your web address once you log in. Learn more
LDAP β A way for users to sign in with their existing Active Directory (company network) account. Learn more
Microsoft Entra ID (Azure AD) β Microsoft's service for managing work accounts. Incident Tracker connects to it for Single Sign-On and for creating accounts automatically. Learn more
Microsoft Graph β A connection to Microsoft that lets Incident Tracker copy users from Microsoft groups into matching Incident Tracker user groups on a schedule. Single Sign-On must be set up first. Learn more
SAML β The technical standard Incident Tracker uses for Single Sign-On. Learn more
SCIM β A standard that lets Microsoft Entra ID send new users, changes, and deactivations to Incident Tracker automatically. Learn more
Sign in with Google β Adds a Sign in with Google button so existing users can sign in with their Google account. It doesn't create new accounts. Learn more
Single Sign-On (SSO) β Lets users sign in to Incident Tracker with their organization's work account instead of a separate password. Existing accounts must be converted to third-party accounts before they can use it. Learn more
Third-party Account β A user account that signs in through an outside service, such as Single Sign-On or Google, rather than an Incident Tracker password. Learn more
Compliance & Records#
Banned List β A list of people who are not allowed at certain locations or activities. Administrators add and remove people by hand. Learn more
Clery β Information for higher education organizations that can be attached to a report. Only administrators can add, edit, or delete it. Learn more
Event Log β A dated list of actions taken in the system, such as logins, report submissions, and account changes. Administrators use it to check who did what, including finding deleted reports. Learn more