Account (Tenant): Each company using Blink has a separate account, completely isolated from all other accounts.

Action: An Action is a built-in feature on the Blink platform. It is the functional element of a Step. Actions enable you to perform operations on remote systems. Typical Actions on AWS include Create a user and Delete a user, and on Github Create pull requests, and Create user repo.

Automation: An Automation constitutes of a series of actions that serve to solve a specific use case. It is created using Steps and Sections.

Connection: A connection can be created with a vast number of cloud infrastructures, monitoring and security tools. A connection enables Actions to run on remote systems that require authorization. It is created using a token from the target system or via the personal account of the user on that system.

Groups: 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, to grant access to all group members.

User: Users must be added to the account before they can use the Blink platform. Types of users:

Admin: Can add, invite and delete users. Admin user also has owner permissions in all the workspaces of the account.

Member: A member of a particular account.

Runner: A runner executes the actions defined in the Automation. By default all actions are executed from the Blink cloud, however, the user can choose to deploy a runner that will execute all of the actions from your managed cloud infrastructure.

Section: A Section is a series of Steps within an Automation. The purpose of a Section is to create order by grouping Steps together into meaningful groups.

Step: Steps are the building blocks of a Blink Automation. Each Step has a single goal and Steps are arranged in a logical order to complete a workflow. The user assigns input parameters and the Step executes an Action and displays its output.

Trigger: Steps and Automations run when they are prompted by one of the following triggers:

Event-based: An Automation that is triggered by an event that occurs on an external service provider.

Scheduled: An Automation that is triggered at a pre-set time and can be repeated at any frequency.

On-demand: An Automation that is triggered when selected from the self-service catalog.

Workspace: A workspace groups all of your Automations and resources such as connections, runners and Actions. Only a user associated with a certain workspace has access to the Automations and the resources. All the Automations of a Workspace appear on the Automations Pack page.