1 WHAT IT IS
This glossary defines the core terms and concepts you will encounter across the Bizzmine platform — from workspaces and collections through to workflows, documents, permissions, and integrations. It is organised by subject area so you can quickly find the terminology relevant to the part of the platform you are working with. The final section highlights common distinctions that are easy to conflate.
2 WHO IT'S FOR
Audience: Everyone Reading time: 15 min
Useful for anyone new to Bizzmine — end users orienting themselves to the interface, and admins who need precise language when configuring collections, workflows, and permissions.
3 PREREQUISITES
No prerequisites.
4 HOW IT WORKS
General structure
Bizzmine organises work along a clear hierarchy: Workspace → Dashboard → Widget → Collection → Record
| Term | Meaning |
|---|---|
| Workspace | A top-level working context. Users switch workspaces to reach the dashboards, navigation items, and information relevant to that area of work. |
| Dashboard | A workspace page that groups related widgets. |
| Widget | A configurable dashboard component that displays information or provides an entry point to work with it. |
| Collection | A configurable, structured source of information — similar to a database table — for a business process, document set, or other data domain. |
| Record | One saved entry in a collection. Bizzmine may also call it an instance, registration, or, in document contexts, a document. |
| Form | The screen layout used to create, read, or edit a record. |
| Settings area | The administrative area where collections, forms, workflows, access, workspaces, widgets, and system options are configured. |
| User interface / workspace area | The operational area where users complete tasks, work with records, view dashboards, and receive notifications. |
Collections, records, and data design
| Term | Meaning |
|---|---|
| Data collection | A collection for operational records such as incidents, audits, inspections, risks, or actions. In configuration it may be called a static collection. |
| Workflow collection | A collection whose records follow a defined workflow with steps, actions, assignments, and status. |
| Controlled-document collection | A collection designed for document lifecycle management, including publication, distribution, revision, and archival. |
| Collection properties | The high-level settings that define a collection's identity, behaviour, and available features. |
| Data design | The configuration of a collection's data structure: its fields, types, relationships, and related business rules. |
| Field | A defined piece of data in a collection, such as title, date, owner, status, or score. |
| Form field | A field as it appears on a particular form, including its layout and on-screen behaviour. |
| Caption | The user-facing label shown for a field, form element, or configurable item. |
| Bookmark | A stable, non-translated technical identifier for a field. Useful in formulas, scripting, integrations, and templates; not normally the label users see. |
| Hint | Guidance displayed with a field to help users supply the right information. |
| Placeholder | Example or prompt text shown inside an empty field. |
| Required field | A field that must have a value before the record can be saved or progressed. |
| Read-only field | A field that can be viewed but not edited in the current context. Workflow state, permissions, relations, formulas, and scripting can make a field read-only. |
| Default value | A value supplied automatically when a new record or field is created. |
| Field value / list value | One of the permitted options for a choice field such as a dropdown, radio group, or checkbox group. |
| Field type | The kind of data and control used for a field. |
| Alphanumeric field | A text field for letters, numbers, and other short text. |
| Numeric field | A field for numbers; it can be configured with minimum/maximum values, decimals, prefixes, suffixes, and formatting. |
| Memo field | A longer text field, optionally with rich-text editing. |
| Email field | A field intended to contain an email address. |
| Date, time, and date-time picker | Fields for entering a date, a time, or both. |
| Time range | A field for a start and end time. |
| Checkbox | A true/false choice. |
| Radio group | A set of options from which one value is selected. |
| Combobox | A drop-down selection field. |
| Enum list | A predefined, system-managed list of values, such as a status list. |
| Hyperlink | A field that stores or presents a web link. |
| Canvas | A field on which a user can draw or annotate, if drawing is allowed. |
| PDF file | A field/control for a PDF document. |
| Controlled-document field | A field/control that holds the controlled file and its document-lifecycle settings. |
| Macro button | A configurable form button with a caption and/or icon that performs a predefined action. |
| AI button | A form control that can invoke configured AI assistance for designated source and target fields. |
| Organisation-chart selector | A control for choosing people or organisational units such as departments, functions, or roles. |
| Mailing-list field | A control for configuring or selecting email recipients. |
| Form element | A layout-only component on a form, such as a panel, title bar, text block, image, container, list, or button. |
| Panel / container | A layout element used to group form elements visually. |
| Accordion | A collapsible section of a form that groups related fields. |
| Grid | A tabular display, often used for a list of linked records or a report. |
| Card view | A visual list presentation that displays records as cards rather than rows. |
| Stack / edit in stack | Opening a linked record in an additional on-screen view rather than leaving the current form. |
| Form template | A reusable starting layout or definition used when creating a form. |
| Data-design inheritance | Reusing or copying configuration from a collection, folder, or existing data design rather than defining it from scratch. |
Relationships, lookups, and subsets
| Term | Meaning |
|---|---|
| Linked collection | A relationship that lets a record refer to information in another collection. |
| Lookup | A selection mechanism for choosing an existing related record. |
| Linked record | The actual record selected through a relationship or lookup. |
| Relational link | A live reference to another record. The non-link data is normally read-only because it reflects the source record. |
| Historical link | A relationship that stores a copy of related data at the time it is linked. Depending on its setup, that copy can be edited. |
| 1×1 relation | A relationship that permits one linked record. |
| 1×N relation | A relationship that permits multiple linked records, commonly shown as rows in a grid. |
| Cross-link / cross-linked field | The configuration that carries data on the relationship itself, rather than on either source record. |
| Reversed relation | A relationship displayed from the opposite direction. It is presented as non-editable. |
| Sub-collection | A configured, filtered subset of records from a collection. It does not create a separate independent data store. |
| Collection view | A configured way to expose a collection or subset of its records, including its display and selection context. |
| List | A configured list definition for presenting or selecting collection data. |
| External list | A list that is maintained or supplied outside the collection's normal data design and can be selected or managed separately. |
| List source | The collection or data source from which a list obtains its values or records. |
| Collection mapping | A mapping that transfers or aligns fields between source and destination collections or processes. |
| Fixed value | A mapped value explicitly set in configuration rather than copied from a source field. |
Forms, searches, reporting, and automation
| Term | Meaning |
|---|---|
| Search | A configured way to find collection records using conditions and fields. |
| Search filter | A saved collection-specific filter definition; it can be offered to users as a reusable query. |
| Filter | Criteria that reduce a list, grid, report, or search result to matching records. |
| Condition | A rule in a search, formula, workflow, or script that evaluates whether something is true. |
| Report | A formatted presentation of collection information. |
| Report designer | The configuration area for selecting fields, layout, grouping, and display options for reports. |
| Word report | A report generated into a Word-document format from configured data and templates. |
| Document template | A reusable file or layout used to generate a document from Bizzmine data. |
| Formula | A configured calculation that automatically derives a field value from other data. |
| Formula tag | A referenced field or token available when constructing a formula. |
| Scripting | Rules that dynamically change form behaviour or values. In some Bizzmine models this is called evaluation. |
| Evaluation | A configured scripting rule that can, for example, set values, hide a field, make it required, or change editability. |
| Visibility rule | A rule that shows or hides a field or form element based on data or context. |
| Validation | A rule or check that confirms entered data meets requirements. |
| Import | Bringing structured information or configuration into Bizzmine from an external file or source. |
| Import mapping | The configuration that connects incoming columns or values to Bizzmine fields. |
| Bulk export | Exporting multiple records at once, subject to permission. |
Workflow, tasking, and monitoring
| Term | Meaning |
|---|---|
| Workflow | The configured sequence of steps and rules that takes a record through a business process. |
| Workflow editor / designer | The visual configuration screen for creating workflow steps, gateways, actions, and transitions. |
| Workflow version / flow version | A saved version of a workflow definition. |
| Workflow status / flow status | The current position and progression of a record in its workflow, shown as a status or visual flow. |
| Step | A stage in a workflow at which people perform work, review information, make a decision, or trigger an outcome. |
| Start step | The first step when a workflow starts. |
| Normal step | A standard operational step in a workflow. |
| End step | The final step that completes a workflow path. |
| Gateway | A decision point that routes a record along one of several workflow paths. |
| Assessment step | A step used for evaluation or assessment. |
| Publication step | A step that publishes a controlled document or makes an item officially available. |
| Distribution step | A step that distributes information or documents to configured recipients. |
| Read and understood | A workflow action that asks recipients to confirm they have read and understood assigned content. |
| Transition / workflow action | An available action that moves a record from one workflow step to another, often with validation, assignment, notifications, or signatures. |
| Task | A unit of work generated for a user by a workflow, revision, training, or other process. |
| Task list | A view or widget that shows the tasks a user needs to act on. |
| Executor / assignee | The person, role, department, or function assigned to perform a task or workflow action. |
| Assignment | The act and configuration of allocating a task, step, or action to one or more executors. |
| Due date | The time by which a task, action, or revision is expected to be completed. |
| Reminder | A scheduled prompt that draws attention to an upcoming or overdue item. |
| Notification | A configured or in-app/email message triggered by an event, schedule, or workflow action. |
| Notification template | The reusable content and recipient setup for a notification. |
| Mail template | A reusable email subject/body definition used by a collection or workflow. |
| Mail mapping | Configuration that maps collection fields to values used in a generated email. |
| Forward task | Reassigning or passing an existing task to another eligible user. |
| Execute on behalf of | Performing an action for another user when the configuration and permissions permit it. |
| Restart workflow | Starting the record's workflow again from the configured point. |
| Veto | An explicit negative/stop outcome on a workflow step that prevents the normal path from continuing. |
| Monitor | The view that shows a record's workflow steps, task activity, action dates, and cancellation/veto state. |
| Scheduler | A component or service that displays or manages planned and recurring work. |
| Periodic task | A recurring activity generated at a configured interval. |
| Periodic revision | A recurring, scheduled review/revision process for a collection or controlled document. |
| Fallback executor | The alternate assignee used if the normal assignment cannot be fulfilled. |
Documents, lifecycle, and auditability
| Term | Meaning |
|---|---|
| Controlled document | A document managed with governance controls such as workflow, approval, publication, distribution, revision, and access management. |
| Document properties | Metadata and settings attached to a controlled document. |
| Document tree | A hierarchical browser for finding and navigating documents. |
| Folder | A container used to organise documents and, where configured, inherit or copy document-related settings. |
| Draft | A document or record version that is being prepared and is not yet published. |
| Published document | The official released version of a controlled document. |
| Archive | The retained historical store of a document's earlier versions or archived copies. Accessing archives is a distinct permission. |
| Archived PDF | A preserved PDF version of a document, potentially with its own watermark setting. |
| Trash can | The recoverable holding area for deleted records or documents. It is distinct from the archive. |
| Delete to trash can | Removing an item from normal use while keeping it recoverable. |
| Recover from trash can | Restoring an item that was moved to the trash can. |
| Revision | A controlled change cycle for a document or other governed record. |
| Version | A specific saved iteration of a record or document. |
| Minor revision / minor version | A revision that creates the configured minor version increment. |
| Major revision / major version | A revision that creates the configured major version increment. |
| Revision task | A task generated to have a record or document reviewed and revised. |
| Change request | A permission-controlled request to change a managed item. |
| Compare document | Comparing versions or variants of a document to identify differences. |
| Document translation | Producing or managing a language-specific variant of a document. |
| Watermark | Text or a visual overlay applied to generated, published, or archived PDFs to communicate status or ownership. |
| Electronic signature | A formal signing control used to capture an authorised approval or acknowledgement, often as part of a workflow action. |
| Signature on save / on completion | A configuration that requires electronic signing when saving a record or completing a workflow action. |
| History | The record-level event log: what happened, who did it, and when. |
| Track changes | The detailed, permanent before-and-after history of field-level changes. |
| Audit trail | The evidence created by history, track changes, signatures, and related event logs. |
| File history | The version/change history for an attached or controlled file. |
| Lock | A temporary control that prevents conflicting edits to a record while it is being worked on. |
| Lock management | The administrative view for inspecting and resolving collection locks. |
Workspaces, dashboards, and widgets
| Term | Meaning |
|---|---|
| Workspace item | A configurable item that appears in workspace navigation. It can be a dashboard, widget, collection entry point, external link, or separator. |
| Separator | A non-clickable workspace-navigation divider used to group items. |
| External link | A workspace item that opens a configured web address. |
| New record item | A workspace item that opens a configured collection to create a new record. |
| Collection-list widget | A widget that displays collection records, usually with search, filtering, grid actions, and record creation/opening. |
| Collection-info widget | A summary widget that presents configured information about a collection or its records. |
| Chart widget | A visual widget that presents data as a chart. |
| Document-tree widget | A widget for browsing documents in a hierarchy. |
| Task-list widget | A widget that presents actionable tasks. |
| Scheduler widget | A widget for scheduled or periodic activity. |
| Content-editor widget | A configurable rich-content area on a dashboard. |
| HTML widget | A widget for presenting configured HTML content. |
| RSS widget | A widget that displays information from an RSS feed. |
| Copilot widget | A dashboard entry point for configured AI assistance. |
| Log widget | A view of general, security, activity, integration, or service logs. |
| API keys widget | The administrative feature for managing API access keys. |
| Licences widget | The administrative feature for viewing licence information and availability. |
| Language-management widget | The feature for managing the application's language/translation configuration. |
| Qualification matrix widget | A widget that compares required and held qualifications, skills, or functions. |
People, organisation, access, and administration
| Term | Meaning |
|---|---|
| User | A named person with access to Bizzmine. |
| External user | A user who accesses a specifically shared form, portal, or item rather than the full standard workspace. |
| Anonymous form / external form | A form that can be made available through an external or public-style access route, subject to its configuration. |
| Organisation chart | The managed structure of departments, functions, roles, and users used for selection, assignment, and permissions. |
| Department | An organisational unit in the organisation chart. |
| Function | A job function or position in the organisation chart. |
| Role | A role in the organisation chart; it can be used to group access and assignments. |
| Permission | A granted ability to read, create, edit, manage, perform workflow actions, or access governed functions. |
| Permission set / permission configuration | The configured access rules for a collection, document, workspace item, or other secured feature. |
| Manager permission | Access that lets a person manage the configured object or collection according to the assigned rights. |
| Read permission | Access that permits viewing without necessarily allowing change. |
| Access type | A high-level setting such as access for everybody or nobody, combined with selected organisation-chart entries where applicable. |
| Collection manager | A user recognised as having management responsibility for a collection in the current context. |
| Owner / administrator | Elevated user types that can configure broader system or account settings. |
| Confidential | A designation used to restrict or signal sensitive workspace or collection content. |
| Usage overview | An administrative view of where a configured object or data structure is used. |
| Permission history | An audit view of changes to permissions. |
| Active, inactive, hidden | States that determine whether an item is usable, disabled, or not shown in normal navigation. |
Training, competency, and assessments
| Term | Meaning |
|---|---|
| Training app | A configured training module or application that manages training-related processes. |
| Training | A defined learning activity or requirement. |
| Training session | A scheduled instance of a training activity. |
| Lesson | A constituent part of a training session. |
| Trainer | A person assigned to deliver or manage training. |
| Skill | A capability that can be associated with a user, function, training, document, or qualification. |
| Skill grade | The level or rating assigned to a skill. |
| Qualification | A recognised competency or entitlement associated with a user. |
| Qualification certificate | The evidence or certificate associated with a qualification. |
| Qualification category | A grouping used to organise qualifications. |
| Qualification matrix | A view that compares people, functions, roles, skills, or qualifications against configured requirements. |
| Renew qualification | Extending or refreshing a qualification that is expiring or requires review. |
| Exam | A configured test used to assess knowledge or competency. |
| Exam session | A scheduled or assigned instance of an exam. |
| Exam creator | The control/configuration used to create an exam. |
| Exam score evaluation | The rules or outcome used to assess exam scores. |
| Question and answer | An exam item and its possible or recorded answer. |
| Assessment | An evaluation activity or workflow step. |
| Exam subscription | The enrolment of a user in an exam or examination process. |
System configuration and integrations
| Term | Meaning |
|---|---|
| General settings | Account-wide application options. |
| Regional settings | Language, locale, date, time, and similar regional preferences. |
| Theme | A reusable visual style configuration for the application or forms. |
| Authentication settings | How users authenticate to Bizzmine. |
| Mail settings | System-level email delivery settings. |
| Microsoft 365 online editing | Configuration for working with supported Microsoft 365 document-editing capabilities. |
| Media support | System options governing supported media handling. |
| Firewall settings | Configuration relevant to permitted network access and connectivity. |
| API key | A credential used by an external integration to authenticate with Bizzmine APIs. |
| Integration | A configured connection or data exchange with another system. |
| AI agent | A configured AI capability attached to a collection or process. |
| AI source field / target field | Fields selected as the information AI reads from or writes to. |
| AI validation | A review/acceptance step for AI-generated field values when that configuration is enabled. |
| AI agent session | A running AI interaction associated with a form or record; it can temporarily lock the item. |
| Translation / language | Management of multilingual labels, content, and document variants. |
| System log | Operational, security, activity, directory, or conversion log information used for administration and troubleshooting. |
Common distinctions
| Do not conflate | Difference |
|---|---|
| Workspace / dashboard / widget | A workspace is the top-level context; a dashboard is a page inside it; a widget is a component on that page. |
| Collection / record / form | A collection defines a class of data; a record is one stored item; a form is the screen used to work with that item. |
| Data design / form design | Data design defines what information exists; form design determines how it is laid out and interacted with. |
| Static / workflow / controlled-document collection | These are distinct collection behaviours: ordinary structured records, process-driven records, and governed document lifecycles. |
| Archive / trash can | Archive retains historical document versions; trash can holds deleted items that may be recovered. |
| History / track changes | History records events; track changes records before-and-after field-level changes. |
| Revision / version | A revision is the governed change process; a version is a specific saved iteration. |
| Task / notification / reminder | A task requires work; a notification communicates an event; a reminder prompts attention at a configured time. |
| Linked collection / sub-collection | A linked collection connects records across two collections; a sub-collection is a filtered subset of one collection. |
| List / collection view / collection-list widget | A list is a configured data presentation/selection definition; a view exposes a collection/subset in a context; the widget is the dashboard component that shows it. |
| Permission / role / manager | A permission is an allowed action; a role is an organisational grouping; manager denotes an assigned management-level access responsibility. |
| Formula / scripting (evaluation) | A formula calculates a value; scripting/evaluation changes data or behaviour according to rules. |
5 RELATED ARTICLES
No questions yet.