Workspaces
The Tenant's Dashboard
Overview
The ‘Overview’ provides a centralized view of automation activity across your Blink workspace. It highlights key metrics such as workflow usage, actions automated, time saved, and estimated cost savings, helping teams monitor performance, track impact, and optimize automation at scale. Filters by tenant, workspace, and timeframe allow you to customize the data view to fit your operational needs.1
Navigate to Dashboards
Go to the ‘Dashboard’ page by navigating to ‘Tenant Settings’ in your Blink workspace. This page provides a high-level view of usage across all workspaces within the selected tenant.
2
In the Overview Tab
In the Overview tab, you can find the usage panel at the top of the page. This section highlights key metrics related to automated workflows across your selected tenants and workspaces, including:
| Usage | Description | |
|---|---|---|
| 1 | Unique Workflows | Total number of distinct workflows executed across the selected workspaces within the timeframe. |
| 2 | Actions Automated | Cumulative number of billable actions successfully executed by workflows in the selected tenant, workspaces and timeframe. |
| 3 | Time Saved | Estimated total time saved (in hours) by automating actions instead of performing them manually. |
| 4 | Money Saved | Estimated cost savings derived from time saved via automation, calculated in monetary value. |
| 5 | Timeframe | Allows you to define the reporting period for the metrics displayed (e.g., last 7 days, last 30 days). |
| 6 | Tenant | Dropdown to filter and view data specific to a selected tenant. |
| 7 | Workspace | Dropdown to refine the data shown to specific workspaces within the selected tenant. |
| 8 | Bar Chart | Visual graph showing the daily count of automated actions over the selected timeframe and filters. |
Note: Workspace usage data in Blink Ops provides essential insights into automation effectiveness. By tracking workflow execution, action volume, and estimated savings, teams can measure impact, identify optimization opportunities, and better allocate engineering and automation resources. contact Blink Ops support for limit adjustments.
Active Workflows
The Active Workflows section provides detailed visibility into which workflows are being executed, how frequently they run, and the total amount of actions executed in a workspace and tenant. This view helps teams identify high-usage workflows, track vendor utilization, and assess performance across tenants and workspaces, enabling better prioritization, optimization, and scaling of automation efforts.
| Usage | Description | |
|---|---|---|
| 1 | Vendor | The third-party vendor(e.g., Okta, CrowdStrike) that the workflow interacts with or automates. |
| 2 | Name | The specific name of the workflow, as defined by the builder or admin. |
| 3 | Workspace | The name of the workspace in which the workflow is created and executed. |
| 4 | Runs | The total number of times this workflow has been triggered or executed within the selected timeframe. |
| 5 | Workflow Actions | The number of actions defined within this specific workflow. |
| 6 | Total Actions | Refers to all actions executed throughout the entire workflow, including any subflows. If no subflows are exist in the workflow, then the total action refers to the total amount of actions used within the parent workflow. |
| 7 | Timeframe | Controls the date range for analyzing workflow runs and action usage metrics (e.g., last 7 days). |
| 8 | Tenant | Dropdown to filter and view data specific to a selected tenant. |
| 9 | Workspace | Used to narrow down workflows to specific workspaces within the selected tenant. |
| 10 | Condition Builder | Filters table data to display only the results that match the condition statements you define |
Error Logs
The Error Logs section provides a detailed, real-time view of all failed workflow executions across your selected tenant and workspaces. This table allows you to quickly identify which workflows encountered errors, when they occurred, and what caused them. With powerful filtering, search, and drill-down capabilities, the ‘Error Logs’ help teams troubleshoot failures efficiently and maintain the reliability of automated processes.
| Field | Description | |
|---|---|---|
| 1 | Workspace Name | The name of the workspace where the workflow execution occurred. |
| 2 | Workflow Name | The name of the workflow that encountered the error during execution. |
| 3 | Execution Number | A unique identifier for the specific execution attempt of the workflow. |
| 4 | Error | The error code or message returned from the failed workflow execution. Hover to view details, or click to open the full error log for that specific run. |
| 5 | Date and Time | The exact timestamp when the error occurred, shown in the user’s local time zone. |
| 6 | Tenant | Dropdown to filter error logs by a specific tenant. |
| 7 | Workspace | Dropdown to filter error logs by one or more workspaces within the selected tenant. |
| 8 | Search | Allows users to search logs by keyword, such as workflow name, workspace, or error message. |
| 9 | Condition Builder | Lets you apply conditional logic to filter the table data based on specific criteria. |