> ## Documentation Index > Fetch the complete documentation index at: https://docs.blinkops.com/llms.txt > Use this file to discover all available pages before exploring further. # Key Concepts > Essential concepts and terminology you need to understand before building workflows in Blink. To use the Blink platform, it is helpful to know **key concepts** and **terminology**.
| **Key Concept** | **Definition** | | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Action** | An `Action` is a built-in feature on the Blink platform. It is the functional element of a Step. Actions enable you to perform operations on remote systems. Typical Actions on AWS include *Create a user* and *Delete a user*, and on Github *Create pull request* and *Create user repo*. See [Actions](/docs/workflows/building-workflows/actions) for more details. | | **AI Agent** (also known as Agents) | Agents are a new automation capability within the Blink platform that enables AI reasoning (human-like thinking). | | **Builder Copilot** | `Builder Copilot` is an innovative feature that helps users to create custom Workflows from the ground up, using the advanced capabilities of generative AI to enhance and streamline workflows within the Blink workflow editor. See [Builder Copilot](/docs/builder-copilot) for more details. | | **Cases** | The `Cases` feature allows you to effectively handle security incident investigations by providing detailed information and logs in one place on a single dashboard. This, in turn, allows for quicker responses to security incidents as soon as they are detected or identified. See [Cases](/docs/case-management) for more details. | | **Connection** | A `Connection` can be created with a vast number of cloud infrastructures and monitoring and security tools. A `Connection` enables actions to run on remote systems that require authorization. It is created using a token from the target system or via the personal account of the user on that system. See [Connections](/docs/workflows/building-workflows/connections) for more details. | | **Dashboards** | `Dashboards` enable visualization of data from tables across the Blink platform, including [Case Management Tables](/docs/case-management/manage-tables) and [Blink Tables](/docs/blink-platform/tables/tables). See [Dashboards](/docs/blink-platform/dashboards/dashboards) for more details. | | **Integrations** | An `Integration` is a connection to an external service provider that you wish to interact with and use as part of a workflow. | | **Runners** | A `Runner` executes the actions defined in the Workflow. By default, all actions are executed from the Blink cloud; however, the user can choose to deploy a runner that will execute all of the actions from your on-premises cloud infrastructure. See [Runners](/docs/blink-platform/runners) for more details. | | **Steps** | `Steps` are the building blocks of Blink's Workflows. Each Step has a single goal and Steps are arranged in a logical order to complete a workflow. The user assigns input parameters, and the Step executes an Action and displays its output. See [Steps](/docs/workflows/building-workflows/steps) for more details. | | **Tenant** | A `Tenant` in Blink is the top-level organizational unit that contains all workspaces, users, and resources for your account. Tenants have their own data quotas, user roles, and can be managed by service providers. | | **Trigger** | Steps and workflows run when they are initiated by one of the following `triggers`: See [Triggers](/docs/workflows/building-workflows/triggers) for more details. | | **Variables** | `Variables` are persistent values you can define and use throughout your entire platform. In the Platform you can use dynamic variables or global variables. | | **Web Forms** | `Web Forms` enable the creation and sharing of secure, interactive web pages designed to gather data, collect responses, share information, and trigger workflows based on user input. This feature combines dynamic, step-by-step functionality with robust support for static and interactive flows, empowering teams to implement versatile, user-friendly workflows efficiently. See [Web Forms](/docs/blink-platform/web-form/web-form) for more details. | | **Workflow Editor** | The `Workflow Editor` allows you to create and edit automated workflows, where you can view the run log of the workflow. The workflows can be a draft or published version. | | **Workflows** | A `Workflow` constitutes a series of actions that solves a specific use case. It is created using Steps and Sections. See [Workflows](/docs/workflows) for more details. | | **Workspace** | A `workspace` enables you to create data-segregated and separate workspaces for different teams across your company, as well as for different use cases. Every team can have one or more workspaces. This enables team members to collaborate on projects and share automated workflows and resources efficiently. All the workflows of a Workspace appear on the Workflow Pack page. See [Workspaces](/docs/blink-platform/workspaces) for more details. |