, ...}`, For example:
```json theme={"dark"}
{
"created_at": {
"$gt": "2018-01-01T16:00:00.000Z",
"$lt": "2018-06-01T16:00:00.000Z"
}
}
```
It means that the logical `AND` operator is used between the two predicates. Its type is an object of conditions.
### predicates
RQL supports various predicates for filtering:
* `$eq`: Equals (can be used on all types)
* `$neq`: Not equals (can be used on all types)
* `$gt`: Greater than (can be used on numbers, strings, and timestamp)
* `$lt`: Less than (can be used on numbers, strings, and timestamp)
* `$gte`: Greater than or equal to (can be used on numbers, strings, and timestamp)
* `$lte`: Less than or equal to (can be used on numbers, strings, and timestamp)
* `$like`: Like (can be used only on type string)
### More Examples:
#### Example One
A basic query to fetch records from a Case Table with a low status:
```json theme={"dark"}
{
"limit": 25,
"offset": 0,
"filter": {
"severity": "low"
}
}
```
#### Example Two
A more complex query that filters records from a Case Table based on creation date, severity status, and sorts the results according to the date the case was created in descending order:
```json theme={"dark"}
{
"limit": 25,
"filter": {
"case_type": {
"$eq": "cloud security"
},
"created_at": {
"$gt": "2018-01-01T16:00:00.000Z",
"$lt": "2018-04-01T16:00:00.000Z"
},
"$or": [{ "severity": "high" }, { "status": "open" }]
},
"sort": ["-created_at"]
}
```
A detailed explanation of the above RQL Query:
* `limit`: Limits the number of records returned
* `25`: Specifies that the query should return a maximum of 25 records.
* `filter`: The main object containing the filtering criteria.
* `case_type`:
* `$eq`: Filters records where the "case\_type" field is "Cloud Security".
* `created_at`
* `$gt`: Specifies that the created\_at field must be greater than "2018-01-01T16:00:00.000Z".
* `$lt`: Specifies that the created\_at field must be less than "2018-04-01T16:00:00.000Z".
* `$or`: Logical OR operator to combine multiple conditions.
* `severity`:
* `"high"` : Filters records where the severity field is "high".
* `status`:
* `"open"`: Filters records where the status field is "open".
* `sort`: Specifies the sorting order of the returned records.
* `["-created_at"]`: Sorts the records in descending order by the created\_at field (the - sign indicates descending order).
#### Example Three
This query filters the case management records to retrieve those that are open, have a severity status of critical, the case manager is either John Doe or Jane Doe, contain the word "urgent" in the case overview, and were created within the first 4 months of 2024.
```json theme={"dark"}
{
"filter": {
"status": {
"$eq": "open"
},
"severity": {
"$eq": "medium"
},
"case_manager": {
"$contains_any": ["johndoe@gmail.com", "janedoe@gmail.com"]
},
"overview": {
"$like": "%urgent%"
},
"created_at": {
"$gte": "2024-01-01T00:00:00Z",
"$lt": "2024-04-31T23:59:59Z"
}
}
}
```
Detailed Explanation of the above RQL Query:
* `filter`: The main object containing the filtering criteria
* `status`:
* `$eq`: Specifies that the status field must be equal to "open".
* `priority`:
* `$gt`: Specifies that the priority field must be greater than 2.
* `case_manager`:
* `$contains_any`: Specifies that the "case\_manager" field must contain at least one of the specified values ("[johndoe@gmail.com](mailto:johndoe@gmail.com)" or "[janedoe@gmail.com](mailto:janedoe@gmail.com)").
* `overview`:
* `$like`: Specifies that the overview field must match the pattern "%urgent%", meaning it should contain the word "urgent" anywhere within the overview text field.
* `created_at`:
* `$gte`: Specifies that the "created\_at" field must be greater than or equal to "2024-01-01T00:00:00Z".
* `$lt`: Specifies that the created\_at field must be less than "2024-04-31T23:59:59Z".
# List Records from Table
Source: https://docs.blinkops.com/docs/api/tables/list-records-from-table
get /workspace/{ws_id}/table/{table}
API endpoint to list records from a Blink table with optional filtering.
# Updates Field for Table
Source: https://docs.blinkops.com/docs/api/tables/updates-field-for-table
put /workspace/{ws_id}/table/{table}/fields/{field}
API endpoint to update a field value in a Blink table record.
# Get tenant entities (users or groups)
Source: https://docs.blinkops.com/docs/api/tenant/get-tenant-entities-users-or-groups
get /tenant/entities
Returns a paginated list of users and groups in the authenticated user's Blink tenant.
# Get groups of user
Source: https://docs.blinkops.com/docs/api/users/get-groups-of-user
get /user/{id}/groups
API endpoint to retrieve all groups that a specific user belongs to in Blink.
# Remove a user from groups
Source: https://docs.blinkops.com/docs/api/users/remove-a-user-from-groups
delete /user/{id}/groups
Removes a user from one or more groups. The user cannot be removed from the tenant-wide "All Users" group.
# Batch copy of playbooks to target workspace and pack
Source: https://docs.blinkops.com/docs/api/workflows/batch-copy-of-playbooks-to-target-workspace-and-pack
post /workspace/{ws_id}/batch_copy
Batch copy of playbooks to target workspace and pack
# Batch move of playbooks to target workspace and pack
Source: https://docs.blinkops.com/docs/api/workflows/batch-move-of-playbooks-to-target-workspace-and-pack
post /workspace/{ws_id}/batch_move
Batch move of playbooks to target workspace and pack, the order of the
# Create a new playbook
Source: https://docs.blinkops.com/docs/api/workflows/create-a-new-playbook
post /workspace/{ws_id}/playbooks
Creates a new playbook in the specified workspace and immediately publishes it.
# Delete a playbook by its ID
Source: https://docs.blinkops.com/docs/api/workflows/delete-a-playbook-by-its-id
delete /workspace/{ws_id}/playbooks/{id}
API endpoint to delete a playbook by its unique identifier in Blink.
# Edit playbook metadata
Source: https://docs.blinkops.com/docs/api/workflows/edit-playbook-metadata
put /workspace/{ws_id}/playbooks/{id}/edit
Updates the name, description, tags, and runner of the playbook with the given ID. Updating the runner requires the ViewAction permission on RunnerObject.
# Execute a playbook
Source: https://docs.blinkops.com/docs/api/workflows/execute-a-playbook
post /workspace/{ws_id}/playbooks/{id}/execute
API endpoint to trigger the execution of a playbook in Blink.
# Get a playbook by its ID
Source: https://docs.blinkops.com/docs/api/workflows/get-a-playbook-by-its-id
get /workspace/{ws_id}/playbooks/{id}
API endpoint to retrieve a playbook's details by its unique identifier.
# Get a playbook version by branch and version number
Source: https://docs.blinkops.com/docs/api/workflows/get-a-playbook-version-by-branch-and-version-number
get /workspace/{ws_id}/playbooks/{id}/version/{branch}/{version}
API endpoint to retrieve a specific playbook version by branch and version number.
# Get connections used by a list of playbooks
Source: https://docs.blinkops.com/docs/api/workflows/get-connections-used-by-a-list-of-playbooks
post /workspace/{ws_id}/playbooks/get-playbooks-used-connections
Returns the list of connections (with vendor info) that are referenced by the given playbook IDs.
# Get the latest draft playbook version for a playbook
Source: https://docs.blinkops.com/docs/api/workflows/get-the-latest-draft-playbook-version-for-a-playbook
get /workspace/{ws_id}/playbooks/{id}/draft
API endpoint to retrieve the latest draft version of a playbook in Blink.
# Get the latest public playbook version for a playbook
Source: https://docs.blinkops.com/docs/api/workflows/get-the-latest-public-playbook-version-for-a-playbook
get /workspace/{ws_id}/playbooks/{id}/public
API endpoint to retrieve the latest published version of a playbook in Blink.
# List all versions metadata of a playbook
Source: https://docs.blinkops.com/docs/api/workflows/list-all-versions-metadata-of-a-playbook
get /workspace/{ws_id}/playbooks/{id}/versions
API endpoint to list metadata for all versions of a specific playbook.
# List playbooks with optional filtering
Source: https://docs.blinkops.com/docs/api/workflows/list-playbooks-with-optional-filtering
get /workspace/{ws_id}/playbooks
API endpoint to list all playbooks in your workspace with optional filtering.
# Share portal app
Source: https://docs.blinkops.com/docs/api/workflows/share-portal-app
post /playbooks/{id}/portal_share
Share portal app with other users or groups
# Un-share portal app
Source: https://docs.blinkops.com/docs/api/workflows/un-share-portal-app
post /playbooks/{id}/portal_unshare
Un-share portal app with other users or groups
# Add entities to workspace
Source: https://docs.blinkops.com/docs/api/workspaces/add-entities-to-workspace
post /workspaces/{ws_id}/entities
API endpoint to add entities such as users or groups to a Blink workspace.
# Assign a role to a user or group in a workspace
Source: https://docs.blinkops.com/docs/api/workspaces/assign-a-role-to-a-user-or-group-in-a-workspace
post /workspaces/{ws_id}/{entity_type}/{entity_id}/role/{role}
API endpoint to assign a role to a user or group within a Blink workspace.
# Get workspace details
Source: https://docs.blinkops.com/docs/api/workspaces/get-workspace-details
get /workspaces/{ws_id}
API endpoint to retrieve details about a specific Blink workspace.
# Update the Workspace Settings
Source: https://docs.blinkops.com/docs/api/workspaces/update-the-workspace-settings
put /workspaces/{ws_id}/settings
Update the workspace settings by provided values
# Account Management
Source: https://docs.blinkops.com/docs/blink-platform/account-management/account-management
This page provides an overview of the features and functionality available in your Blink Ops account settings, as well as Blink's security and legal policies.
## Profile Details
Access and manage your **Username**, **Email Address**, change your **Password**, and enable **Two-Factor Authentication** here.
![]()
**Note:** If you log in using Google, GitHub, Microsoft, or SSO, the options to change your password or enable two-factor authentication will not be available.
***
## API Keys
In the API Keys settings page you can manage your personal API keys of the Blink platform. You can create, delete and edit your API keys.
![]()
***
## Accounts - Users and Service Accounts
A Tenant-Admin can create a service account or invite a user to an account and then immediately add the user to groups and workspaces, and define a user role. See [Blink Users](/docs/blink-platform/account-management/accounts) for more details.
![]()
***
## Groups
**Groups** allow you to manage users by teams or departments. You can assign specific roles to groups within workspaces, granting all members access. See [Blink Groups](/docs/blink-platform/account-management/groups) for more information.
![]()
***
## Roles
Each Blink Ops user can be assigned one of three roles: **Admin**, **Builder**, or **Consumer**. Learn more in [Blink User Roles](/docs/blink-platform/account-management/roles).
![]()
***
## Workspace Management
The **Workspace Management** section allows you to view and manage all your workspaces. See [Workspace Management](/docs/blink-platform/account-management/workspace-management) for more details.
![]()
***
## General
In the **General** tab of account settings, you can apply various configurations to your Blink Ops account. See [General Settings](/docs/blink-platform/account-management/general) for details.
![]()
***
## AI Settings
See [AI Settings](/docs/blink-platform/account-management/ai-settings) for details.
1. **Enable Builder Copilot test data access** – When enabled, the [Builder Copilot](/docs/builder-copilot/builder-copilot) can access workflow testing execution data from the current session to generate more context-aware and precise configuration suggestions. If a step produces an error in its output, you can ask Builder Copilot to fix it, with the error message included in its context for more accurate and effective resolutions. When disabled, suggestions are based only on the workflow definition and user input.
![]()
2. AI Models- Enable Blink to use AI models from your own AWS account (via Amazon Bedrock) instead of Blink's shared AI infrastructure. When active, all AI calls are routed through your account.
![]()
***
## Audit Logs
**Audit Logs** track and monitor activities across three main categories within your tenant. See [Audit Logs](/docs/blink-platform/account-management/audit-logs) for more information.
![]()
***
## Account Security Settings
Learn how to configure your account's security settings. For detailed instructions, visit [Account Security Settings](/docs/blink-platform/account-management/identity-providers/identity-providers).
![]()
## Resetting Your Password
Instructions about how to reset your password for your Blink Account. See [Resetting your Password](/docs/blink-platform/account-management/resetting-your-password) for more details.
![]()
## Security, Legal, and Privacy Policy
Access Blink Ops’ security statement and privacy policy here. See [Security and Legal](/docs/blink-platform/account-management/security-and-legal/security-statement) for further information.
# About Accounts
Source: https://docs.blinkops.com/docs/blink-platform/account-management/accounts
How to manage your Blink account settings, including profile, preferences, and organization details.
Each company using Blink has its own separate account, fully isolated from all other companies. Within an account, groups can be created to organize users, such as teams or departments.
The Blink platform supports two types of accounts: [user account](#users) and [service accounts](#service-account), each serving different purposes.
## User Account Vs Service Account
A [user account](#users) is an identity created for an individual to access and interact with systems, applications, and services, typically requiring authentication via a username and password, and often equipped with permissions aligned with the individual's role. On the other hand, a [service account](#service-account) is designed for use by applications, services, or automated processes rather than human users. Service accounts are authenticated using credentials such as keys or tokens and are granted specific permissions to perform predefined tasks, allowing for secure and automated access to resources without human intervention. While user accounts are managed based on the individual's lifecycle, service accounts are managed according to the application's needs.
## Users
Each company using Blink operates within its own separate account, fully isolated from all other accounts. Only Admin users have the authority to invite new users and manage user access, including adding or removing users from groups.
Before a user can access the Blink platform, they must be added to the account. Admins can invite a user, assign them to specific groups and workspaces, and define their role in advance. Once the invited user accepts the invitation, all their workspaces, group memberships, and roles are already configured, allowing them to start using the platform immediately without additional setup.
**Please note**: Deleting a user does not remove any associated resources, such as workspaces, workflows, or connections.
![]()
### Inviting a New User
Click on "Account" option. You will be navigated to the Accounts Page in your **Account Settings**.
![]()
In the **Users** tab of the 'Accounts' page, click the "Invite User" button in the top-right corner. Provide the email address of the new user you would like to invite
The user will receive an email invite and once accepted, appear in the member list of the account.
There are three types of built-in [Tenant Roles](/docs/blink-platform/account-management/roles#tenant-role-scope) to assign the invited user:
* [Admin](/docs/blink-platform/account-management/roles#admin): As an Admin, you have full access to all workspaces as well as control over all settings across the Blink Platform.
* [Consumer](/docs/blink-platform/account-management/roles#consumer): As a Consumer, you have full access to the self-service portal as well as read and write permissions in the user's Workspaces.
* [Builder](/docs/blink-platform/account-management/roles#builder): As a Builder, you have complete access to read, write, and execute permissions within the user's Workspaces.
* [Tenant Guest](/docs/blink-platform/account-management/roles#4-tenant-guest) As a Tenant Guest, you only have access to view a workspace.
You can also assign a user a custom role within the tenant scope.
### Checking the Status of a Member of your Account
A member can have one of the following statuses:
| User status | Description | Admin actions available |
| ----------- | -------------------------------- | ----------------------------------------------------------------------- |
| Active | The user has signed up to Blink. | Deactivate user, remove user or check which groups the user belongs to. |
| Inactive | The user is blocked from Blink. | Re-activate. |
| Invited | The user is invited to Blink. | Re-send or cancel the invite. |
The following images shows Admin actions for an inactive user.
![]()
The following screenshot shows Admin actions for an invited user.
![]()
The following screenshot shows Admin actions for an active user.
![]()
## Service Account
A service account is a specialized, non-human account used by locations, services, or automated processes to access resources and perform tasks. It is authenticated through credentials such as API keys or tokens and is granted specific permissions tailored to its intended functions, enabling secure and automated operations without human intervention.
**Note**: Only [Tenant Admin](/docs/blink-platform/account-management/roles#admin) users can create a service account and designate roles.
### How to create a New Service Account
Click on "Account" option. You will be navigated to the Accounts Page in your **Account Settings**.
![]()
Navigate to the "Service Account" Tab. In the "Service Account" tab of the Accounts page, click the "Create new account" button in the top-right corner.
Provide a Name for your Service Account, optionally add a description and choose a role:
* [Admin](/docs/blink-platform/account-management/roles#admin): As an Admin, the account has full access to all workspaces as well as control over all settings across the Blink Platform.
* [Builder](/docs/blink-platform/account-management/roles#builder): As a Builder, the account has complete access to read, write, and execute permissions within the user's Workspaces.
If the service account is assigned [Tenant- Builder Role](/docs/blink-platform/account-management/roles#builder), the [Tenant- Admin](/docs/blink-platform/account-management/roles#admin) will have to invite the Service Account to each Workspace they want it to operate in.
* [Consumer](/docs/blink-platform/account-management/roles#consumer): As a Consumer, the account has full access to the self-service portal as well as read and write permissions in the user's Workspaces.
![]()
### Editing a Service Account
Click on the Service Account's table field you would like to make changes to. The changes will be applied automatically.
![]()
### Deleting a Service Account
Click on the icon in the last column and click on the delete option and confirm you want to delete the selected service account by clicking the "Delete" button.
![]()
### Service Account Information
Each service account is created with one API Key. Access the Service Account's API Key by
1. Clicking on the icon in the last column and click on the "Account info" option and to view your service account's information and API key.
![]()
OR
2. Clicking the icon to copy your API Key.
![]()
# AI Settings
Source: https://docs.blinkops.com/docs/blink-platform/account-management/ai-settings
## AI Features
**Enable Builder Copilot test data access**- When enabled, the Builder Copilot can access workflow testing execution data from the current session to generate more context-aware and precise configuration suggestions. When disabled, suggestions are based only on the workflow definition and user input.
![]()
***
## AI Models
Blink supports three options for AI infrastructure:
* **Blink** *(recommended)* – Uses Blink-managed AI infrastructure through Blink's Amazon Bedrock account. This is the default option and provides a fully managed experience, with all AI requests routed through Blink.
* **[Amazon Bedrock](/docs/blink-platform/account-management/ai-settings#amazon-bedrock-prerequisites)** – Uses your own Amazon Bedrock account. When selected, all AI-related requests are executed through your AWS infrastructure, giving you full control over your AI resources and billing.
* **[Azure AI Foundry](/docs/blink-platform/account-management/ai-settings#microsoft-azure-foundry-prerequisites)**- Enables Blink to use AI models from your own Azure subscription (via Azure AI Foundry) instead of Blink's shared AI infrastructure. When active, all AI calls are routed through your account.
***
## How to Configure the Chosen AI Model
### Amazon Bedrock Prerequisites
* An AWS account with permission to deploy CloudFormation stacks and create IAM roles.
When you select Amazon Bedrock as your AI Model, all platform-wide AI operations are routed directly through your organization’s Microsoft Foundry account. This includes [Agents](/docs/agent-builder/agent-builder), [Agent Blink](/docs/case-management/agent-blink), [Builder Copilot](/docs/builder-copilot/builder-copilot), and other AI-powered capabilities across the Blink platform.
### Limitations
**Important to Note**: [Knowledge sources](/docs/agent-builder/building-the-agent), in the Agent Builder, are not currently supported when using [Amazon Bedrock as the AI provider](/docs/blink-platform/account-management/ai-settings#configuration-amazon-bedrock-as-the-ai-provider). Knowledge functionality is available only when using [Blink as the AI provider](/docs/blink-platform/account-management/ai-settings#ai-models)
![]()
***
### Setup Steps
Navigate to **Account Settings → AI Settings → AI Models**.
In the **AI Provider** dropdown, select **Amazon Bedrock**.
Blink automatically generates a unique **External ID** for your account and displays it on screen.
**What is the External ID?**
It is a secret token that Blink embeds in every `AssumeRole` request. Your IAM trust policy must require it, which prevents any other AWS account from assuming your role even if they know your Role ARN. Do not share it.
Fill in:
* **AWS Account ID** — the 12-digit numeric ID of the AWS account where Blink should operate (e.g. `123456789012`).
* **IAM Role Name** — the name you want to give the IAM role that Blink will assume. The default suggestion is `BlinkBedrockExecutionRole`; you can use any name that fits your naming conventions.
Click **Open in AWS Console**. This opens the AWS CloudFormation quick-create page with all parameters pre-filled:
| Parameter | Value |
| ----------- | ------------------------------ |
| Stack name | `blink-bedrock-access` |
| External ID | your External ID from step 3 |
| Role Name | the name you entered in step 4 |
In the AWS Console, scroll to the bottom, acknowledge the IAM capability checkbox, and click **Create stack**. Wait for the stack status to reach `CREATE_COMPLETE` (usually under 2 minutes).
**What does the stack create?**
A single IAM role in your account. The role's trust policy allows Blink's AWS account to assume it — but only when the correct External ID is presented.
The role's permission policy grants the following actions, scoped to Anthropic foundation models and cross-region inference profiles only:
* `bedrock:InvokeModel`
* `bedrock:InvokeModelWithResponseStream`
* `bedrock:Converse`
* `bedrock:ConverseStream`
* `bedrock:CountTokens`
Return to the Blink AI Settings page and click **Test connection**. Blink will attempt to assume the role and invoke a lightweight Bedrock call using the values currently in the form - **no need to save first**.
A success confirmation means the role and permissions are correctly configured.
Click **Save changes** to activate the integration.
**Reverting to Blink's Default Provider**:
Switch the **AI Provider** dropdown back to **Blink** and save. The IAM role in your AWS account is not deleted automatically — you can clean it up by deleting the `blink-bedrock-access` CloudFormation stack.
**Reverting to Blink's Default Provider**
Switch the **AI Provider** dropdown back to **Blink** and save. The app registration and federated credential in your Azure tenant are not removed automatically — you can delete them via the Azure Portal if no longer needed.
***
### Required Bedrock Model Access
The customer must enable access to the following cross-region inference profiles in their AWS account before the integration will work. All are from the **Anthropic** provider in Bedrock.
**How to enable:** AWS Console → Amazon Bedrock → Model access → Manage model access → select each model below → Request model access.
**Note**: All models in the table must be enabled
| Model | Bedrock Model ID |
| ----------------- | ------------------------------------------------- |
| Claude Sonnet 4.6 | `global.anthropic.claude-sonnet-4-6` |
| Claude Haiku 4.5 | `global.anthropic.claude-haiku-4-5-20251001-v1:0` |
**How to Confirm a Model is Ready**:
Go to **AWS Console → Amazon Bedrock → Playgrounds → Chat**, select the model, and send a test message. A successful response confirms the model is accessible.
### Microsoft Foundry Prerequisites
* An Azure account with an Azure AI Foundry resource created.
* The following Claude models deployed in your Foundry resource, using these **exact deployment names**:
* `claude-sonnet-4-6`
* `claude-haiku-4-5`
* Permission to create app registrations and run scripts in your Azure subscription (Owner or Contributor + Application Administrator).
* Access to Blink's **AI Settings** page (Account Settings → AI Models).
When you select Azure AI Foundry as your AI Model, all platform-wide AI operations are routed directly through your organization’s Microsoft Foundry account. This includes [Agents](/docs/agent-builder/agent-builder), [Agent Blink](/docs/case-management/agent-blink), [Builder Copilot](/docs/builder-copilot/builder-copilot), and other AI-powered capabilities across the Blink platform.
### Limitations
**Important to Note**: [Knowledge sources](/docs/agent-builder/building-the-agent), in the Agent Builder, are not currently supported when using [Microsoft Foundry as the AI provider](/docs/blink-platform/account-management/ai-settings#microsoft-azure-foundry-prerequisites). Knowledge functionality is available only when using [Blink as the AI provider](/docs/blink-platform/account-management/ai-settings#ai-models)
![]()
***
### Setup Steps
Navigate to **Account Settings → AI Models**.
In the **AI Provider** dropdown, select **Azure AI Foundry**.
Fill in:
* **Subscription ID** — the ID of the Azure subscription that contains your Foundry resource. Find it in Azure Portal → *Subscriptions*.
* **Resource Group** — the resource group that contains your Azure AI Foundry resource.
* **Resource Name** — the name of your Azure AI Foundry resource (e.g. `my-foundry`).
Click **Generate Setup Script**. Blink generates a Bash script pre-filled with the values you entered. Open Azure Cloud Shell (Bash), paste the script, and run it.
The script uses the following parameters:
| **Parameter** | **Value** |
| --------------------- | -------------------------------------- |
| Subscription ID | your Subscription ID from step 3 |
| Resource Group | your Resource Group from step 3 |
| Resource Name | your Foundry Resource Name from step 3 |
| OIDC Issuer / Subject | provided by Blink automatically |
**What does the script do?**
It creates an Azure AD app registration and service principal in your tenant, then configures a federated identity credential that authorises Blink's cluster identity to obtain access tokens — no client secrets or API keys are stored anywhere. It also assigns the *Cognitive Services User* role on your Foundry resource to that app registration.
The script is safe to re-run. If the app registration already exists it updates the federated credential in place.
When the script completes, it outputs two values you will need in the next step:
* **Entra Tenant ID**
* **Application (Client) ID**
Paste both values from the script output into the corresponding fields in Blink.
Click **Test connection**. Blink will authenticate with your Azure tenant and invoke each required Claude model deployment — **no need to save first**.
A success confirmation means the federated credential and model deployments are correctly configured.
Click **Save changes** to activate the integration.
**Reverting to Blink's Default Provider**
Switch the **AI Provider** dropdown back to **Blink** and save. The app registration and federated credential in your Azure tenant are not removed automatically — you can delete them via the Azure Portal if no longer needed.
***
### Required Microsoft Foundry Model Access
You must deploy the following Claude models in your Azure AI Foundry resource before the integration will work. The deployment names must match exactly — Blink uses these names when invoking the models.
* **How to deploy**: Azure Portal → Azure AI Foundry → your resource → models + endpoints → Deploy model → select the model → set the deployment name exactly as shown above.
* **How to confirm a model is ready:** Go to Azure AI Foundry → Playgrounds → Chat, select the deployment, and send a test message. A successful response confirms the model is accessible.
Both models must be deployed before testing the connection. The connection test will fail if either deployment is missing or named differently.
| **Model** | **Required Deployment Name** |
| ----------------- | ---------------------------- |
| Claude Sonnet 4.6 | `claude-sonnet-4-6` |
| Claude Haiku 4.5 | `claude-haiku-4-5` |
***
# API Keys
Source: https://docs.blinkops.com/docs/blink-platform/account-management/api-keys
Create and manage API keys for programmatic access to the Blink platform.
In the API Keys settings page you can manage your personal API keys of the Blink platform. You can create, delete and edit your API keys.
![]()
**NOTE**: There always has to be one API key available. The maximum number of API keys at any given time is `5`.
## Create API Key
Select the **New API Key** button in the top-right corner
Give your API key a name, description (optional) and choose when the API Key expires (after 30 days, 90 days or never ). Then click the create button in the bottom-right corner.
![]()
It will be added to the table.
| Parameter | Description |
| ----------- | -------------------------------------------------------------------------------------------------------- |
| Name | Name given to the API Key |
| Description | Description given to the API Key |
| Key | The API key itself |
| Created At | The time you created the API key |
| Expires | It will display: the day of expiration, never- if no expiry is set or expired- if expiration date passed |
| Last used | The last time you used the API key |
## Generate a New API Key
**Note**: This setting can only be used with the default API key which is now a legacy feature so will only appear in certain Tenants
To generate a new API key, click the icon on the right-hand side of the default API key row, then select **Rotate**.
A popup will appear asking you to confirm if you are sure you would like to rotate the API key. Select the confirm button
![]()
***
## Edit API Key
If you want to make any changes to the API information, double click on the cell and make the desired changes. You can change the API key name or description.
![]()
***
## Delete API Key
If you want to delete an API Key, click on the icon on the right-hand side of the row and select the **delete** option.
![]()
***
## Using your Personal API Key in Workflows
Click anywhere on the workflow within the Workflow pack.
You will be redirected to the Workflow Editor.
Click the icon in the top right-hand side corner.
Choose the Settings option to access the Workflow settings.
Go to the **Run Methods** section and select the **REST API** or **CLI** method.
Under the command text field, select which **personal API key** from the dynamic dropdown menu.
Upon selection, your **personal API key** will be added to the command, allowing you to proceed using the chosen run method for your chosen Workflow.
![]()
# Audit Logs
Source: https://docs.blinkops.com/docs/blink-platform/account-management/audit-logs
The Audit Log monitors user activity in the tenant
The **Audit Log** provides a comprehensive, timestamped record of all key activities occurring within the tenant. It is a critical tool for monitoring changes, troubleshooting issues, and ensuring compliance by giving administrators visibility into who did what and when.
**Note**: Audit logs are retained for a duration of 30 days.
Audit log events are categorized into the following areas:
* Approval management
* Cases
* Case related tables
* Connections
* Dashboards
* Global variables
* Runners
* Self-service apps
* Tables
* Tenant admin settings
* Tenant user management
* Users
* Workflows
* Workspace management
For a complete list of Audit Log events, see this [section](#categories-and-events).
The audit logs do not track changes to data or content, such as workflow action updates, workflow executions, modifications to table records, or changes to cases.
***
## Audit Log Table Content
Each log entry includes the following information:
* **Category** – The general type of activity: Setting updates, System configuration, or User actions.
* **Action** – The specific action that occurred.
* **Parameters** – Key data relevant to the action, such as the affected username, Workflow name, or API endpoint.
* **Details** – Additional context or information about the action.
* **Workspace** – The name of the workspace where the action took place.
* **Done by** – The email address of the user who initiated the action.
* **Date and Time** – When the action was performed.
![]()
***
## Categories and Events
In the following section, you can find a complete overview of Blink’s audit log categories and the types of events captured within each. Audit logs in Blink are designed to give you full visibility into user activity, system changes, and workflow executions across the platform.
### Approval Management
| **Event** | **Description** |
| ----------------- | ------------------------------------------------------- |
| Request approved | A submitted request was approved by an authorized user. |
| Request denied | A submitted request was denied by an authorized user. |
| Request submitted | A request was submitted for approval. |
***
### Cases
| **Event** | **Description** |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Case exported | A case was exported to a downloadable format. |
| Case shared | A case was shared with external parties or users. |
| Case viewed | Logged when a user opens and views the details of a case. |
| Case closed | Logged when a case has been closed |
| Case response action triggered | Logged when a predefined response action (e.g., notification, remediation step, or ability workflow) is executed for a case. |
| Case escalated | Logged when a the [escalated action](/docs/case-management/cases/case-overview/case-overview#escalate-case) in the Case Overview is used. |
| Table exported to CSV | A case table was exported in CSV format. |
***
### Case Related Tables
Case related tables refer to **all** tables in [Case Management](/docs/case-management/case-management) including: the [Cases Table](/docs/case-management/cases/cases), [Alerts Table](/docs/case-management/alerts/alerts), [Observable Table](/docs/case-management/observables/observables), [Attachments Table](/docs/case-management/attachments/attachments),[Tasks Table](/docs/case-management/tasks/tasks) or your own [Custom Table](/docs/case-management/case-management-settings#create-a-custom-table) created in [Case Management](/docs/case-management/case-management)
| **Event** | **Description** | |
| --------------------------- | ------------------------------------------------------------ | - |
| Custom cases table created | A case management tables was created. | |
| Custom cases table edited | An existing case management table was edited. | |
| Case related tables read | Logged when a case management tables was accessed or viewed. | |
| Case related tables deleted | A case management tables was deleted. | |
| Exported to CSV | Data from a custom cases table was exported as a CSV file. | |
| Field created | A new field was added to a case management table. | |
| Field edited | A field in a case management tables was updated. | |
| Field deleted | A field was removed from a case management tables | |
***
### Connections
| **Event** | **Description** |
| ------------------ | -------------------------------------------------- |
| Connection created | A new integration connection was created. |
| Connection deleted | An existing integration connection was removed. |
| Connection edited | An integration connection was modified or updated. |
***
### Dashboards
| **Event** | **Description** |
| ------------------------- | --------------------------------------------------------------- |
| Dashboard activated | A dashboard was activated and made live. |
| Dashboard created | A new dashboard was created. |
| Dashboard deactivated | A dashboard was deactivated. |
| Dashboard deleted | A dashboard was deleted. |
| Dashboard edited | Changes were made to a dashboard’s configuration or layout. |
| Dashboard metadata edited | Metadata for the dashboard (e.g., tags, ownership) was updated. |
***
### Global Variables
| **Event** | **Description** |
| ----------------------- | --------------------------------------------------- |
| Global variable created | A new global variable was created. |
| Global variable deleted | A global variable was removed from the system. |
| Global variable edited | An existing global variable was updated or changed. |
***
### Runners
| **Event** | **Description** |
| --------------------------- | -------------------------------------------------------------------- |
| Runner group created | A new group for managing runners was created. |
| Runner group deleted | A runner group was deleted. |
| Runner group edited | A runner group’s settings or members were updated. |
| Runner group set as default | A runner group was marked as the default for new workflows or tasks. |
***
### Self-Service Apps
| **Event** | **Description** |
| ------------- | ---------------------------------------------------- |
| App created | A new self-service app was created. |
| App deleted | A self-service app was removed. |
| App published | A self-service app was published and made available. |
***
### Tables
| **Event** | **Description** |
| --------------------- | ----------------------------------------------- |
| Field created | A new field was added to a data table. |
| Field deleted | A field was removed from a data table. |
| Field edited | A field in a table was modified. |
| Table created | A new data table was created. |
| Table read | A new data table was accessed or viewed |
| Table deleted | A data table was deleted. |
| Table edited | A data table was updated or modified. |
| Table exported to CSV | A table’s contents were exported to a CSV file. |
***
### Tenant Admin Settings
| **Event** | **Description** | |
| ---------------------------------- | ------------------------------------------------------------------- | - |
| Audit logs exported | Audit logs were exported for review or archiving. | |
| Blink-cloud runner updated | Settings for the Blink cloud runner were updated. | |
| Default tenant runner updated | The default runner for the tenant was changed. | |
| Runner auto upgrade updated | Auto-upgrade settings for runners were modified. | |
| SAML role mapping updated | Role mapping configuration for SAML was updated. | |
| SAML settings updated | SAML authentication settings were changed. | |
| Two-factor authentication disabled | Two-factor authentication was disabled for the tenant. | |
| Two-factor authentication enabled | Two-factor authentication was enabled for the tenant. | |
| Time format updated | The time display format used across the Blink platform was changed. | |
| Date format updated | The date display format used across the Blink platform was changed. | |
***
### Tenant User Management
| **Event** | **Description** |
| ---------------------------------------- | -------------------------------------- |
| Group created | A new group was created. |
| Group deleted | An existing group was deleted. |
| Group name updated | The name of a group was changed. |
| Role created | A new role was created. |
| Role deleted | An existing role was deleted. |
| Role updated | An existing role was updated. |
| Service account activated | A service account was activated. |
| Service account created | A new service account was created. |
| Service account deactivated | A service account was deactivated. |
| Service account deleted | A service account was deleted. |
| Service account group assignment updated | A service account's group was updated. |
| Service account role changed | A service account's role was changed. |
| User activated | A user was activated. |
| User deactivated | A user was deactivated. |
| User deleted | A user was deleted. |
| User group assignment updated | A user's group assignment was updated. |
| User invited | A user was invited. |
| User role changed | A user's role was changed. |
***
### Users
| **Event** | **Description** |
| --------------- | ----------------------- |
| User logged in | A user logged in. |
| User logged out | A user logged out. |
| API key created | An API key was created. |
| API key deleted | An API key was deleted. |
***
### Workflows
| **Event** | **Description** |
| ------------------------- | ------------------------------- |
| Pack created | A new pack was created. |
| Pack deleted | A pack was deleted. |
| Pack edited | A pack was edited. |
| Workflow activated | A workflow was activated. |
| Workflow created | A new workflow was created. |
| Workflow deactivated | A workflow was deactivated. |
| Workflow deleted | A workflow was deleted. |
| Workflow published | A workflow was published. |
| Workflow settings updated | Workflow settings were updated. |
***
### Workspace Management
| **Event** | **Description** |
| ---------------------- | ------------------------------------------- |
| Workspace created | A new workspace was created. |
| Workspace deleted | A workspace was deleted. |
| Workspace name updated | A workspace’s name was updated. |
| User invited/added | A user was invited or added. |
| User removed | A user was removed. |
| User role changed | A user’s role in the workspace was changed. |
***
## External Audit Log Integration
Blink supports native audit log streaming to external SIEM systems, allowing organizations to integrate Blink audit data into tools like Splunk or Elasticsearch. This feature gives security teams greater visibility and control by centralizing audit logs for compliance, monitoring, and incident response without the need for manual exports. [Tenant admins](/blink-platform/account-management/roles#1-admin) can configure their SIEM endpoint directly in Blink, test the connection, and begin streaming audit logs in real time.
![]()
***
In the top right-corner of the Audit Log page, select the icon
![]()
1. **Enable audit log streaming**:
* When enabled, audit logs will be delivered to your specified external destination in real time.
* Disabling this will stop all log delivery and deactivate the form below.
2. **URL**:
* The destination URL for your external logging service.
This must be a reachable HTTPS endpoint that supports log ingestion.
3. **Authentication Token**:
* A token or API Key used to authenticate requests to your external logging endpoint. This is required for secure delivery of audit logs.
4. **Destination Type**- Select the type of destination where logs will be sent:
* [Splunk HEC](#generating-a-splunk-http-event-collector-hec-token)
* HTTP (Bearer Auth)
* Elasticsearch
![]()
You can verify that Blink is successfully connected to your selected SIEM platform by clicking the 'Test Connection' button.
![]()
***
## Configuration Guide: Generating a Splunk HTTP Event Collector (HEC) Token
Follow this step-by-step guide, to learn how to generate Splunk HTTP Event Collector (HEC) token, which is required for integrating Splunk with the Blink platform. This token is required to integrate Splunk with the Blink platform in order to stream Blink's audit logs to a selected external destination.
**Note**: The images used in this guide are for illustration purposes only. Your Splunk configuration may differ based on your organization's environment, existing settings, and indexing policies. Use the images as a visual reference to help guide you through each step.
Log in to your [Splunk Enterprise account](https://login.splunk.com). In the top-right corner, click on **Settings**, then search for **HTTP Event Collector** and select it.
![]()
Fill in all required fields for the data source configuration.
![]()
Choose the appropriate indexes that the 'HTTP Event Collector' token will be allowed to access.
**Reminder**: The indexes displayed in the example image may differ from your organization’s configuration. Be sure to select the correct indexes based on your environment and data routing needs.
![]()
Review all the details you have entered to ensure everything is accurate before proceeding.
![]()
Once the token has been generated in Splunk, copy it and securely store it.
![]()
To complete the integration with Blink, go to the [Audit Settings](#external-audit-log-integration) section of the Blink platform and do the following:
* Paste the token into the **Authentication Token** field
* Enter the **URL**: If the HEC feature is enabled in the Splunk Enterprise platform you will see the port it uses (by default, it's `8088`). Your full url will look something like this `https://splunk.yourcompany.com:8088`
* Select **Splunk HEC** as the **Destination Type**
This ensures that Blink can successfully forward audit logs to your Splunk instance.
![]()
Click **Test Connection** to verify that the URL and token have been entered correctly and that Blink can successfully communicate with your Splunk instance. Once the connection is validated, click **Save Settings** to apply the configuration.
![]()
# Enabling Two Factor Authentication
Source: https://docs.blinkops.com/docs/blink-platform/account-management/authentication
Configure authentication methods for your Blink account, including SSO and multi-factor authentication.
When signing up for Blink, you have the option to enable two-factor authentication (2FA) for enhanced account security. Two-factor authentication adds an extra layer of protection by requiring users to verify their identity using two separate forms of identification before accessing their account.
**Note**: Two-Factor Authentication is only available for the **email login** option.
![]()
## Enabling Two-Factor Authentication (2FA) for Your Account
Two-Factor Authentication (2FA) is enabled at the tenant level and is automatically enforced for all users in the tenant upon login.
Navigate to the bottom-left corner of the Blink interface and click on the circle displaying your initials.
From the 'User Settings' menu, select 'General'.
![]()
On the 'General Settings' page, locate the 'Enable Two-Factor Authentication' option and toggle it on to activate the feature.
![]()
Click 'Save Settings' to confirm the activation of Two-Factor Authentication.
Using your preferred authenticator app, scan the barcode displayed on the screen.
In your authenticator app, retrieve the unique 6-digit code. Enter this code in the designated field, then click 'Continue'.
![]()
You will be redirected to the Sign-In page. Sign back into your Blink account.
Follow the prompt to enter a new authentication code from the same authenticator app to complete the verification.
![]()
After successfully logging in, Two-Factor Authentication will be fully activated for your Blink account.
At any time, you can choose to disable Two-Factor Authentication by toggling the 'Enable Two-Factor Authentication' switch off.
![]()
# General Settings
Source: https://docs.blinkops.com/docs/blink-platform/account-management/general
Configure general account settings including organization name, timezone, and preferences in Blink.
## General
In **General Settings** you can choose to:
* Customize your account by adding your own logo. Simply select the image box, and upload your preferred logo either from **uploading a file** or by entering the **image URL** in the **URL tab**. Your logo will be displayed in the bottom-left corner of your screen.
![]()
**Note**
The logo will be displayed in a squared ratio of 30px. We recommend uploading a picture with a size of at least 30x30 px.
The File format must be either a **JPG** or a **PNG**.
The File size can be up to **10 MB**.
***
## Main Settings
* Enable or Disable **runners to auto upgrade** by clicking the toggle button.
* Enable or Disable **Blink-Cloud runners** by clicking the toggle button.
* Enable or Disable [two factor authentication](/docs/blink-platform/account-management/authentication) by clicking the toggle button
Two-Factor Authentication (2FA) is enabled at the tenant level and is automatically enforced for all users in the tenant upon login.
* Select a **Default Tenant Runner** from the drop down menu.
* **Date Format** – Select the preferred date format to be applied across the entire Blink platform:
* **MM/DD/YYYY**
* **DD/MM/YYYY**
* **Time Format** – Select the preferred time display format for the Blink platform:
* **12-hour (AM/PM)**
* **24-hour**
* [Blink Portal Custom Header](/docs/blink-platform/blink-portal/blink-portal#customize-the-blink-portal-logo-and-header)- Set the header text that will be displayed in the [Blink Portal](/docs/blink-platform/blink-portal/blink-portal)
![]()
***
## Managed security service provider (MSSP)
* Appoint a provider to manage the account by entering the designated provider code. For more information visit the [Service Provider](/docs/blink-platform/service-providers/service-providers.mdx) section of our documentation.
![]()
***
## Approvals
The [publish approval process](/docs/workflows/managing-workflows/publish-approval/publish-approval) ensures that workflow changes are reviewed before being published, creating a streamlined approval process. These settings enable administrators to maintain stricter control over publishing permissions.
* **Restrict approvals to selected reviewers:** when this setting is enabled, only the selected reviewers will be able to review and approve the workflow changes.
* **Restrict reviewers to the same group:** when this setting is enabled, the builder who submitted the changes for approval can only choose reviewers who belong to the same group as the builder.
![]()
***
## Bots
* [Bot for Slack](/docs/blink-platform/blink-portal/blink-bot-for-slack): Create a Slack connection. See [creating a new connection](/docs/workflows/building-workflows/connections/creating-connection) for more details.
* [Bot For Zoom](/docs/blink-platform/blink-portal/zoom-slackbot): Create a Zoom connection. See [creating a new connection](/docs/workflows/building-workflows/connections/creating-connection) for more details.
![]()
# Blink Groups
Source: https://docs.blinkops.com/docs/blink-platform/account-management/groups
Groups are used to manage groups of users, for example work teams and departments
Groups are used to manage groups of users, for example work teams and departments. You can attach a specific role to a group inside a workspace, thus granting access to all group members.
## Creating a new group
1. Navigate to **Account Settings** and select the ![]()
icon.
2. Click **New Group**. In the dialog box, fill in the group name and description.
3. Then click **Save**.
![]()
## Adding a member to a group
### Adding a member from the Users tab
1. Navigate to **Account Settings** and select the ![]()
icon.
2. Select a user and double click on the **Groups** column.
3. From the dropdown menu, select a group you wish to add the user to.
4. Click **Add**.
### Adding a member from the Groups tab
1. Navigate to **Account Settings** and select the ![]()
icon.
2. Select a **Group** and double click on the **Users** column.
3. From the dropdown menu, select a user you wish to add to the group.
4. Click **Add**.
## Adding groups to a workspace
1. Click ![]()
to navigate to the **Workspaces Settings**.
2. In the empty text field invite a new member to your workspace by **User, Group or Email**
3. Click **Add**. The group is added to the workspace.
![]()
# Configuring a SAML application on Azure AD
Source: https://docs.blinkops.com/docs/blink-platform/account-management/identity-providers/azure
Instructions on how to configure a SAML SSO application with Azure.
Log in to Azure Active Directory Portal, and select "Enterprise applications" in the navigation panel.
![]()
Click on "New application"
![]()
Click on "Create your own application".
![]()
In the panel on the right, enter an app name and select the "Integrate any other application you don't find in the gallery (Non-gallery)" option, and click "Create" in the bottom-left corner.
![]()
Click on "Single sign-on" on the left pane, and select "SAML".
![]()
Click on "Edit".
![]()
**NOTE**
Please note that the Identifier (Entity ID) value, along with the Single Sign-On URL, can be located within the SAML tab under the Account Management Settings section within the Blink Platform. The **Reply URL (Assertion Consumer Service URL)** is not available under the SAML tab, therefore you can find it below:
**The Entity ID** : `urn:amazon:cognito:sp:eu-west-1_NEemCMO1L`
**The Reply URL (Assertion Consumer Service URL)** : `https://cognito.blinkops.com/saml2/idpresponse`
**Single Sign-On URL** : Please look in the Account Management Settings section within the Blink Platform to find your unique **Single Sign-On URL**.
![]()
Using the Reply URL **(Assertion Consumer Service URL)**, as well as the **Identifier (Entity ID)** value as well as the **Single Sign-On URL** value located within the SAML tab under the Account Management Settings section within the Blink Platform, copy and paste the values in the following text fields as demonstrated in the image below:
![]()
Next, scroll to the **Attributes & Claims** section and select the **add new claim** option in the top-left corner. Then under the **Additional Claims** section, ensure that the **claim names**, **type** and **value** correspond to the values as demonstrated in the image below:
![]()
Proceed by clicking on the **groups claim** option and provide all the required information on the sidebar to the right. Then, complete the process by clicking on the "Save" button.
![]()
# Configuring a SAML application on Cloudflare
Source: https://docs.blinkops.com/docs/blink-platform/account-management/identity-providers/cloudflare
Instructions on how to configure a SAML SSO application with Cloudflare.
## 1. Get SaaS Application URLs
* **Entity ID**: A unique URL issued for your SaaS application.
* **Assertion Consumer Service URL:** The service provider’s endpoint for receiving and parsing SAML assertions.
![]()
**NOTE**
Please note that the **Identifier (Entity ID)** value, along with the **Assertion Consumer Service URL**, can be located within the SAML tab under the Account Management Settings section within the Blink Platform. Please note the value of the **Assertion Consumer Service URL (ACS URL)** can be either the **Service Provider Login URL (SSO URL)** or **IdP-Initiated Login URL**.
**The Entity ID** : `urn:amazon:cognito:sp:eu-west-1_NEemCMO1L`
**Assertion Consumer Service URL:** [https://cognito.blinkops.com/saml2/idpresponse](https://cognito.blinkops.com/saml2/idpresponse).
![]()
***
## 2. Add your Application to Access
Navigate to the **Zero Trust** option in the sidebar.
![]()
Navigate to **application**.
![]()
Select **Add an application**.
![]()
Select SaaS.
![]()
Enter a unique name in the Application field, like `BlinkOps`, and hit **Enter** since the `BlinkOps` application might not be included.
![]()
Enter the **Entity ID** and **Assertion Consumer Service URL** obtained from your SaaS application account.
**INFO**
**The Entity ID** : `urn:amazon:cognito:sp:eu-west-1_NEemCMO1L`
**Assertion Consumer Service URL**: [https://cognito.blinkops.com/saml2/idpresponse](https://cognito.blinkops.com/saml2/idpresponse).
![]()
Select the **Name ID** Format expected by your SaaS application (usually Email).
![]()
Scroll down to the **SAML attribute statements** section and add the following **key-value pairs**, and then click Next.
![]()
**INFO**
**IdP groups**\
If you are using Okta, AzureAD, Google Workspace, or GitHub as your IdP, Access will automatically send a SAML attribute titled groups with all of the user’s associated groups as attribute values.
Configure **App Launcher settings** for the application — **this is an optional step.**
Under **Block pages**, choose what end users will see when they are denied access to the application:
* **Cloudflare default**: Reload the login page and display a block message below the Cloudflare Access logo. The default message is "That account does not have access", or you can enter a custom message.
* **Redirect URL**: Redirect to the specified website.
* **Custom page template**: Display a custom block page hosted in Zero Trust.
![]()
Next, configure how users will authenticate:
* Select the Identity providers you want to enable for your application.
* (Optional) Turn on Instant Auth if you selected only one IdP and want users to skip the identity provider selection step.
* (Optional) Under WARP authentication identity, allow users to authenticate to the application using their WARP session identity.
![]()
Select Next.
***
## Add an Access Policy
To control who can access your application, create an **Access policy**.
![]()
Then navigate to the **Assign a group** section and fill out the following fields.
![]()
Then head to the **SAML** tab under the **Account Management Settings** section within the Blink Platform and click the **Role Mapping** section and select the applicable values.
**Note:** Please note that within the **mapping** section, it's necessary to designate at least one **mapping role** as an **admin** with administrative privileges. Otherwise, you will not have the ability to operate within your account as an **administrator**.
![]()
***
## 4. Configure SSO in your SaaS application
Finally, you will need to configure your SaaS application to require users to log in through Cloudflare Access.
Configure the following fields with your SAML SSO-compliant application:
* SSO endpoint
* Access Entity ID or Issuer
* Public key
![]()
**NOTE**\
The metadata is available at the URL: `/saml-metadata`
Proceed by copying the contents of that file found at the URL: `/saml-metadata`. Then navigate to the **Metadata File section** found within the **SAML tab** in your **Account Management Settings**
Paste the **contents of that file** into the designated text field labeled Metadata File.
![]()
Then click **Save Settings** in the bottom-right corner. Your application will appear on the Applications page.
***
# Configuring a SAML application on Google Workspace
Source: https://docs.blinkops.com/docs/blink-platform/account-management/identity-providers/google
Instructions on how to configure a SAML SSO application with Google Workspace.
Log in to Google Admin account, press "Apps" on left sidebar, and under it "Web and mobile apps", then press in main window "Add app" and choose "Add custom SAML app":
![]()
In "Add custom SAML app", give App name, and press continue:
![]()
In the IdP page, click on the 'download metadata' button.
![]()
Once the file is downloaded, navigate to the Metadata File section found within the SAML tab in the Account Management Settings. Paste the **downloaded metadata** values into the designated text field labeled Metadata File.
![]()
**NOTE**
Please note that the Identifier (Entity ID) value, along with the Single Sign-On URL, can be located within the SAML tab under the Account Management Settings section within the Blink Platform. The **ACS URL** is not available under the SAML tab, therefore you can find it below:
**The Entity ID** : `urn:amazon:cognito:sp:eu-west-1_NEemCMO1L`\
**The ACS URL** : `https://cognito.blinkops.com/saml2/idpresponse`\
**Single Sign-On URL** : Please look in the Account Management Settings section within the Blink Platform to find your unique **Single Sign-On URL**.
![]()
Using the **ACS URL**, as well as the **Identifier (Entity ID)** value and the **Single Sign-On URL** available in the SAML tab under the Account Management Settings section within the Blink Platform, proceed to copy and insert these values into the designated text fields below.
**Note**: Paste the **Single Sign-On URL value** in the **START URL** text field.
![]()
Press continue
In the **Attribute mapping** page, map **"First name"** to **"given\_name"**, **Last name** to **family\_name**, and **"Primary email"** to **"email"**.
![]()
Next, scroll to the **Group Membership** section, select your **Google Groups**, and set the App attribute value as **group** and click 'FINISH'. Then head to the SAML tab under the Account Management Settings section within the Blink Platform and click the **Role Mapping** section and select the applicable values.
![]()
When a user belongs to multiple Google groups, Blink resolves role assignment in SAML SSO using a **top-down priority order** based on the `Group:Role` mapping table. The first matching group in the list determines the assigned role.
**IMPORTANT** Please note that in the **Mapping** section, at least one mapping role must be designated as an **admin** with administrative privileges. Additionally, the user configuring the group must be a part of the group mapped to the **Admin** role. Otherwise you won't be able to operate as an administrator in your account or access and edit the role mapping again.
![]()
After you finish SAML app creation, you can set up User access by changing the status to **ON** for all organizational units:
![]()
![]()
# Account Security Settings
Source: https://docs.blinkops.com/docs/blink-platform/account-management/identity-providers/identity-providers
Set up and manage identity providers for single sign-on (SSO) authentication in Blink.
This guide walks you through the key authentication and identity settings available in the Blink platform. From managing authorized domains and setting up external Identity Providers (IdPs), to configuring role mappings and enforcing SAML policies, each section helps you securely control user access and authentication behavior across your Blink environment. Start by accessing your account's security settings using the steps below.
***
## Access Account Settings
Navigate to the security settings on the Blink platform. In the bottom-left corner click on the rounded icon with your initials on it.
A dialogue box will appear, with your Blink Ops account settings:
![]()
If you are part of more than one tenant, you have the option to switch between the tenants by selecting the tenant from the dynamic dropdown menu.
![]()
***
## Login & Authentication
### Authorized Domains
A comma-separated list of domains allowed for IDP or username/password login. If not populated, any domain will be valid.
**Note**: SAML authorized domains are configured in a separate section. Navigate [here](#saml-authorized-domains).
![]()
***
### Identity Provider
Blink provides the option to configure an external Identity Provider to use within the Blink platform. Any SAML app can be connected to Blink.
Blink provides templates for:
* [Okta](/docs/blink-platform/account-management/identity-providers/okta)
* [Google Workspace](/docs/blink-platform/account-management/identity-providers/google)
* [Azure AD](/docs/blink-platform/account-management/identity-providers/azure)
* [Cloudflare](/docs/blink-platform/account-management/identity-providers/cloudflare)
***
### Role Mapping
Role Mapping is the method by which Blink synchronizes **Identity Providers** to the Blink platform.
Please be aware that configuring **Role Mapping** varies depending on the **Identity Provider** you are using. Therefore, it's crucial to carefully follow the instructions tailored to your chosen **Identity Provider** when setting up **Role Mapping**
**Note**: When mapping a Blink group to an Identity Provider (IdP), make sure the group is created in Blink before you configure the role mapping in the selected Identity Provider (IdP). Also, the name of the group in Blink must **match exactly** with the name of the group in the Identity Provider.
**IMPORTANT**: Please note that in the **Mapping** section, at least one mapping role must be designated as an **admin** with administrative privileges. Additionally, the user configuring the group must be a part of the group mapped to the **Admin** role. Otherwise you won't be able to operate as an administrator in your account or access and edit the role mapping again.
* [Okta Role Mapping-Step 8](/docs/blink-platform/account-management/identity-providers/okta)
* [Google Role Mapping-Step 8](/docs/blink-platform/account-management/identity-providers/google)
* [Azure AD](/docs/blink-platform/account-management/identity-providers/azure)
* [Cloudflare](/docs/blink-platform/account-management/identity-providers/cloudflare)
Role mapping rules are evaluated sequentially, the first matching rule determines the user’s assigned role mapping. You can easily adjust the evaluation order by clicking the icon and dragging each group to your preferred position.
![]()
***
### SAML Authorized Domains
SAML Authorized Domains cannot be populated by the user
Identity providers, for example [Okta](/docs/blink-platform/account-management/identity-providers/okta), do not independently validate domain ownership. As a result, customers requesting domain-related updates will contact Customer Support (CS) for assistance. CS will then verify that the requested domains are legitimately associated with the customer before applying any changes.
This verification step is required to prevent impersonation and ensure that only authorized domains are linked to a customer’s identity provider configuration.
![]()
***
### SAML Session Lifetime
Select the duration (in hours or days) a user can remain logged into their account before being automatically logged out and required to log in again.
The default time out is `30` days.
![]()
***
### SAML Strict Mode
Choose whether you would like to enable **SAML Strict Mode** by checking the box. When enabling **SAML Strict Mode**, all organization users who are not administrators must use **SAML** to sign in to Blink. Admins retain access to alternative sign-in modes for troubleshooting purposes.
![]()
***
# Configuring a SAML application on Okta
Source: https://docs.blinkops.com/docs/blink-platform/account-management/identity-providers/okta
Instructions on how to configure a SAML SSO application with Okta.
Log in to Okta, go to the admin dashboard, and select "Applications" in the navigation panel.
Select "Create App Integration".
![]()
Select "SAML 2.0" and click 'Next'.
![]()
Enter an "App Name" and click Next.
![]()
Please note that the **IdP-Initiated Login URL**, **Service Provider ID (SP Entity ID)**, **Service Provider Login URL (SSO URL)** and **Service Provider Logout URL (SLO URL)** can be located within the SAML tab under the Account Management Settings section within the Blink Platform.
**IdP-Initiated Login URL** : Please look in the Account Management Settings section within the Blink Platform to find your unique **IdP-Initiated Login URL**.
**Service Provider ID (SP Entity ID)** : urn:amazon:cognito:sp:us-east-1\_Nu63sypSS
**Service Provider Login URL (SSO URL)** : `https://cognito.blinkops.com/saml2/idpresponse`
**Service Provider Logout URL (SLO URL)** : `https://cognito.blinkops.com/saml2/logout`
![]()
**Please Note** users who use on-premise deployment, please **do not** use the above values to complete the **Create SAML Integration** section of the Okta application, instead you should login to your **own** on-premise deployment app and use the unique values provided in the **SAML** tab under the **Account Management Settings**.
Using the unique **IdP-Initiated Login URL** available in the SAML tab under the Account Management Settings section within the Blink Platform, proceed to the **Create SAML Integration** section of the application and copy and paste the URL value in the **Single Sign-On URL** text field. Then copy and paste the **Service Provider Login URL (SSO URL)** value in **both** the **Recipient URL** text field and the **Destination URL** text field. Lastly copy and paste the **Service Provider ID (SP Entity ID)** value in the **Audience URI (SP Entity ID)** text field.
![]()
Scroll down to the “Attribute Statements” section and add the following key-value pairs, and then click Next.
![]()
Then scroll down to the "Group Attribute Statement" section and fill out the following fields like portrayed in the following image:
The error message in the image indicates: **"Invalid SAML response received: The value of the attribute custom:groups must have a length less than or equal to 2048 characters."**
![]()
### Cause of the Error:
This error occurs because the **SAML response from the client's Identity Provider (IdP)** includes a `custom:groups` attribute whose **total character length exceeds AWS Cognito's 2048-character limit** for string attributes.
In this specific case:
* The client configured **group mapping using a wildcard**, which sends **all the user's group memberships** via SAML.
* As a result, Cognito receives a very long string of group names combined, pushing the total value over the 2048-character limit.
* Cognito then **rejects the login attempt**, since it cannot store or process that oversized attribute.
***
### Recommended Solution:
To fix this, **stop using wildcard group mapping** and instead implement **manual group mapping** in the IdP SAML configuration.
#### What to do:
* The client should **explicitly map only the relevant groups** required by Blink, such as:
* `Blink Builders`
* `Blink Users`
* `Blink Admins`
* This will **limit the number and size** of the groups included in the SAML assertion, ensuring the `custom:groups` attribute stays within Cognito’s size constraints.
Using wildcards (e.g., `*`) sends **all** group memberships, including unrelated or nested ones. This makes it unpredictable and highly prone to exceeding limits,especially in large organizations. This change needs to be made **in the client’s IdP application settings**, not in Blink or Cognito itself.
![]()
Then head to the **SAML** tab under the **Account Management Settings** section within the Blink Platform and click the [Role Mapping](/docs/blink-platform/account-management/identity-providers/identity-providers#role-mapping) section and select the applicable values.
When a user belongs to multiple Okta groups, Blink resolves role assignment in SAML SSO using a **top-down priority order** based on the `Group:Role` mapping table. The first matching group in the list determines the assigned role.
Please note that in the **Mapping** section, at least one mapping role must be designated as an **admin** with administrative privileges. Additionally, the user configuring the group must be a part of the group mapped to the **Admin** role. Otherwise you won't be able to operate as an administrator in your account or access and edit the role mapping again.
![]()
Select “I’m an Okta customer adding an internal app” from the options menu, and then click Finish.
![]()
To give users permission to authenticate via this SAML app, you will need to assign users or groups.
Click on the "Assignments" tab and assign the users or groups you require.
![]()
Click on the "Sign On" tab and scroll down to the "SAML Signing Certificates".
![]()
Click on "View SAML setup instructions".
![]()
Next, under the **Optional** section at the bottom, copy the **IDP metadata** values.
![]()
Next, navigate to the **SAML** section found within the SAML tab in the Account Management Settings. Paste the **IDP metadata** values into the designated text field labeled 'Metadata File'.
![]()
# Resetting your password
Source: https://docs.blinkops.com/docs/blink-platform/account-management/resetting-your-password
Instructions about how to reset your password if you have forgotten it
If you forget your password you can easily renew it.
1. On the log-in page, click **Forgot Password**. You will be redirected to the **Forgot password** page.
![]()
2. Enter the email address that is associated with your Blink account and click **Submit**. An email will be sent to your inbox.
3. Go to your inbox, open the email from Blink, and click **Reset password**. You will be redirected to the **Reset password** page. If you didn't receive an email, click **Send Again**.
4. Enter a new password, confirm the password, and click **Log in**. *Your password has been changed successfully* appears.
5. Click **Log in** and log in with your new password.
# RBAC and User Roles
Source: https://docs.blinkops.com/docs/blink-platform/account-management/roles
Understand and configure user roles and permissions within your Blink organization.
In the Blink Platform, access permissions to Blink resources and their functionality are managed through Role-based Access Control (RBAC) and User Roles. Blink Users are assigned User Roles based on two distinct scopes: the [Tenant scope](#tenant-user-role-scope) and the [Workspace Scope](#workspaces-user-role-scope). The Tenant scope covers permissions across the entire tenant, while the Workspace scope focuses on permissions within individual workspaces. Each role has its own set of predefined roles and permissions. Every Blink user has at least one Tenant Role and a separate Workspace role for each workspace they are part of. User Roles can differ between workspaces; for example, you might be an Owner in one workspace and a Contributor in a different workspace. Additionally, you have the option to [create your own custom user roles](#adding-a-new-role).
![]()
***
## Important Key Terms to Understand: RBAC, Scopes and User Roles
1. **Role-Based Access Controls (RBAC)** is a system that limits network access based on an individual's role within an organization. It involves assigning permissions and privileges to ensure users have the appropriate level of access according to their roles and responsibilities.
2. **Scopes** - A scope defines where specific tasks a [user](/docs/blink-platform/account-management/accounts#users) or [service account](/docs/blink-platform/account-management/accounts#accounts) in an organization can be performed.
3. **User Roles** are aggregations of scopes that define what tasks a user can perform based on the access permissions assigned to their role within the organization.
***
## Tenant Role Scope
Under the **Tenant Role Scope**, you can be assigned a built-in user role as an [Admin](#admin), [Builder](#builder), [Consumer](#consumer), [Tenant Guest](#tenant-guest) or any custom user role created in your Tenant scope.
### 1. Admin
As an Admin, you have full access to all Workspaces and control over all **tenant** settings.
Please note that users assigned an [Admin Role in the Tenant Scope ](#1-admin) have editing permissions across **all** tenant workspaces.
| Feature | Description | Permissions |
| ---------------- | ----------------------------------- | ----------------------- |
| Account Settings | View entities and settings | account:view |
| Account Settings | Invite users to the account | account:invite |
| Account Settings | Manage own API keys | account:api\_keys:edit |
| Account Settings | Create entities and update settings | account:edit |
| Blink Portal | View Apps | portal:app:view |
| Blink Portal | View Agents | portal:agent:view |
| Blink Portal | View Services | portal:service:view |
| Blink Portal | Execute Apps | portal:app:execute |
| Blink Portal | Execute Agents | portal:agent:execute |
| Blink Portal | Execute Services | portal:service:execute |
| Workspaces | View Workspaces | workspace:view |
| Workspaces | View Personal Workspace | workspace:view:personal |
| Workspaces | Create Workspaces | workspace:create |
***
### 2. Consumer
As a Consumer, you have Blink Portal read and execute access only.
#### Blink Portal
| Feature | Description | Permissions |
| ------------ | ---------------- | ---------------------- |
| Blink Portal | View Apps | portal:app:view |
| Blink Portal | View Agents | portal:agent:view |
| Blink Portal | View Services | portal:service:view |
| Blink Portal | Execute Apps | portal:app:execute |
| Blink Portal | Execute Agents | portal:agent:execute |
| Blink Portal | Execute Services | portal:service:execute |
***
### 3. Builder
As a Builder, you have access to workspaces you are a member of and have full access to the Self Service Portal.
| Permissions | Description | Feature |
| ---------------- | ----------------------- | ----------------------- |
| Account Settings | Manage own API keys | account:api\_keys:edit |
| Blink Portal | View Apps | portal:app:view |
| Blink Portal | View Agents | portal:agent:view |
| Blink Portal | View Services | portal:service:view |
| Blink Portal | Execute Apps | portal:app:execute |
| Blink Portal | Execute Agents | portal:agent:execute |
| Blink Portal | Execute Services | portal:service:execute |
| Workspaces | View Workspaces | workspace:view |
| Workspaces | View Personal Workspace | workspace:view:personal |
| Workspaces | Create Workspaces | workspace:create |
***
### 4. Tenant Guest
As a Tenant Guest, you have only access permissions to view Workspaces.
| Permissions | Description | Scope |
| ----------- | --------------- | -------------- |
| Workspaces | View Workspaces | workspace:view |
***
## Workspaces Role Scope
Under the **Workspace Role Scope**, you can be assigned a built-in role as an [Owner](#owner), [Contributor](#contributor), [Viewer](#viewer) or [Case Management Guest](#case-management-guest) or any custom Workspace user role created in your Tenant.
To assign a user a **Workspace Role**, follow these [instructions](/docs/blink-platform/account-management/workspace-management#manage-members).
### 1. Owner
As an owner, you have full access to the workspace and workspace settings.
| Feature | Description | Permissions |
| -------------------- | --------------------------------------------------------------- | ----------------------------- |
| Agents and Workflows | Read-only access to workflow and agent configurations | agent\_workflow:view |
| Agents and Workflows | Execute workflows or interact with agents | agent\_workflow:execute |
| Agents and Workflows | Create, modify, and configure workflow steps or agent behaviors | agent\_workflow:edit |
| Agents and Workflows | Publish workflows and agents changes | agent\_workflow:publish |
| Agents and Workflows | Review and approve workflow changes | workflow:approve |
| Agents and Workflows | Publish approved workflows | workflow:publish\_approved |
| Agents and Workflows | Share workflows and agents to portal | agent\_workflow:portal\_share |
| Case Management | View existing cases | case\_management:view |
| Case Management | Create and edit cases. | case\_management:edit |
| Case Management | Close cases. | case\_management:close\_case |
| Case Management | Delete Cases. | case\_management:delete\_case |
| Case Management | Manage case management settings. | case\_management:admin |
| Connections | View existing connections | connections:view |
| Connections | Create and edit connections | connections:edit |
| Dashboards | View existing dashboards | dashboard:view |
| Dashboards | Share dashboards to portal | dashboard:portal\_share |
| Dashboards | Create and edit dashboards | dashboard:edit |
| Global Variables | View existing global variables | global\_variables:view |
| Global Variables | Create and edit global variables | global\_variables:edit |
| Runners | View existing runners | runners:view |
| Runners | Create and edit runners | runners:edit |
| Tables | View existing tables | tables:view |
| Tables | Execute actions and responses | tables:execute |
| Tables | Create and edit tables | tables:edit |
| Workflows | View existing workflows | Workflow:view |
| Workflows | Execute workflows | workflow:execute |
| Workflows | Share workflows to portal | workflow:portal\_share |
| Workflows | Create and edit workflows | workflow:edit |
| Workflows | Can Publish Approved Workflows | workflow:publish\_approved |
| Workflows | Approve Workflows | workflow:approve |
| Workflows | Publish Workflows | workflow:publish |
| Workspaces | Share workspaces resources | workspaces:share |
| Workspaces | Update workspace settings | workspaces:edit |
| Workspaces | Delete workspaces | workspaces:delete |
***
### 2. Contributor
As a contributor, you have full access to the workspace, but without access to the workspace settings.
| Feature | Description | Permissions |
| -------------------- | --------------------------------------------------------------- | ----------------------------- |
| Agents and Workflows | Read-only access to workflow and agent configurations | agent\_workflow:view |
| Agents and Workflows | Execute workflows or interact with agents | agent\_workflow:execute |
| Agents and Workflows | Create, modify, and configure workflow steps or agent behaviors | agent\_workflow:edit |
| Agents and Workflows | Publish workflows and agents changes | agent\_workflow:publish |
| Agents and Workflows | Review and approve workflow changes | workflow:approve |
| Agents and Workflows | Publish approved workflows | workflow:publish\_approved |
| Agents and Workflows | Share workflows and agents to portal | agent\_workflow:portal\_share |
| Case Management | View existing cases | case\_management:view |
| Case Management | Create and edit cases. | case\_management:edit |
| Case Management | Close cases. | case\_management:close\_case |
| Case Management | Delete Cases. | case\_management:delete\_case |
| Case Management | Manage case management settings. | case\_management:admin |
| Connections | View existing connections | connections:view |
| Connections | Create and edit connections | connections:edit |
| Dashboards | View existing dashboards | dashboard:view |
| Dashboards | Share dashboards to portal | dashboard:portal\_share |
| Dashboards | Create and edit dashboards | dashboard:edit |
| Global Variables | View existing global variables | global\_variables:view |
| Global Variables | Create and edit global variables | global\_variables:edit |
| Runners | View existing runners | runners:view |
| Runners | Create and edit runners | runners:edit |
| Tables | View existing tables | tables:view |
| Tables | Execute actions and responses | tables:execute |
| Tables | Create and edit tables | tables:edit |
| Workflows | View existing workflows | workflow:view |
| Workflows | Execute workflows | workflow:execute |
| Workflows | Share workflows to portal | workflow:portal\_share |
| Workflows | Create and edit workflows | workflow:edit |
| Workflows | Can Publish Approved Workflows | workflow:publish\_approved |
| Workflows | Approve Workflows | workflow:approve |
| Workflows | Publish Workflows | workflow:publish |
| Workspaces | Share workspace resources | workspaces:share |
***
### 3. Viewer
As a viewer, you can only observe the mentioned features without the ability to edit or create them.
| Feature | Description | Permissions |
| -------------------- | ----------------------------------------------------- | ---------------------- |
| Agents and Workflows | Read-only access to workflow and agent configurations | agent\_workflow:view |
| Case Management | View existing cases | case\_management:view |
| Connections | View existing connections | connections:view |
| Dashboards | View existing dashboards | dashboard:view |
| Global Variables | View existing global variables | global\_variables:view |
| Runners | View existing runners | runners:view |
| Tables | View existing tables | tables:view |
| Workflows | View existing workflows | workflow:view |
***
### 4. Case Management Guest
As a Case Management Guest, you have access permissions to specific cases within Case Management.
| Feature | Description | Scope |
| --------------- | ---------------------------------------------------------------------------------------- | --------------------------- |
| Case Management | Edit only the cases shared with the user and their groups, including any linked entities | case\_management:restricted |
***
## Adding a New Custom Role
1. In the top-right corner, click the **New Role** button.
2. A dialogue box will open, displaying all **user role permissions**.
3. Add a **Role Name** and a **Role Description**.
4. Select a **Role Scope** by selecting between a **Tenant Role** or a **Workspace Role** from the dynamic dropdown.
Please note that **Tenant Role** or a **Workspace Role** have different access permissions
| **Feature** | **Permission** | **Description** |
| -------------------- | ------------------------- | --------------------------------------- |
| **Account settings** | `account:view` | View entities and settings |
| | `account:invite` | Invite users to the account |
| | `account:edit` | Create entities and update all settings |
| **Blink Portal** | `portal:app:view` | View apps |
| | `portal:service:view` | View services |
| | `portal:app:execute` | Execute apps |
| | `portal:service:execute` | Execute services |
| **Workspaces** | `workspace:view` | View user’s associated workspaces |
| | `workspace:view:personal` | Access user’s personal workspace |
| | `workspace:create` | Create workspaces |
| Feature | Permission | Description |
| -------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------- |
| **Case Management** | `case_management:restricted` | View and edit only the cases shared with the user and their groups, including any linked entities |
| | `case_management:view` | View existing cases |
| | `case_management:edit` | Create and edit cases |
| | `case_management:close_case` | Close cases |
| | `case_management:delete` | Delete case management entities |
| | `case_management:admin` | Manage case management settings, including editing a case, closing a case, and deleting a case |
| **Connections** | `connection:view` | View existing connections |
| | `connection:edit` | Create and edit connections |
| **Dashboards** | `dashboard:view` | View existing dashboards |
| | `dashboard:edit` | Create and edit dashboards |
| **Global Variables** | `global_variable:view` | View existing global variables |
| | `global_variable:edit` | Create and edit global variables |
| **Runners** | `runner:view` | View existing runners |
| | `runner:edit` | Create and edit runners |
| **Tables** | `table:view` | View existing tables |
| | `table:edit` | Create and edit tables |
| **Workflows** | `workflow:view` | View existing workflows |
| | `workflow:execute` | Execute workflows |
| | `workflow:edit` | Create and edit workflows |
| | `workflow:publish` | Publish workflows |
| | `workflow:approve` | Review and approve workflow changes |
| | `workspace:share` | Share workspace resources |
| | `workspace:edit` | Update workspace settings |
| | `workspace:delete` | Delete workspace |
***
5. Then, select the relevant checkboxes to customize user role permissions and then click the **create** icon.
![]()
# PRIVACY POLICY
Source: https://docs.blinkops.com/docs/blink-platform/account-management/security-and-legal/privacy-policy
Blink Ops privacy policy covering data collection, usage, and protection practices.
# PRIVACY POLICY
IMPORTANT: BY USING BLINK OPERATIONS INC.'S AND ITS AFFILIATES ("**Blink**" OR "**WE**") SERVICES AND WEBSITE (THE "**SERVICES**") YOU CONSENT TO THE TERMS AND CONDITIONS OF THIS PRIVACY POLICY AND CONSENT THAT ALL PERSONALLY IDENTIFIABLE INFORMATION ("**PII**") THAT YOU SUBMIT OR THAT IS PROCESSED OR COLLECTED THROUGH THE SERVICES MAY BE PROCESSED BY BLINK IN THE MANNER AND FOR THE PURPOSES DESCRIBED IN THE FOLLOWING PRIVACY POLICY. Any capitalized terms not defined herein shall have such meaning ascribed to them in the Blink Terms of Service.
We recognize that privacy is important. This policy applies to all of the software, services, information, tools, features and functionality available on the Services offered by Blink or its subsidiaries or affiliated companies and covers how PII that Blink collects and receives, including in respect of any use of the Services, is treated. If you have any questions about this policy, please feel free to contact us using the contact details published on our Services or directly at [privacy@blinkops.com](mailto:privacy@blinkops.com).
IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS SET FORTH HEREIN PLEASE DO NOT USE THE SERVICES.
1. **Information We Collect and How We Use It. In order to provide and improve our Services, we may collect PII, including the following types of information:**
* **Information You Provide.** When you subscribe to the Services or otherwise during the Account creation process, we ask you for personal information, including full name, email address, professional affiliation and other information you may provide.
* **User Communications.** When you send an email or other communication to Blink, we may retain those communications in order to process your inquiries, respond to your requests and improve our Services. We may send you push notifications to send you news and updates in respect of the Services. We may also send you newsletters and promotional communications, you may opt-out of this service at any time by unsubscribing in the link provided in such communications.
* **Aggregated and Analytical Data.** In an ongoing effort to better understand and serve the users of the Services, Blink often conducts research on its users demographics, interests and behavior based on the PII and other information provided to us. This research may be compiled and analyzed on an aggregate basis, and Blink may share this aggregate data with its affiliates, agents and business partners. This aggregate information does not identify you personally. Blink may also disclose aggregated user statistics in order to describe our services to current and prospective business partners, and to other third parties for other lawful purposes.
* **User Activity.** When you use the Services, we may automatically receive and record technical information regarding the method and nature of your use of the Services and information from your browser, including without limitation information and statistics about your search activity, session times, impressions, pages visited, online/offline status, IP address, internet service provider, type of browser, regional and language settings and software and hardware attributes, unique device identifier, advertising identifier and location (including geolocation, beacon based location, and GPS location). An IP address is a numeric code that identifies your browser on a network, or in this case, the Internet. Your IP address is also used to gather broad demographic information. Blink uses all of the PII that we collect to understand the usage trends and preferences of our users.
2. **Cookies; web beacons and third party processors.**
In order to collect the data described herein, support your login and identify you, we may use temporary cookies that remain on your device for a limited period of time. We may also use persistent cookies that remain on your device until manually removed in the settings of your device/browser, in order to manage and maintain the services and record your use of the Services. Cookies by themselves cannot be used to discover the identity of the user. A cookie is a small piece of information which is sent to and stored on your device. Cookies do not damage your device. Most browsers or devices may allow you to block cookies but you may not be able to use some features on the Services if you block them. You may set most browsers to notify you if you receive a cookie (this enables you to decide if you want to accept it or not). We may also use web beacons via the Services to collect information. Web beacons or "gifs", are electronic images that may be used in our Services or in our emails. We use Web beacons to deliver cookies, count visits and to tell if and when an email has been opened and acted upon. We also use third party tracking technologies, such as cookies and web beacons and various third party providers to process and analyze your PII, profile end user activities and provide targeted ads, including without limitation tracking your use of the Services and third party services and site
3. **Links.**
Links to other services, sites and applications may be provided by Blink as a convenience to our users. Blink is not responsible for the privacy practices or the content of other sites and applications and you visit them at your own risk. This privacy statement applies solely to PII collected by us.
4. **Minors.**
If you are a minor under the age of 18, you must obtain parental consent prior to using our Services. Blink will not knowingly contact or engage with minors under the age of 18 without said parental consent. If you have reason to believe that a child has provided us with their PII, please contact us at the address given above and we will endeavor to delete that PII from our databases.
5. **Information Sharing.**
As part of providing the Services and/or generating and processing analytics, our affiliates, agents representatives and third party providers may have access to your PII. Blink may also share PII in the following circumstances: (a) as required for the provision, maintenance and improvement of the Services; (b) if we become involved in a reorganization, merger, consolidation, acquisition, or any form of sale of some or all of our assets (which sale may be to an entity registered or incorporated in a different jurisdiction than Blink); and/or (c) to satisfy applicable law or prevention of fraud or harm or to enforce applicable agreements and/or their terms, including the Terms of Services, including investigation of potential violations thereof
6. **Information Security.**
We follow generally accepted industry standards to protect against unauthorized access to or unauthorized alteration, disclosure or destruction of PII. However, no method of transmission over the Internet, or method of electronic storage, is 100% secure. Therefore, while we strive to use commercially acceptable means to protect your PII, we cannot guarantee its absolute security. We keep your PII only for as long as reasonably necessary for the purposes for which it was collected or to comply with any applicable legal or ethical reporting or document retention requirements
7. **Data Integrity, Accessing and Updating Personal Information.**
Blink processes PII only for the purposes for which it was collected and in accordance with this policy or any applicable service agreements. We review our data collection, storage and processing practices to ensure that we only collect, store and process the PII needed to provide or improve our Services. We take reasonable steps to ensure that the PII we process is accurate, complete, and current, but we depend on our users to update or correct their PII whenever necessary. Nothing in this policy is interpreted as an obligation to store information, and we may, at our own discretion, delete or avoid from recording and storing any and all information.
8. **Your Rights.**
* **Right of Access and Rectification.** You have the right to know what PII we collect about you and to ensure that such data is accurate and relevant for the purposes for which we collected it. We allow our users the option to access and obtain a copy of their PII and to rectify such PII if it is not accurate, complete or updated. However we may first ask you to provide us certain credentials to permit us to identify your PII.
* **Right to Delete PII or Restrict Processing.** You have the right to delete your PII or restrict its processing. We may postpone or deny your request if your PII is in current use for the purposes for which it was collected or for other legitimate purposes such as compliance with legal obligations.
* **Right to Withdraw Consent.** You have the right to withdraw your consent to the processing of your PII. Exercising this right will not affect the lawfulness of processing your PII based on your consent before its withdrawal.
* **Right of Data Portability.** Where technically feasible, you have the right to ask to transfer your PII in accordance with your right to data portability.
You may exercise the above rights by sending a request to [privacy@justBlink.com](mailto:privacy@justBlink.com).
* **Right to Request Information on Transfers.** You have the right to request certain details of the basis on which your PII is transferred outside the European Economic Area. Please be aware that certain information relating to such transfers may be partially redacted or restricted due to data transfer agreements or reasons relating to commercial confidentiality.
* **Right to Lodge Complaint.** You also have the right to lodge a complaint with a data protection supervisory authority regarding the processing of your PII
9. **Enforcement.**
Blink regularly reviews its compliance with this policy. Please feel free to direct any questions or concerns regarding this policy or our treatment of PII by contacting us as provided above. When we receive formal written complaints it is Blink's policy to contact the complaining user regarding his or her concerns. We will cooperate with the appropriate regulatory authorities, including local data protection authorities, to resolve any complaints regarding the transfer of PII that cannot be resolved between Blink and an individual
10. **Changes to This Privacy Policy.**
Blink may update this policy. We will notify you about significant changes in the way we treat PII by sending a notice to the primary email address specified in your account or by placing a prominent notice on the Services. We encourage you to periodically review this policy for the latest information about our privacy practices
11. **Consent To Processing.**
By providing any PII to us pursuant to this policy, all users, including, without limitation, users in the United States, Israel and member states of the European Union, fully understand and unambiguously consent to this policy and to the collection and processing of such PII abroad. The server on which the Services are hosted and/or through which the Services are processed may be outside the country from which you access the Services and may be outside your country of residence. Some of the uses and disclosures mentioned in this policy may involve the transfer of your PII to various countries around the world that may have different levels of privacy protection than your country. By submitting your PII through the Services, you consent, acknowledge, and agree that we may collect, use, transfer, and disclose your PII as described in this policy. If you do not consent to the terms of this policy, please do not use the Services
12. **Questions.**
If you have any questions about this policy or concerns about the way we process your PII, please contact us using the contact details published on our Services. If you wish to delete all information regarding your use of the Services, please contact us at [privacy@blinkops.com](mailto:privacy@blinkops.com)
13. **Your California Privacy Rights and Do Not Track Notices.**
California Civil Code Section 1798.83 permits customers of Blink who are California residents to request certain information regarding its disclosure of PII to third parties for their direct marketing purposes. To make such a request, please contact us at [privacy@blinkops.com](mailto:privacy@blinkops.com). Please note that we are only required to respond to one request per customer each year. You are also advised that Blink does not respond to “Do Not Track” signals
# Security Statement
Source: https://docs.blinkops.com/docs/blink-platform/account-management/security-and-legal/security-statement
Blink Ops security statement outlining platform security measures and compliance standards.
This document addresses the security implications of a Blink hybrid deployment where the Runner is self-hosted (on-premises), but other aspects of the platform are performed by the SaaS controller. This document shows how the Blink platform may be incorporated into any cloud environment, while keeping customer's cloud environment secured.
## Security principles
**Minimal trust methodology**
Blink has adopted a minimal trust methodology to keep customers as independent as possible from Blink when it comes to their security posture. Blink is designed to serve as an abstraction & automation level over existing SaaS services that are being used by the customers, and by that prevents granting power/trust to Blink to take actions on customer’s behalf.
**Data security**
To create a secure environment for users, data security measures in all aspects are taken. Security of data in transit, stored data, secured backups, strict data access principles, cloud security posture etc. have been taken into account during the creation and maintenance of the Blink platform.
**Role-based access control (RBAC)**
Blink allows granular RBAC permission management, using roles, permissions, workspaces, groups, and resources. Using Blink’s RBAC, customers are able to import existing permissions of users from their existing SaaS permissions, as well as utilizing different authorization approaches under RBAC within the account.
## Data security
Blink SaaS data flow diagram
![]()
**Data in rest**
Data stored at rest on Blink premise, will always be stored at an encrypted state. When using Blink's hybrid model, the following data types are stored in Blink SaaS premise:
* Account metadata
* User details
* Automation content
* Resources names & types
* Logs of Automation executions
Blink does not store the customers secrets when using hybrid deployment. Credentials are stored using Hashicorp’s vault.
**Data in transit**
All in-transit data on the Blink platform and external dependencies, is sent over TLS encrypted networking / industry-standard encryption methodologies. In addition to the data kept at rest on the Blink platform, additional data is forwarded using Blink SaaS to the customer’s utilization through the UI. This data includes:
* User credentials
* Users Automations
* Step outputs
## Main security measures
**Customer identity**
Any action performed by Blink users is signed by a JWT token. The identity token is generated by an external authentication provider and is validated through the customer’s request. By enforcing the performed action signature, Blink mitigates the risk of Man In Middle and Request forgery attack vectors.
**Credentials Security** (Credentials Jail)
1. Blink is relying on external credentials in order to allow users to integrate and interact with external SaaS services. To avoid dangers related to credentials, Blink on-prem solution allows the user to keep all credentials usage on-premise. Blink will integrate to the customer’s secret manager. Currently supported secret managers include Hashicorp Vault and AWS Secret Manager.
2. Usage of credentials on a runner-based system where running code is allowed, imposes the risk of credentials leaking - either by accident or by adversary action. Blink mitigates this risk by applying a Credentials jail - credentials are exposed only to pre-built and acknowledged system actions, rather than being directly exposed to arbitrary usage.
**RBAC permissions management**
Blink allows granular RBAC permission management, using roles, permissions, workspaces, groups, and resources. Using Blink’s RBAC, customers are able to import existing permissions of users from their existing SaaS permissions, as well as utilizing different authorization approaches under RBAC within the account.
## Additional security measures
**Environment Isolation**
Blink offers two run modes in terms of isolation:
1. **Shared environment** - Use the main Blink cloud service, which is shared across multiple accounts. Data is separated by per-tenant separation.
2. **Dedicated SaaS namespace** - Network, data flow, data storage and all business logic is completely separated at this mode. Data is separated on a DB per customer basis.
**High availability and DDOS protection**
The entire stack of Blink service is served on a highly available Kubernetes service. All components shown in the data flow diagram are protected by high availability measures, including crash-recovery. Additionally, all services are protected against OWASP and DDOS.
**Backups**
Data stored on Blink premise is backed up multiple times every day at an encrypted state. Customers may request for their backup data to be deleted, according to GDPR regulations.
**Audits and logs**
All metadata for actions performed on an account is kept for a minimal duration of 6 months, and is accessible by customer's request.
## Security & Privacy policies and standards
In addition to the security measures detailed in this document, Blink acts upon the highest industry standards on security topics. Blink can provide documentation related to these topics at the customer's request. These topics include the following:
1. Compliance
2. Password management
3. Permission access management
4. Privacy policy
5. Risk assessment
6. Third-party vendor management
7. Key management and information security
8. Incident response
9. Auditing
10. Environment security
11. Data retention and erasure
12. Backup policy
13. Endpoint security
# About the Blink Platform
Source: https://docs.blinkops.com/docs/blink-platform/blink-platform
In the Blink Platform section of the documentation, you can find all the necessary information related to the Blink Platform and its features.
Learn how to create and manage tables.
Visualize data with custom dashboards.
Automate workflows through the Blink Portal
Manage user accounts and permissions.
### Blink Platform Navigation
When a new user first enters Blink, a personal [workspace](#workspaces) is automatically created. In the left-hand navigation bar at the top, you'll find all the essential features of your workspace.
The top section of the navigation bar features the main workspace features: [Workflows](/docs/workflows/workflows), [Tables](#tables), [Dashboards](#dashboards), [Workspace Settings](#workspaces) and [Cases](#cases) (when enabled in your workspace settings)
Under [Workflows](/docs/workflows/workflows) you'll find a nested submenu with the following pages : [Connections](/docs/workflows/building-workflows/connections/connections), [Global Variables](#global-variables), [Runners](#runners), [Executions](/docs/workflows/monitoring-workflows-health#past-executions), and [Templates](#templates).
**Tenant-level** information is found at the bottom of the navigation bar. Here, you can access the [Overview Dashboards](#blink-platform), the [Self-Service Portal](#self-service-portal), [Approval Management](/docs/workflows/managing-workflows/publish-approval/publish-approval), and [Account Settings](/docs/blink-platform/account-management/account-management). Just click on the feature you wish to access.
![]()
### Workspaces
`Workspaces` 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 Workflows Pack page.
See [Workspaces](/docs/blink-platform/workspaces/workspaces) for more details.
![]()
### Runners
The Runner serves as the essential element in executing all actions within a Workflow. It offers the flexibility of deployment either on the Blink cloud infrastructure or within your own environment. To enhance scalability and distribute the workload efficiently, you have the option to create a runner group that can incorporate multiple instances of the runner.
![]()
### Tables
Tables enable you to present and interact with data in Blink, unlocking new Workflow possibilities. Since your Workflow can write to Tables and read data from them, this enables you to create stateful workflows. See the [Tables](/docs/blink-platform/tables/tables) for more details.
![]()
### Dashboards
Dashboards are visual interfaces for presenting data in Tables across the Blink Platform.
![]()
### Self-service Portal
Blink enables you to create Workflows that streamline workflows, and securely share them with other teams and workspaces. Users granted access can easily use the Workflows and move on to the next important job, without waiting for someone to create or do a task for them. You can use any existing Automation that is shared with (exposed to) you. All Workflows that are shared with you are listed in your Self-service portal. The `Self-service Portal` cuts out the middle-man enabling a more efficient work process. Visit the [Blink Portal](/docs/blink-platform/blink-portal/blink-portal#approvals-and-requests) for more details.
![]()
### Web forms
The **Web Form** feature is vital for collecting user input through a **sharable web form**. The **web form** can be sent in the middle of the Workflow so it can incorporate data from previous steps. It can also affect the subsequent steps of the workflow. Users can tailor the form as desired and easily share it with other users via a link. Visit the [Web Forms](/docs/blink-platform/web-form/web-form) for more details.
![]()
### Account Management
Everything related to Account Management and Account Settings can be found in this section. Visit the [Account Management](/docs/blink-platform/account-management/account-management) for more details.
### Service Providers and Tenant Management
Blink customers have the option to designate a Service Provider (MSP, MSSP) to oversee the management of their account. By doing so, the Service Provider can develop customized Workflows tailored to the specific needs of the end-users, as well as manage and update them to guarantee a reliable and secure workspace. Moreover, the Service Provider can promptly address any issues that may arise, ensuring uninterrupted operations and a seamless user experience. Visit the [Service Providers and Tenant Management](/docs/blink-platform/service-providers/service-providers) for more details.
![]()
# Blink Bot For Slack
Source: https://docs.blinkops.com/docs/blink-platform/blink-portal/blink-bot-for-slack
Use the Blink bot for Slack to run self-service portal workflows directly from your Slack workspace.
## Using the Self-service Portal via Slack
Blink has created bot for Slack to seamlessly execute apps available in the Self-service portal directly from your Slack environment. Every Workflow that is exposed in the portal is automatically exposed to the bot for Slack.
Please note only admins can connect the Blink Bot for Slack
## Connecting Slack to the Blink platform
To run workflows directly from Slack, you need to connect your Slack workspace to your Blink account. Follow these steps:
1. In the Blink Platform, go to the bottom left corner and click your profile icon (a colored circle with your initials).
2. Navigate to **General**, then scroll to the **Bot for Slack** section. Click **Connect to Slack**.
3. A permission request dialog will appear, asking for access to your Slack workspace.
4. Click **Allow** to grant permission. Once connected, you’ll see **Connected to Slack** in your account settings.
## Executing a Workflow via Slack
![]()
1. In any channel or conversation, enter ***/***. Select **Portal** from the drop down menu.
2. If you are not logged in to the Blink platform, you will receive a message to **Go to login page**. Click **Go to login page** and log in to Blink. If you logged in successfully, **Thanks for logging in** will appear on your Slack feed.
3. Enter ***/portal*** and click **Self service portal request**. A list of all items available in the Self-service portal is displayed.
4. Click on any item in the portal. You will receive a message that the Workflow is running. If the Workflow needs input parameters, you will be prompted to enter them before running.
The Blink bot will notify you of your request, the Workflow state and its results.
# The Blink Portal
Source: https://docs.blinkops.com/docs/blink-platform/blink-portal/blink-portal
Overview of the Blink Portal for sharing workflows, dashboards, and self-service automation with your team.
The Blink Portal is an interface which allows users to execute workflows with a single click, view and export dashboards effortlessly, and tap into the full suite of resources your teams have built, right from one streamlined interface.
**Note**: Although you can run and interact with workflows and dashboards in the Blink Portal, you cannot modify any of the workflows or dashboards displayed there.
***
## Customize the Blink Portal Logo and Header
![]()
1. To customize your Blink Portals Logo and Header, navigate to your [General Settings](/docs/blink-platform/account-management/general)
2. Upload your custom logo and update the portal header as needed, then save your changes. Once saved, your updates will be automatically applied to the Blink Portal’s header and logo.
![]()
***
**The Blink Portal is separated into two separate tabs:**
For detailed guidance on Workflows, see our [Workflows Documentation](/docs/workflows/workflows).
In the **Services** tab of the Blink Portal, you can access all **published** and **active** workflows available in your tenant:
* **Filter by workspace:** Narrow down workflows based on the workspace they belong to.
* **Filter by tags:** View workflows according to the tags assigned to them.
* **Search bar:** Quickly locate a specific workflow by name or keyword.
![]()
Once you find the workflow you want, enter any required input parameters and the run the workflow.
![]()
***
## Blink Portal Activity
The Blink Portal makes it easy to review and monitor all workflow executions associated with your account.
To access your workflow activity history, open the **Services** tab and click **My Activity** in the upper-right corner.
![]()
A table of all your workflow executions, including their current status and key execution details. This allows you to quickly understand what ran, when it ran, and whether any action is required.
* You can filter the table to display all workflow executions, only workflows that failed during execution in the Blink Portal or only workflows that completed when executing in the workflow
* Next to the 'Date' field, you can select the to filter workflow executions according to a specified date and time
![]()
***
## Share Workflows to the Blink Portal
In the [Workflow Overview](/docs/workflows/managing-workflows/workflow-overview-page) page, you can share and expose the selected workflow to the Blink Portal.
1. On the Workflow page, hover over the workflow you would like to expose to the Blink Portal and click on the "Overview" button.
![]()
2. Toggle the “Blink Portal” button to publish the selected workflow to the Blink Portal. Once enabled, the workflow becomes available for use in the portal.
If you disable this toggle, the workflow will be removed from the Blink Portal and will no longer be available to users.
![]()
***
## Service Settings in the Blink Portal
**Note**: These settings are only available to users with access to the workspace the selected service is part of.
To access the Blink Portal's settings, click the menu and choose from the following options:
1. **Manage Portal Access**- Enter the email address of a user(s) or group(s) within your tenant to share the selected workflow in the Blink Portal.
2. **Navigate to the selected workflow**- Navigate directly to the workflow you have selected in the Blink Portal.
3. Navigate to the **workspace** where the selected workflow is located.
![]()
# Dashboards
For detailed guidance on Dashboards, see [Dashboards Documentation](/docs/blink-platform/dashboards/dashboards).
In the **Dashboard** tab of the Blink Portal, you can access all dashboards you have shared to the Blink Portal
* **Filter by workspace:** Narrow down dashboards based on the workspace they belong to.
* **Filter by tags:** View dashboards according to the tags assigned to them.
* **Search bar:** Quickly locate a specific dashboard by name or keyword.
![]()
***
## View Dashboard in the Blink Portal
Select a 'Dashboard' to open it in the Blink Portal. In the top-right corner, you can configure the auto-refresh interval to control how often the dashboard updates and reflects the most recent data.
By default, the dashboard refreshes **every 5 minutes**.
Available refresh intervals:
* Off (manual refresh only- )
* 5 seconds
* 30 seconds
* 1 minute
* 5 minutes (default)
* 15 minutes
* 30 minutes
* 1 hour
Adjust the refresh setting based on how frequently you want the data to update.
![]()
***
You can also select a **timeframe**, which acts as a **global filter** across the dashboard. This allows you to view only the data created within a specific time window—for example, all cases created in the last 7 days.
**Note:** This filter applies only to widgets whose data source includes the `created_at` field.
The available timeframes are:
* **Today**
* **Last 24 hours** *(default)*
* **Last 7 days**
* **Last 30 days**
![]()
***
## Dashboard Widget's Expanded View
In the dashboards view mode, you can click on a widget to open an expanded view that displays the underlying raw data from the widget’s data source.
Within this expanded view, you can also interact directly with elements of the visualization to further refine the data being displayed. For example, selecting a specific slice in a pie chart or an individual bar in a bar chart will filter the results to show only the raw records associated with that selected element.
This allows you to quickly drill down into the data behind specific parts of the visualization directly from the dashboard.
**Note:** When a widget is grouped by a user field (e.g., Case Manager or custom user fields), the expanded view shows the full underlying dataset
![]()
***
## Dashboard Settings in the Blink Portal
**Note**: These settings are only available to users with access to the workspace the selected dashboard is part of.
To access the Blink Portal's settings, click the menu and choose from the following options:
1. **Manage Portal Access**- Enter the email address of a user(s) or group(s) within your tenant to share the selected dashboard in the Blink Portal.
2. **Navigate to the selected workflow**- Navigate directly to the dashboard you have selected in the Blink Portal.
3. Navigate to the **workspace** where the selected dashboard is located.
![]()
***
## Sharing Dashboards to the Blink Portal
To view a dashboard you created in the Blink Portal, you must first publish and share it. By default, the dashboard is shared only with you, but you can choose to share it with additional users or groups to provide them access.
If you de-activate the dashboard, it will not show up in the Blink Portal
Follow these steps to publish and share a dashboard you created in the Blink Portal:
In the top-right corner of your dashboard, click the **Publish** button to start the sharing process.
![]()
A pop-up will appear asking you to confirm that you want to share the dashboard. Click **Confirm** to proceed.
![]()
After confirmation, you can enter the username(s) or group name(s) you want to share the dashboard with. By default, the dashboard is automatically shared with you and can now be found in the Blink Portal.
![]()
***
## Exporting Dashboards
Once you find the dashboard you want, click on it to explore all its **widgets and data**. You can also **export the dashboard** by clicking the button in the top-right corner of the interface.
![]()
For detailed guidance on Agents, visit the [Agent Documentation](/docs/agent-builder/agent-builder).
In the **Agents** tab of the Blink Portal, you can access all agents that you been shared with you in the Blink Portal.
* **Filter by workspace:** Narrow down dashboards based on the workspace they belong to.
* **Search bar:** Quickly locate a specific dashboard by name or keyword.
![]()
***
## Agent Settings in the Blink Portal
**Note**: These settings are only available to users with access to the workspace the selected dashboard is part of.
To access the Blink Portal's settings, click the menu and choose from the following options:
1. **Manage Portal Access**- Enter the email address of a user(s) or group(s) within your tenant to share the selected agent in the Blink Portal.
2. **Navigate to the selected Agent**- Navigate directly to the agent you have selected in the Blink Portal.
3. Navigate to the **workspace** where the selected agent is located.
![]()
***
# Blink App for Slack
Source: https://docs.blinkops.com/docs/blink-platform/blink-portal/slack-app
Connect workflows to Slack using the Blink app for direct messaging and channel-based automation.
Blink is a platform that enables you to automate your daily work. A workflow is created using actions that integrate with a wide variety of cloud services. This application for Slack enables you to connect each Workflow you create in the [Blink Portal](/docs/blink-platform/blink-portal/blink-bot-for-slack) to your Slack workspace.
## Creating Slack Connection
A connection can be created from the Connections page or from the Workflow Editor page.
Creating a new connection from the connections screen:
1. In the Blink platform, navigate to the **Connections** page > **Add connection**. A New Connection dialog box opens displaying icons of external service providers available.
2. Select the **Slack** icon. A dialog box with name of the connection and connection methods appears.
3. (Optional) Edit the name of the connection. At a later stage you cannot edit the name.
4. Select which method to make the connection. The recommended method appears the blue button. The method can be changed later by editing your connection.
For more information, refer to [Creating a Slack connection](/docs/integrations/slack#creating-a-slack-connection).
## Slack Actions and Triggers
For the full list of supported Slack Actions, refer to Slack [Actions](/docs/integrations/slack/actions) and [Triggers](/docs/integrations/slack/triggers).
To find out further information and instructions about the more advanced Slack actions available, visit the [Slack Interactivity](/docs/workflows/building-workflows/actions/advanced-actions/interactive-actions/slack-interactivity) and [Ask a Question via Slack](/docs/workflows/building-workflows/actions/advanced-actions/interactive-actions/ask-a-question/ask-a-question-slack) sections of the Blink Documentation.
## Automating Slack Workflows with Blink
With Blink, you can trigger automated workflows to create and enrich tickets, manage projects, and send notifications to team members over chat or email.
### Workflow Library Examples
[Onboarding Team Member to Project](https://library.blinkops.com/workflows/onboarding-team-member-to-project)
Preview this Automation on desktop
[Setting Up an Incident Process](https://library.blinkops.com/workflows/setting-up-an-incident-process)
Preview this Automation on desktop
**TIP**
For more premade Automations, visit [Blink Automation Library](https://library.blinkops.com/workflows?vendors=Slack\&level=featured).
## Pricing
For more information, [Schedule a Demo](https://www.blinkops.com/schedule-time) or [Contact Blink](https://www.blinkops.com/contact).
# Blink Teams Bot
Source: https://docs.blinkops.com/docs/blink-platform/blink-portal/team-slackbot
Use the Blink bot for Microsoft Teams to run self-service portal workflows directly from your Teams environment.
## Using the Self-service portal via Teams
We have created the bot for Teams to seamlessly execute apps available in the Self-service portal directly from your Teams environment. Every Workflow that is exposed in the portal is automatically exposed to the bot for Teams.
## Connecting Teams to the Blink platform
To execute Workflows from Teams, a connection between your Teams workspace and your Blink account must be created.
1. In your Teams application, navigate to Apps on the left-hand side of your screen. You will be redirected to the Team's App Marketplace. In the search bar, type "Blink Ops" and click the "Add" button.
2. The Blink App will be added to your Teams application, and a conversation with the Blink Teams Bot will automatically open.
## Executing a Workflow via Teams
1. In your teams app, navigate to the Blink App and start a conversation by entering ***/portal***.
![]()
2. If you are not logged in to the Blink platform, you will receive a message to **Go to login page**. Click **Go to login page** and log in to Blink. If you logged in successfully, **Thanks for logging in** will appear.
![]()
3. Enter ***/portal*** and click **the open dialogue** button. A pop up will appear with a dropdown menu containing a list of all items available in the Self-service portal is displayed.
![]()
4. Click on any item in the portal. You will receive a message that the Workflow is running. If the Workflow needs input parameters, you will be prompted to enter them before running. The Blink bot will notify you of your request, the Workflow state and its results.
# Blink Zoom Bot
Source: https://docs.blinkops.com/docs/blink-platform/blink-portal/zoom-slackbot
Use the Blink bot for Zoom to run self-service portal workflows directly from your Zoom environment.
## Using the Self-service portal via Zoom
We have created the bot for Zoom to seamlessly execute apps available in the Self-service portal directly from your Zoom environment. Every Workflow that is exposed in the portal is automatically exposed to the bot for Zoom.
## Connecting Zoom to the Blink platform
To execute Workflows from Zoom, a connection between your Zoom workspace and your Blink account must be created.
1. On the bottom left-side of your screen, navigate to **Account Settings** > **General** > **Connect to Zoom**. A dialog window opens; **Blink is requesting permission to access the Blink Ops Zoom workspace**.
2. Click **Allow**. **Connected to Zoom** is displayed in your account setting.
(Optional) A **Reconnect** button enables you to reconnect if you have already made this connection, but are experiencing issues.
## Executing a Workflow via Zoom
1. In any channel or conversation, enter ***/***. Select **Portal** from the drop down menu.
2. If you are not logged in to the Blink platform, you will receive a message to **Go to login page**. Click **Go to login page** and log in to Blink. If you logged in successfully, **Thanks for logging in** will appear on your Zoom feed.
3. Enter ***/portal*** and click **Self service portal request**. A list of all items available in the Self-service portal is displayed.
4. Click on any item in the portal. You will receive a message that the Workflow is running. If the Workflow needs input parameters, you will be prompted to enter them before running.
The Blink bot will notify you of your request, the Workflow state and its results.
# Dashboard Building Interface
Source: https://docs.blinkops.com/docs/blink-platform/dashboards/building-a-dashboard/building-a-dashboard
Step-by-step guide to building dashboards with widgets, filters, and data sources in Blink.
## Create your First Dashboard
1. In your selected workspace, go to the 'Dashboards' tab and click 'New Dashboard'.
![]()
2. Choose an icon to customize your dashboard.
3. Provide a name for your dashboard.
4. Choose one of the following categories:
* **Email Security**
* **Cloud Security**
* **Endpoint Security**
* **Network Security**
* **Data Security and Privacy**
* **Credential Security**
* **Insider Threat**
* **Identity and Access Management**
* **SOC & Incident Response**
* **Threat Intelligence**
5. **Optional**- Provide a short description for your dashboard.
![]()
6. You will then be directed to the [Dashboard Building Interface](/docs/blink-platform/dashboards/building-a-dashboard/building-a-dashboard#dashboard-building-interface) where you can start building your dashboard using [Widgets](/docs/blink-platform/dashboards/building-a-dashboard/widgets/widgets).
![]()
# Dashboard Building Interface
The Dashboard Building Interfaces reflect your underlying source data and are represented by different types of widgets. [Widgets](/docs/blink-platform/dashboards/building-a-dashboard/widgets/widgets) are the essential building blocks of the Dashboard Building Interfaces. [Widgets](/docs/blink-platform/dashboards/building-a-dashboard/widgets/widgets) enable you and other collaborators to see and interact with your table’s data in real time.
***
## Dashboard Building Interface Tabs
The Dashboard Building Interface consists of two distinct tabs:
### Editor Mode
In the 'Editor Mode' tab of the Dashboard Building Interface, you can begin building your dashboard by selecting a [data source](/docs/blink-platform/dashboards/building-a-dashboard/source-types/source-types) and selecting [Widgets](/docs/blink-platform/dashboards/building-a-dashboard/widgets/widgets) to represent the data.
![]()
### Preview
In the preview tab of the Dashboard Building Interface, you can view the dashboard you have recently created and how it will look if you choose to activate and publish the dashboard via the [Self-Service Portal](/docs/blink-platform/dashboards/consume-dashboards-via-self-service-portal)
![]()
## Dashboard Widget's Expanded View
In the dashboard's [preview mode](/docs/blink-platform/dashboards/building-a-dashboard/building-a-dashboard#preview), you can click on a widget to open an expanded view that displays the underlying raw data from the widget’s data source.
Within this expanded view, you can also interact directly with elements of the visualization to further refine the data being displayed. For example, selecting a specific slice in a pie chart or an individual bar in a bar chart will filter the results to show only the raw records associated with that selected element.
This allows you to quickly drill down into the data behind specific parts of the visualization directly from the dashboard.
**Note:** When a widget is grouped by a user field (e.g., Case Manager or custom user fields), the expanded view shows the full underlying dataset
![]()
## Customize the Dashboard Building Interface
You can customize the appearance of a [chart widget](/docs/blink-platform/dashboards/building-a-dashboard/widgets/charts) by selecting a color palette, adjusting the legend, and modifying the X and Y axis labels. For more details, visit [this section](/docs/blink-platform/dashboards/building-a-dashboard/widgets/charts#customize-widget-appearance).
![]()
You can customize the layout of your Dashboard Building Interface by selecting a widget and then dragging and dropping it to your desired location.
![]()
You can also adjust the size of your widgets by selecting the bottom-left corner of the widget and zooming in to shrink it or zooming out to enlarge it.
![]()
Select the icon in the top-right corner of the custom HTML widget to view it in full screen.
![]()
![]()
***
## Dashboard Building Interface Settings
1. When you make any changes to your Dashboard Building Interface, the changes are automatically saved. You will see this in top-right corner of the Dashboard Building Interface.
![]()
2. In the top-right corner of the Dashboard Builder, click the icon to open a menu with the following options:
1. **Edit Info**: Update your dashboard’s information as needed. After making changes, click **Save Changes** to apply them automatically.
2. **Share Dashboard**: - You can share an **activated** dashboard by entering the name of the user or group you want to share the selected dashboard with.
3. **Copy Dashboard Schema**- Copies the JSON syntax of the selected Dashboard
4. **Export Dashboard**: Download a PDF version of your dashboard for sharing or record-keeping purposes.
**Note**: You can also export a dashboard via the [export dashboard workflow action](/docs/blink-platform/dashboards/dashboard-actions/export-dashboard) or through the [Self-Service Portal](/docs/blink-platform/dashboards/dashboard-actions/export-dashboard#3-through-the-self-service-portal).
5. **Copy Dashboard ID** - Copies the selected Dashboard's unique ID
6. **Delete**: Permanently removes the selected dashboard. Use with caution.
![]()
***
# Case Management Reportings
Source: https://docs.blinkops.com/docs/blink-platform/dashboards/building-a-dashboard/source-types/case-management-reporting
The Case Management Reportings is a data source that represents the [case tables](/docs/case-management/cases/cases) in case management.
MTTx (Mean Time To x) data represents the time duration between different stages in a case's process. For example, it shows the minimum time it took to change a case's status from **open** to **in progress** or the case status SLA.
| Table Field | Description |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| Case ID | The Case's ID number. |
| Case Name | The name of the Case. |
| Case Type | The type of Case. |
| Severity | The severity rank of your Case. It can be: **Low, Medium, High or Critical**. |
| Tags | Tags linked to a specific Case. |
| Vendor | The vendors used in the Case. |
| Case Manager | The user who manages the Case. |
| Collaborators | Users who collaborate on the Case. |
| Created at | Date and time the Case was created. |
| Status | The Status of the Case. |
| Status Types | The Status Type: **Not started Status**, **Active Statuses** or **Done Statuses** |
| Time from case open to chosen status | The time from when a case is in the open status and changed to different status type- duration field in `hh:mm:ss` |
| Time from Status to Status | The time duration between two selected case statuses-duration field in `hh:mm:ss` |
| Time in Status | The time in a status - duration field in `hh:mm:ss` |
| Time to close | The time span from case creation to closing a case - duration field in `hh:mm:ss` |
| Time to Assign | The time span from case creation to assigning the first case manager - duration field in `hh:mm:ss` |
**Important to Know**
**Time From Case Open to Status:**
* If a case starts in `OPEN`, moves through other active statuses, and later returns to a status it was in before, the timer for that status starts over. Because of this, the total time shown in the widget may increase each time the case re-enters the same status.
* Cases that are opened directly in an active status (for example, `IN PROGRESS`) are not counted in this widget. Only cases that begin in the `OPEN` status are included.
### Overview
* When using the MTTx Reporting case table as the widget source, users can select the time from the **Status to Status** column under ‘Field Function’ option.
* This field measures the duration between two selected case statuses in the format `hh:mm:ss`.
* This allows users to specify the **"From"** and **"To"** statuses, enabling precise tracking of transitions between specific stages in the case lifecycle.
### Use Case Example
* This bar chart shows the **sum** of the time taken for cases to transition from **OPEN** to **IN PROGRESS**, based on data from the **MTTx Reporting** case table. It aggregates the total duration cases remained in the **OPEN** status before moving to **IN PROGRESS**, resulting in **36 seconds and 342 milliseconds**, helping users track and analyze the process efficiency.
![]()
## Case Workflows
This data represent all the cases created using [Case Actions](/docs/case-management/case-management-workflow-actions/case-actions) in an automated workflow.
| Table Field | Description |
| --------------------- | ----------------------------------------------------------------------------- |
| Workflow Name | The name of the Workflow. |
| Workflow ID | The Workflow's ID number. |
| Pack Name | The name of the Workflow's Pack. |
| Workflow Run Duration | The duration time of the Workflow's execution. |
| Case ID | The Case's ID number. |
| Case Created At | Date and time the Case was created. |
| Case Name | The name of the Case. |
| Case Type | The type of Case. |
| Severity | The severity rank of your Case. It can be: **Low, Medium, High or Critical**. |
| Tags | Tags linked to a specific Case. |
| Vendor | The vendors used in the Case. |
# Data Source Types
Source: https://docs.blinkops.com/docs/blink-platform/dashboards/building-a-dashboard/source-types/source-types
Instructions about the different data source Data Source Types
The data presented in the dashboard through tables or other widgets, such as graphs or numbers, is sourced from [Tables](/docs/blink-platform/tables/tables), [Case Management Tables](/docs/case-management/manage-tables) or [Case Management Reportings](/docs/blink-platform/dashboards/building-a-dashboard/source-types/case-management-reporting). Therefore, a prerequisite for building a valuable dashboard is to create at least one Table that can be selected in the [Dashboard-Building Interface](/docs/blink-platform/dashboards/building-a-dashboard/building-a-dashboard#dashboard-building-interface).
![]()
# Charts
Source: https://docs.blinkops.com/docs/blink-platform/dashboards/building-a-dashboard/widgets/charts
Instructions on how to create and use the Chart Widget
## Adding Chart Widgets
In the *Edit Mode* tab of the Dashboards Building Interface, click the "add a widget" button.
![]()
Choose the type of chart you want to utilize. You can choose between a Pie, Donut, Bar, Line or Scatter chart.
![]()
In the top left corner, double-click on *Untitled widget* and provide a name for the selected chart widget.
![]()
Choose a data source: [Tables](/docs/blink-platform/tables/tables), [Case Management Tables](/docs/case-management/manage-tables) or [Case Management Reportings](/docs/blink-platform/dashboards/building-a-dashboard/source-types/case-management-reporting) and proceed by selecting the specific table column from the data source you would like to use.
![]()
Under the Filters section, you can use the [condition builder](/docs/workflows/building-workflows/condition-builder#condition-builder) to define one or more conditions that determine which records are included, filtering the underlying data accordingly. You can also create [nested conditions](/docs/blink-platform/condition-builder/condition-builder#the-advanced-condition-builder-and-nested-conditions) to group related conditions together and apply their own `AND` or `OR` logic, enabling more advanced and precise filtering.
![]()
## Chart Types and Configuration
### Pie Chart Data Configuration
**Note**
The data used to configure the `pie chart` will be taken from a particular table from the [tables feature](/docs/blink-platform/tables/tables) or [case management feature](/docs/case-management/case-management).
As a reminder, chart elements can expose raw data that may be sensitive, and therefore should not be used if you have concerns with viewers being able to see that information.
1. **Column**: Choose the table column you want to **group** the `pie chart` by.
* If the selected column is a time period, you will see the **Bucket by** option, allowing you to categorize the time period. This will be shown as a legend on the right side of the `pie chart`.
![]()
* If the selected column contains user-related data, the 'User Count' option becomes available. This lets you choose how to group and count the data:
* Distinct Count – Counts each user and group separately. If a record is linked to a specific user, that user’s name (or email) will appear in the legend. For example, in a pie chart, each slice represents an individual user or group
* Aggregated View– Groups records by user groups instead of individual entities. The legend will only show group names, and the count will include all records linked to the group, including those assigned to individual users in the group.
### Scenario:
A team is tracking case management tasks using a pie chart where the **"Assigned To"** column contains user-related data. In this example:
There are a total of **5** Tasks
* **Talia** is assigned **1 task**
* **John** is assigned **1 task**.
* **Noah** is assigned **2 tasks**.
* **Group-CM Collab** (which includes both John and Noah) is assigned **1 case**.
![]()
When visualizing this data, two different counting methods can be used:
#### **1. Distinct Count**
In this view, each task assigned to the users and group are counted separately:
* **Talia** is assigned **1 task**
* **John: 1 tasks**
* **Noah: 2 tasks**
* **Group-CM Collab: 1 task** (only counting tasks assigned directly to the group, without including those tasks assigned to its members).
#### **2. Aggregated View**
In this view, tasks are counted at the group level, including tasks belonging to individuals within the group:
* **Group- CM Collab** appears as one of the groups as a legend item.
* **Total tasks counted for Group- CM Collab: 4** (**1 task** assigned to John + **2 tasks** assigned to Noah + **1 task** assigned directly to Group- CM Collab).
2. **Sort By:** Choose the order you want the data sorted by:
* Segment name (ascending)
* Segment name(descending)
* Segment count(ascending)
* Segment count(descending)
![]()
3. **Limit**: Limit the number of bars shown on the chart to hide the lower count values
![]()
1. If you select **Record Count**:
* The Chart widget will show the total number of records available in the chosen source table.
**OR**
2. If you select **Field Function** (You can only add a **Field Function** if the selected column is a **numeric value**).
* **Choose a column**: `Time from Status Open to Status`, `Time in Status` or `Time to Assign`
* **Choose the sum operation that will be used to calculate the selected column values**: `Sum`, `Maximum`, `Minimum`, `Average` or `Median`.
![]()
### Donut Chart Data Configuration
**Note**
The data used to configure the `Donut Chart` will be taken from a particular table from the [tables feature](/docs/blink-platform/tables/tables) or [case management feature](/docs/case-management/case-management).
As a reminder, chart elements can expose raw data that may be sensitive, and therefore should not be used if you have concerns with viewers being able to see that information.
1. **Column**: Choose the table column you want to **group** the `donut chart` by.
* If the selected column is a time period, you will be provided with the **Bucket by** option, allowing you to group the column according the time period. This will be displayed as a legend on the right side of the `donut chart`.
![]()
* If the selected column contains user-related data (such as "Purchased By" in this example), the "User Count" option becomes available. This lets you choose how to group and count the data:
* Distinct Count – Counts each user and group separately. If a record is linked to a specific user, that user’s name (or email) will appear in the legend. For example, in a donut chart, each slice represents an individual user or group.
* Aggregated View – Groups records by user groups instead of individual entities. The legend will only show group names, and the count will include all records linked to the group, including those assigned to specific users within it.
![]()
2. **Sort By:** Choose the order you want the data sorted by:
* Segment name (ascending)
* Segment name(descending)
* Segment count(ascending)
* Segment count(descending)
![]()
3. **Limit**: Limit the number of segments shown on the donut chart to hide the lower count values.
1. If you select **Record Count**:
* The Chart widget will show the total number of records available in the chosen source table.
**OR**
2. If you select **Field Function** (You can only add a **Field Function** if the selected column is a **numeric value**).
* **Choose a column**: `Number`
* **Choose the sum operation that will be used to calculate the selected column values**: `Sum`, `Maximum`, `Minimum`, `Average` or `Median`.
![]()
### Bar Chart Data Configuration
**Note**
The data used to configure the `Bar Chart` will be taken from a particular table from the [tables feature](/docs/blink-platform/tables/tables) or [case management feature](/docs/case-management/case-management).
As a reminder, chart elements can expose raw data that may be sensitive, and therefore should not be used if you have concerns with viewers being able to see that information.
1. **Column**: Choose the table column you want displayed on the **X axis**.
* If the selected column is a **time period**, you will be provided with the **Bucket by** option, allowing you to group the column according the time period.
* If the selected column contains user-related data, the User Count option becomes available. This determines how data is grouped on the x-axis in a bar chart:
* **Distinct Count** – Each bar represents an individual user or group separately. If a record is linked to a specific user, that user’s name (or email) will appear on the x-axis. This allows you to see how many records belong to each user or group independently.
* **Aggregated View** – Groups records by user groups instead of individual entities. The x-axis will display only group names, and the count will include all records assigned to the group, including those assigned to individual users in the group.
2. **Sort By:** Choose how you want the data sorted by:
* X-axis value (ascending)
* X-axis value(descending)
* Y-axis value(ascending)
* Y-axis value(descending)
3. **Limit**: Limit the number of bars shown on the chart to hide the lower count values
![]()
1. If you select **Record Count**:
* It will display the number of records available on the selected source table on the Chart widget.
![]()
**OR**
2. If you select **Field Function** (You can only add a **Field Function** if the selected column is a **numeric value**).
* **Choose a column**: `Time from Status Open to Status`, `Time in Status` or `Time to Assign`
* **Choose the sum operation that will be used to calculate the selected column values**: `Sum`, `Maximum`, `Minimum`, `Average` or `Median`.
### Line Chart Data Configuration
**Note**
The data used to configure the `Line Chart` will be taken from a particular table from the [tables feature](/docs/blink-platform/tables/tables) or [case management feature](/docs/case-management/case-management).
As a reminder, chart elements can expose raw data that may be sensitive, and therefore should not be used if you have concerns with viewers being able to see that information.
1. **Column** Choose the table column you want displayed on the **X axis**.
* If the selected column is a time period, you will be provided with the **Bucket by** option, allowing you to group the column according the time period.
![]()
* If the selected column contains user-related data (such as "Purchased By" in this example), the User Count option becomes available. This determines how data is plotted on the x-axis in a line chart:
* **Distinct Count** – Each point on the line represents an individual user or group separately. If a record is linked to a specific user, that user’s name (or email) will appear on the `x-axis`.
* **Aggregated View** – Groups records by user groups instead of individual entities. The `x-axis` will display only group names, and the line will represent the total count of records assigned to each group, including those assigned to individual users in the group.
![]()
2. **Sort By:** Choose how you want the data sorted by:
* X-axis value (ascending)
* X-axis value(descending)
* Y-axis value(ascending)
* Y-axis value(descending)
![]()
3. **Limit**: Limit the number of bars shown on the chart to hide the lower count values
1. If you select **Record Count**:
* The Chart widget will show the total number of records available in the chosen source table.
**OR**
2. If you select **Field Function** (You can only add a **Field Function** if the selected column is a **numeric value**).
* **Choose a column**: `Number`.
* **Choose the sum operation that will be used to calculate the selected column values**: `Sum`, `Maximum`, `Minimum`, `Average` or `Median`.
![]()
### Scatter Chart Data Configuration
**Note**
The data used to configure the `Scatter Chart` will be taken from a particular table from the [tables feature](/docs/blink-platform/tables/tables) or [case management feature](/docs/case-management/case-management).
As a reminder, chart elements can expose raw data that may be sensitive, and therefore should not be used if you have concerns with viewers being able to see that information.
1. **Column**: Choose the table column you want displayed on the **X axis**. If the selected column is a time period, you will be provided with the **Bucket by** option, allowing you to group the column according the time period.
![]()
1. If you select **Record Count**:
* The Chart widget will show the total number of records available in the chosen source table.
**OR**
2. If you select **Field Function** (You can only add a **Field Function** if the selected column is a **numeric value**).
* **Choose a column**: `Number`
* **Choose the sum operation that will be used to calculate the selected column values**: `Sum`, `Maximum`, `Minimum`, `Average` or `Median`.
![]()
## Customize Widget Appearance
In the 'Appearance Tab', you can customize the appearance of a [chart widget](/docs/blink-platform/dashboards/building-a-dashboard/widgets/charts) by selecting a color palette and customizing the legend, as well as the X and Y axis labels.
Widgets that display case severity data will use the **default system color palette** by default. However, you can customize the color palette to better suit your preferences.
![]()
1. **For the [pie chart](/docs/blink-platform/dashboards/building-a-dashboard/widgets/charts#chart-types-and-configuration) and [donut chart](/docs/blink-platform/dashboards/building-a-dashboard/widgets/charts#chart-types-and-configuration) widgets:**
* You can position the legend at the top, bottom, left, or right of the chart, or hide it entirely if you don't want it to be displayed.
* You can also enable a toggle option to display a custom title.
**For Example**
![]()
2. **For the [bar chart](/docs/blink-platform/dashboards/building-a-dashboard/widgets/charts#chart-types-and-configuration), [line chart](/docs/blink-platform/dashboards/building-a-dashboard/widgets/charts#chart-types-and-configuration), and [scatter chart](/docs/blink-platform/dashboards/building-a-dashboard/widgets/charts#chart-types-and-configuration) widgets:**
* To customize the selected chart, choose a single color from the palette by clicking the colored square next to the "Color" label. Then choose a single color to apply to the chart.
* You can toggle options to display labels for the X and Y axes.
**For Example**
![]()
3. Any other changes made in the **Data** tab, will be automatically applied to the widget in real time.
## Deleting a Chart Widget
1. In the left-hand sidebar, click the icon in the top-right corner and then select the delete button.
2. The Chart Widget will be removed from your Dashboard Building Interface.
![]()
# Filters
Source: https://docs.blinkops.com/docs/blink-platform/dashboards/building-a-dashboard/widgets/filter
Instructions on how to create and use the Filter Widget
Dashboards often present a broad overview of data, such as a bar graph displaying all cases grouped by their names. However, there are situations where a more targeted view is necessary. For example, you might want to focus on cases managed by a specific individual or filter for cases only with a "medium" severity level. **The Filter Widget** makes this possible by allowing end-users to apply additional filters. This tool helps refine the displayed data and customize it to show exactly what is most relevant to your needs.
## Important to Note:
Before using the Filter Widget, keep these points in mind:
**Note**
* The filter widget can only be linked to other widgets that have the same [data source](/docs/blink-platform/dashboards/building-a-dashboard/source-types/source-types).
* The filter widget can only be applied to a **single** widget where filtering has already been applied.
***
## Adding a Filter Widget
In the *Edit Mode* tab of the Dashboards Building Interface, click the "add a widget" button. Choose the **Filter** option from the widget list.
![]()
In the sidebar in the top left corner, double-click on *Untitled widget* and provide a name for the selected widget.
![]()
Choose a data source: [Tables](/docs/blink-platform/tables/tables), [Case Management Tables](/docs/case-management/manage-tables) or [Case Management Reportings](/docs/blink-platform/dashboards/building-a-dashboard/source-types/case-management-reporting) and proceed by selecting the specific table column from the data source you would like to use.
![]()
Under the *Filters* section, click on "add condition(s)" to add conditional statements by using the [condition builder](/docs/blink-platform/condition-builder/condition-builder).
![]()
***
#### Nested Conditions
You can also create nested conditions, which are conditions grouped within other conditions. Nested conditions allow you to define more complex logic, applying specific operators (`AND`/`OR`) to a subset of conditions independently from the main group.
![]()
Lastly, connect your Filter Widget to the widget you want to filter. In the following example, the filter widget is connected to a bar graph displaying case data. The filter is set to show only cases with a "medium" severity level, demonstrating how the widget updates to reflect the applied filter.
![]()
***
## Editing the Filter Widget
If you want to remove a conditional statement and stop the filter from being applied to the linked widget, click the Reset button. For any other changes, you can edit directly in the left-hand sidebar. Simply locate the relevant section to adjust or update the information as needed. Changes will be applied automatically
![]()
***
## Deleting a Filter Widget
In the left-hand sidebar, click the icon in the top-right corner and then select the delete button.
The Filter widget will be removed from your Dashboard Building Interface.
![]()
***
# Flow Chart
Source: https://docs.blinkops.com/docs/blink-platform/dashboards/building-a-dashboard/widgets/flow-chart
Instructions on how to create and use the Flow Chart Widget
## Adding a Flow Chart Widget
In the *Edit Mode* tab of the Dashboards Building Interface, click the "add a widget" button and select the 'Flow Chart' widget.
![]()
In the sidebar in the top left corner, double-click on *Untitled widget* and provide a name for the selected widget.
![]()
Choose a data source: [Tables](/docs/blink-platform/tables/tables), [Case Management Tables](/docs/case-management/manage-tables) or [Case Management Reportings](/docs/blink-platform/dashboards/building-a-dashboard/source-types/case-management-reporting) and proceed by selecting the specific table column from the data source you would like to use.
![]()
Choose a data source: [Tables](/docs/blink-platform/tables/tables), [Case Management Tables](/docs/case-management/manage-tables) or [Case Management Reportings](/docs/blink-platform/dashboards/building-a-dashboard/source-types/case-management-reporting) and proceed by selecting the specific table column from the data source you would like to use.
![]()
When this option is selected, the flow chart will display any records that are linked between the chosen input [data source](/docs/blink-platform/dashboards/building-a-dashboard/source-types/source-types) and output [data source](/docs/blink-platform/dashboards/building-a-dashboard/source-types/source-types).
This allows you to visualize relationships between related records and better understand how data flows from the source to the destination.
![]()
**Please be advised**:
* This setting is only supported for [Tables](/docs/blink-platform/tables/tables) and [Case Management Tables](/docs/case-management/manage-tables) data sources. It cannot be used with the [Case Management Reportings](/docs/blink-platform/dashboards/building-a-dashboard/source-types/case-management-reporting) data source.
* This setting can only be used if the input and output data sources are of the same type. It cannot be applied when the input and output use different data sources.
Under the Filters section, you can use the [condition builder](/docs/workflows/building-workflows/condition-builder#condition-builder) to define one or more conditions that determine which records are included, filtering the underlying data accordingly. You can also create [nested conditions](/docs/blink-platform/condition-builder/condition-builder#the-advanced-condition-builder-and-nested-conditions) to group related conditions together and apply their own `AND` or `OR` logic, enabling more advanced and precise filtering.
![]()
Under the *Numbers* section:
1. If you select **Record Count**: It will display the number of records available on the selected source table on the Flow Chart widget.
![]()
**OR**
2. If you select **Field Function** (You can only add a **Field Function** if the selected column is a **numeric value**).
1. **Choose a column**: `Time from Case Open to Status`,`Time from Status to Status`, `Time in Status`, `Time to Close`, `Time to Assign`
2. **Choose the sum operation that will be used to calculate the selected column values**: `Sum`, `Maximum`, `Minimum`, `Average` or `Median`.
![]()
***
## Customize the Flow Chart Widget
In the **Appearance** tab, you can fully customize the **Flow Chart Widget** to match your dashboard’s style and needs. You have control over the color theme, central graphic, and labels for inputs and outputs:
1. **Select a color theme** – Pick a color palette that fits your dashboard’s look.
2. **Choose a central graphic** – Select the image or icon to display at the center of the widget.
3. **Set labels** – Define labels for the inputs and outputs to clarify the flow of information.
![]()
***
## Editing a Flow Chart Widget
In the **Data** tab, any changes you make will be automatically applied to the Flow Chart widget in real time.
***
## Deleting a Flow Chart Widget
In the left-hand sidebar, click the icon in the top-right corner and then select the delete button.
The Flow Chart widget will be removed from your Dashboard Building Interface.
![]()
# Custom HTML
Source: https://docs.blinkops.com/docs/blink-platform/dashboards/building-a-dashboard/widgets/html
Instructions on how to create and use the Custom HTML Widget
## Adding a Custom HTML Widget
In the *Edit Mode* tab of the Dashboards Building Interface, click the "add a widget" button.
![]()
Choose the **Custom HTML** option from the widget list.
![]()
In the sidebar in the top left corner, double-click on *Untitled widget* and provide a name for the selected widget.
![]()
Enter your HTML content (including `