Key Concepts

Build Processes, Not Overhead.
Portal

This section introduces key concepts and terms used throughout the admin portal. Understanding these definitions will help you navigate and manage the platform more effectively.

  • 01. Account

    An account represents a user's profile in the system. Users create an account during the sign-up process by providing an email address, which serves as their unique identifier. Each account holds personal settings, preferences, and team memberships.

  • 02. Team

    A team is a group of users working together under a shared workspace. When a user registers on the platform, a dedicated team is automatically created, and the user becomes its owner. Team owners can invite other users, manage the team name and time zone, assign subscriptions, and control access. While a user can belong to multiple teams, each team has only one designated owner.

  • 03. Project

    Projects are organizational containers within a team. Each team can create and manage an unlimited number of projects. A project brings together everything needed for automation — including processes, data schemas, a vault of keys, and templates — under a single scope.

  • 04. Data Schema

    A data schema defines the structure of data that your processes will work with. It consists of a set of named and typed fields (such as Text, Integer, Real number, or Boolean). Each schema also has a name and a designated key field that must hold unique values. Data schemas are essential for storing persistent data and sharing information between different processes.

  • 05. Vault

    The vault is a secure store of key/value pairs, managed through AWS Systems Manager Parameter Store. Only team owners can create and edit vault entries, while other team members can use them in processes as input parameters — without being able to view the actual values. Vaults are commonly used to manage API keys, credentials, and other sensitive configuration values.

  • 06. Templates

    Templates allow you to generate dynamic content — such as emails, notifications, or prompts — based on data from the Execution State. Defined at the project level, templates are logic-less and tag-driven, using JSON Path mappings to inject values. They can be shared across multiple processes within the same project.

  • 07. Process

    A process is a core unit of automation. It includes a name, an optional description, a BPMN-based flow definition, an initial state, and a list of deployments. Processes define what needs to happen, step by step, using BPMN diagrams and configured tasks.

  • 08. Deployment

    A deployment is an executable version of a process. When you create a deployment, the platform validates the process flow and prepares it for execution. The process's initial state is copied into the deployment (with optional modifications) and used to establish the starting point for runtime execution.

  • 09. Execution State

    The execution state is a live dictionary of key/value pairs that represents the current context of a running process instance. It starts from the initial state defined during deployment and evolves as service tasks complete and pass back new data. Gateways can inspect the execution state to decide which path the process should follow.

  • 10. Activities

    Activities are log entries that record the lifecycle of a process instance — for example, when a process starts, when a service task begins, or when it completes. These records provide visibility into what the system is doing and serve as a powerful tool for monitoring and debugging process execution.

  • 11. Favourites

    Favourites are personal shortcuts. They allow you to quickly access frequently used resources across the platform — such as specific deployments, processes, or projects — by bookmarking them in your dashboard.