Intellect Dictionary A-Z
Use this dictionary as a quick reference for common Intellect terms.
Note: Intellect was previously known as Zaptic. Some older screenshots, exports, URLs, or internal references may still use the name “Zaptic”. In this article, Intellect refers to the current platform experience.
This glossary is designed to help new users, Super Users, Power Users, and operators understand the terminology used across the Portal, App, Intellect University, and training materials.
How to use this dictionaryEach term includes:
| Column | What it means |
|---|---|
| Term | The feature, object, permission, or concept used in Intellect |
| Description | A simple explanation of what the term means |
| Where you’ll see it | The main area of the platform where the term is used |
1. Platform Basics
These terms explain the overall platform, the main user roles, and the difference between the Portal and the App.
| Term | Description | Where you’ll see it |
| App | The operator-facing part of Intellect. It is used to complete tasks, submit reports, raise actions, view assigned work, access guides, search units, and review notifications. | App |
| Instance | A dedicated Intellect environment for a customer, site, or business area. Content, users, data, reports, and configuration live inside an instance. | Platform |
| Operator | A frontline user who completes work in the App. Operators typically complete assigned tasks, start ad hoc tasks, submit reports, raise actions, view guides, and access unit information. | App |
| Portal | The administrative and management side of Intellect. It is used by Super Users, SMEs, managers, and administrators to build content, manage users, maintain data, and review performance. | Portal |
| Power User | A user who oversees task execution and performance on the frontline. Power Users may monitor completion, support operators, and use Boards or reports to drive accountability. | Training, Boards, App |
| Super User | A platform expert who builds, manages, and maintains content in the Portal. Super Users usually support configuration, training, governance, and process optimisation. | Training, Portal |
| User | An individual account in Intellect. Users can belong to teams and have different permissions depending on their role. | Teams |
| User Profile | A user’s personal profile in the App or Portal. It can include name, job title, profile photo, contact details, and training information. | App, Teams |
2. Portal Navigation & Core Areas
These terms describe the main areas users see in the Portal.
| Term | Description | Where you’ll see it |
| Board | A dashboard that displays data captured in Intellect in a visual format. Boards help teams monitor performance, review trends, and track issues or actions. | Boards |
| Data Management | The Portal area where site structures, equipment hierarchies, units, unit types, master data, identification codes, and data attributes are created and maintained. | Portal, Data Management |
| Guides Home | The central Portal area where guides can be created, searched, edited, linked to units or procedures, tagged, and managed. | Portal, Guides |
| Procedure | A folder-like structure that groups related tasks, training modules, guides, reports, and timeline activity. Procedures are often built around use cases such as CIL, Centerlines, Defect Handling, Safety, Quality, or Daily Management. | Procedures |
| Teams | The Portal area where users, teams, permissions, team membership, and training visibility are managed. | Teams |
3. Procedures, Tasks & Flow Building
These terms are used when creating and managing workflows.
| Term | Description | Where you’ll see it |
| Ad Hoc Task | A task that is started manually when needed, rather than appearing from a schedule. Operators can start ad hoc tasks from the + button in the App. | App |
| Conditional Element | A feature used to show or hide content inside a step based on a previous answer. For example, if a user selects “Other”, a text box can appear asking them to explain. | Flow Builder |
| Content | The information, questions, media, or logic that makes up a step in a flow. | Flow Builder |
| Element | A building block used inside a step. Elements can capture data, display guidance, ask questions, show media, control logic, or embed other content. | Flow Builder |
| End Section | A routing destination that ends the current section or flow path. It is commonly used when no further questions are needed. | Flow Builder |
| Flow | A workflow built in Intellect. A flow can be a task, training module, or guide. It is made up of steps and elements. | Flow Builder |
| Flow Builder | The authoring area used to build and configure tasks, training modules, guides, steps, elements, routing, schedules, triggers, statuses, and settings. | Portal |
| Legacy Flow | An older style of workflow authoring. Newer workflows should generally use the current Flow Builder experience. | Flow Builder |
| Multiple Report Subjects | A flow configuration that allows more than one unit type to be used as the report subject for a single flow. This helps reduce duplicate flow configuration. | Flow Builder |
| Preview | A Flow Builder option that shows how a task, training module, or guide will appear to the user before it is published or assigned. | Flow Builder |
| Procedure Timeline | The timeline inside a procedure that shows recent events, reports, comments, status changes, and updates related to that procedure. | Procedures |
| Report Subject | The unit that a report is about. For example, a report subject could be a specific line, machine, product, area, or SKU. | Flow Builder, Reports, Data Management |
| Report Title | The name shown for a submitted report. By default, this is usually based on the flow name, but it can be customised by setting or appending selected answers to the title. | Flow Builder, Reports |
| Routing | Step-level logic that controls where the user goes next based on an answer or a data attribute. Routing can send users to another step, the next step, or the end of a section. | Flow Builder |
| Schedule | A configuration that makes a task or training appear in users’ To Do lists at defined times or intervals. Schedules can be assigned to users or teams. | Flow Builder, To Do List |
| Section | A group of steps inside a flow. Sections help keep workflows organised and can be used for optional or detailed content. | Flow Builder |
| Step | A page or stage within a flow. Each step can contain one or more elements, such as questions, instructions, images, videos, or routing logic. | Flow Builder |
| Subtask | A way to embed one existing task inside another flow. Subtasks help standardise repeatable processes because the same task can be reused in multiple places. | Flow Builder |
| Task | A workflow that users complete in the App or Portal. When completed, a task generates a report. | Procedures, Flow Builder, App |
| Trigger | An automated rule that performs an action when defined conditions are met. Triggers can notify users, create actions, change statuses, mark reports as confidential, or promote reports to guides. | Flow Builder |
| Workflow | A general term for a configured flow, such as a task, training module, or guide. | Flow Builder |
4. Task Elements
These are the elements that can be added into tasks, training modules, and flows.
| Term | Description | Where you’ll see it |
| Confirmation Element | A checkbox-style element used when an operator needs to confirm that something has been done, checked, or understood. | Flow Builder |
| Content Loop | An advanced element that repeats the same set of questions for each item in a list. This is useful for repetitive workflows such as CIL, Centerlines, Changeover, or inspections. | Flow Builder, Data Management |
| Date / Time Element | A capture element that asks the user to enter a date, time, or date and time. It can be used to record when something happened. | Flow Builder, App |
| Dropdown Element | A selection element that lets the user choose one option from a list. Dropdowns are useful when answers need to be standardised. | Flow Builder |
| Embedded Guide | A guide placed directly into a task or training flow so operators can access supporting information without leaving the workflow. | Flow Builder, Guides, App |
| File Upload Element | A capture element that allows users to upload files, such as PDFs, Word documents, Excel files, PowerPoint files, text files, images, or other accepted formats. | Flow Builder, App |
| Image Element | A display element used to show an image to the operator. Images can support visual standards, instructions, examples, or “what good looks like” guidance. | Flow Builder, App |
| Image Select Element | A selection element that lets a user choose from images instead of text options. It is useful when visual selection is clearer than written choices. | Flow Builder, App |
| Link Element | An element that opens a URL. It can be used to link users to web pages, SharePoint documents, videos, external SOPs, or other online resources. | Flow Builder, App |
| Loop Subject | The current item being repeated inside a content loop. The loop subject changes as the loop moves through each item in the selected list. | Flow Builder, Content Loop |
| Multiple Choice Element | A selection element where users choose from predefined options. It can be configured for single-select or multi-select answers. | Flow Builder |
| Number Element | A capture element that asks the user to enter a number. It is often used for checks such as temperature, pressure, speed, quantity, or measurement values. | Flow Builder |
| Signature Element | A capture element that asks the user to sign directly in the App or Portal. It can support sign-off or confirmation requirements. | Flow Builder |
| Text Capture Element | A capture element that allows users to type a response. It can be used for comments, descriptions, explanations, or defect details. | Flow Builder |
| Text Content Element | A display element used to show instructions, information, warnings, or problem statements. It can also display data attributes using the # symbol where supported. | Flow Builder |
| Unit Select Element | A selection element that allows a user to choose a unit from Data Management. It helps link answers, actions, or reports to the right line, machine, product, or other unit. | Flow Builder |
| Video Element | A display element used to show video content in a task, training module, or guide. Videos can support visual instructions or training. | Flow Builder, Guides |
| Yes / No Element | A selection element that asks the user to answer Yes or No. It can be used with routing, conditional logic, or scoring depending on the use case. | Flow Builder |
5. Reports, Actions & Follow-Up
These terms describe what happens once work has been submitted or when follow-up is needed.
| Term | Description | Where you’ll see it |
| Action | A follow-up item assigned to a user or team. Actions are often raised from reports when an issue, defect, or improvement needs someone to investigate or complete work. | App, Reports, Actions, Boards |
| Confidential Report | A report with restricted visibility. Confidential reports are used for sensitive information such as safety incidents, HR-related content, or private assessments. | Reports, Permissions, Triggers |
| Done Tab | The App tab where users can review completed tasks, training, and actions. Completed tasks and training records are shown as reports. | App |
| Report | The record created when a task or training module is completed and synced. A report contains the submitted answers, metadata, status, comments, attachments, and related activity. | Reports, Procedures, Boards |
| Report Status | A label used to track the progress or outcome of a report, such as submitted, pending review, complete, failed, approved, or another custom status. | Reports, Procedures |
| Submission Details | Information shown on a report that helps identify how the report was submitted, such as whether it came from a scheduled task, ad hoc task, or integration. | Reports |
| Task Manager Board | A Board used to track actions, issues, defects, and follow-up work through to completion. | Boards, Actions |
| Timeline | A chronological activity feed that shows events, updates, reports, comments, and status changes. Timelines can exist at procedure, report, or unit level. | Procedures, Reports, Units |
6. Data Management & Hierarchy
These terms relate to master data, unit structure, and the shop floor hierarchy.
| Term | Description | Where you’ll see it |
| Call an Expert | A feature that allows experts to be linked to units so operators can contact the right person for support directly from the App. Contact options can include email, phone, WhatsApp, Teams, or a custom link depending on profile setup. | Data Management, App |
| Centerline | A manufacturing practice used to reduce process variation by checking machine settings or values against defined targets, minimums, or maximums. | Procedures, Data Management, Flow Builder |
| Child Unit / Children | A unit type or unit that sits below another unit in the hierarchy. For example, a machine can be a child of a line. | Data Management |
| Data Attribute | Information stored against a unit in Data Management. Data attributes can be displayed in workflows, used for routing, used in Boards, or used by content loops. Examples include target values, SKUs, line speeds, or machine settings. | Data Management, Flow Builder, Boards |
| Data Attribute Routing | Routing logic based on values stored in Data Management. This can be used to change the path of a workflow depending on the selected unit’s data attributes. | Flow Builder, Data Management |
| Hierarchy | The structure of units and relationships in Data Management. A hierarchy often mirrors the physical shop floor, such as Site > Area > Line > Machine. | Data Management |
| Identification Code | A code assigned to a unit. Identification codes are commonly used for barcode or QR code scanning so the App can identify the correct unit. | Data Management, App |
| Intellect ID | A unique system-generated identifier for a unit or report. Historic exports or screenshots may refer to this as a Zaptic ID. IDs are often used when updating data, linking records, or troubleshooting. | Data Management, Reports |
| Parent Unit / Parents | A unit type or unit that sits above another unit in the hierarchy. For example, a line can be the parent of a machine. | Data Management |
| QR Code Scanning | App functionality that allows users to scan a QR code or barcode to find unit-specific content, start relevant tasks, or open a unit page. | App, Data Management |
| Unit | A specific item in Data Management. A unit can represent a physical object, such as a machine, line, area, or asset, or a reference item, such as a SKU or Centerline step. | Data Management |
| Unit Page | The App page for a selected unit. It can show timeline activity, about information, tasks, reports, and guides linked to that unit. | App, Data Management |
| Unit Type | A folder-like grouping of units in Data Management. Examples include Lines, Machines, Products, Areas, SKUs, or Centerline Steps. | Data Management |
7. Teams, Permissions & Access
These terms explain how users, teams, and permissions are managed.
| Term | Description | Where you’ll see it |
| AI Functionality Permission | A permission that gives a user access to AIKA. On its own, this allows the user to ask AIKA questions based on guides available in the instance. | Teams, Permissions, AIKA |
| AI Reports Access Permission | An additional AI permission that allows AIKA to use completed reports as well as guides when answering a user’s questions. | Teams, Permissions, AIKA |
| Boards Permission | A Portal permission that gives a user access to the Boards tab and the boards available in the instance. | Teams, Permissions |
| Collaborator | A user with edit access to a specific procedure. Collaborators can build and maintain content within that procedure and can usually invite other collaborators. | Procedures |
| Company Tab | The Teams area that lists users invited to the instance. It helps admins review users, permissions, team membership, and user status. | Teams |
| Confidential Reports Permission | A permission that allows a user to view confidential reports and mark or unmark reports as confidential. | Teams, Permissions, Reports |
| Data Management Permission | A Portal permission that allows a user to access Data Management and create or update unit types and units. | Teams, Permissions |
| Procedure Admin Permission | A Portal permission that gives full edit access across all procedures by automatically adding the user as a collaborator to all procedures. | Teams, Permissions, Procedures |
| Procedure Collaborator | A user who has edit access to a specific procedure. This is different from Procedure Admin, which grants wider access across procedures. | Procedures |
| Procedure Management Permission | A Portal permission that allows users to access the Procedures and Guides tabs, create procedures, and build tasks and training where they have access. | Teams, Permissions |
| System Admin Permission | An admin permission that grants access to all main Portal areas and team administrator privileges across all teams. | Teams, Permissions |
| Team | A group of users. Teams are commonly based on role, department, line, shift, or responsibility. Assigning teams to procedures determines which users can access that content in the App. | Teams, Procedures, App |
| Team Admin | A user who can manage membership of a specific team. Team admin access is separate from general User Management permission. | Teams |
| Training Admin | A team-level role that allows a user to view training records for members of the teams they administer. | Teams, Training |
| User Management Permission | A Portal permission that allows access to the Teams tab and visibility of users and teams. Users with this permission who are also team admins can add or remove users from the teams they administer. | Teams, Permissions |
8. Training
These terms relate to training setup, completion, and compliance tracking.
| Term | Description | Where you’ll see it |
| Training | A workflow used to train or assess users. When completed, training creates a training record against the user. | Training, Procedures |
| Training Compliance | A measure of how much assigned training has been completed by a user or team. It is usually shown as a percentage. | Training, Teams |
| Training Matrix | A view of training completion across users and training modules. It helps teams track compliance, overdue training, and completion status. | Training |
9. Guides, Knowledge & AI
These terms relate to guidance, knowledge sharing, and AI-assisted support.
| Term | Description | Where you’ll see it |
| AI Flow Builder | An AI-assisted authoring feature that helps create flows, tasks, or guides from existing content such as uploaded documents, guides, reports, or files. | Flow Builder, AIKA |
| AIKA | AIKA stands for AI Knowledge Assistant. It helps users find answers from the knowledge available in their instance, such as guides and, where permissions allow, completed reports. | AIKA, Portal, App |
| Answer History | A feature that allows operators to view recent previous answers for a question while completing a task. This helps provide context when carrying out repeated checks. | App, Task Execution |
| Guide | Supporting knowledge that helps users complete work correctly. Guides can include SOPs, OPLs, videos, images, work instructions, links, or other documentation. | Guides, Procedures, Data Management, App |
10. Tags, Boards & Integrations
These terms relate to organising content, analytics, integrations, and advanced configuration.
| Term | Description | Where you’ll see it |
| Answer Tag | A label applied to specific answers within dropdown or multiple choice questions. Answer tags help make data easier to group, filter, analyse, and use in Boards or integrations. | Flow Builder, Boards, Integrations |
| Cluster | A way to group and organise ad hoc work in the App so operators can find the right tasks more easily. Clusters are usually configured using tags. | App, Flow Builder |
| Flow Tag | A tag applied to a flow. Flow tags help identify and group flows for reporting, Boards, integrations, and organisation. | Flow Builder, Boards, Integrations |
| Huddle Board | An interactive board used to support shift handovers, daily management meetings, and collaborative problem-solving. Teams can review issues, actions, and operational information together. | Boards |
| Integration | A connection between Intellect and another system, such as ERP, MES, SCADA, IoT, QMS, DMS, LMS, Power BI, or another data platform. Integrations can send data into Intellect, send data out of Intellect, or keep information synchronised. | Integrations |
| Power BI | A data visualisation tool used to create dashboards and embed Boards into Intellect. | Boards |
| Procedure Tag | A tag applied to a procedure to help group, search, filter, or organise related procedures. | Procedures |
| Tag | A label used to organise content or support reporting and integrations. Tags can be applied to procedures, guides, flows, elements, and answers depending on the use case. | Procedures, Guides, Flow Builder, Boards, Integrations |