1: Introduction
      Back to home
      1. Home
      2. 1: Introduction

      Key Terminology

      Understand the key terms used throughout the Rayven platform to help you navigate and configure applications confidently.

      Overview

      Rayven uses a specific set of terminology to describe the components and users involved in building and operating applications on its platform. These terms are foundational and are used consistently throughout the Rayven Workspace and documentation. Understanding these will help you configure applications more effectively and communicate clearly with team members and support.

      Key Terminology in Rayven

      Below is a list of important terms you’ll encounter when using the Rayven platform:

      Rayven Account

      A Rayven Account belongs to a business, organisation, or individual. It serves as the container for all applications and workspace users.

      Application (or Rayven Application)

      A configured solution within a Rayven Account. Applications can be standalone or integrated, and include data tables, workflows, interfaces, and users.

      Workspace

      The development environment within Rayven. This is where Workspace Users build and manage applications, including configuring tables, workflows, interfaces, and user groups. Accessible at: https://workspace.rayven.io

      Workspace User

      A user who can log into the Rayven Workspace. These users have access to configure and manage applications. Workspace Users can have roles with varying permission levels (e.g., User, Admin, SuperAdmin).

      Application User (or just "User")

      A user who accesses the front end (App Interface) of a Rayven Application. Application Users do not have access to the Workspace (unless they are also configured as a Workspace User) and are typically the end-users of the application.

      App Interfaces

      The front-end screens that Application Users interact with. Interfaces display data and functionality via widgets. These are configured in the Workspace and accessed by users via https://app.rayven.io.

      Interface Types

      • Top-level Interface: Visible in the app’s main menu in the App Interfaces.

      • Drilldown Interface: Only accessible via interaction with a widget on a Top-level Interface.

      Workflow Builder

      The tool used to create logic, automate processes, and manage data flows within an application. Workflows are composed of nodes and can be configured with both visual logic and JavaScript.

      Workflow Node

      A building block in a workflow that performs a specific function—such as ingesting data, transforming it, displaying it, or sending it elsewhere.

      Frontend Node

      A type of workflow node that produces a widget for use in App Interfaces. These may be pre-built (e.g., charts, gauges) or custom (e.g., UI Code nodes).

      Widget

      A visual component on an App Interface that displays data or functionality. Widgets are generated by Frontend Nodes and can be resized or repositioned on the interface.

      Tables

      Structured data stores used within applications. There are two types:

      • Primary Tables: Store core records with unique identifiers (UIDs).

      • Secondary Tables: Extend Primary Tables with related or supporting data.

      UID (Unique Identifier)

      A value stored in the Primary Table that uniquely identifies each record. All workflow and unstructured data is anchored to UIDs.

      Labels

      Structured attributes applied to Primary Table rows to enable grouping and filtering. Label types include:

      • Default (No Labelling): Stores a value but does not support grouping.

      • Single Label: Enables grouping by a single value.

      • Multi-Label: Supports combining multiple labels for multi-level filtering.

      Summary

      Rayven uses a consistent and specific set of terms to describe the components of its platform. Understanding the differences between Workspace Users and Application Users, knowing what constitutes a Workflow or a Frontend Node, and recognising the role of Tables, Labels, and Widgets is essential for effectively configuring and using Rayven Applications.

      FAQs

      What is the difference between a Workspace User and an Application User?
      A Workspace User can access the backend tools to build and manage applications, while an Application User can only access the App Interfaces to interact with the application.

      Are ‘App’, ‘Application’, and ‘Solution’ interchangeable terms in Rayven?
      Yes. In Rayven documentation, these terms often refer to the same concept: a configured set of components (tables, workflows, interfaces, users) built using the platform.

      Do I need a Primary Table in every application?
      Yes. Every Rayven application must have a Primary Table with at least one row. It acts as the foundation for structured and unstructured data.

      Can a user belong to multiple applications?
      Yes. An Application User can be granted access to multiple applications within the same Rayven Account. If so, a dropdown menu will allow them to switch between apps when logged in.

      What’s the difference between a Frontend Node and a Widget?
      A Frontend Node is configured in a workflow and becomes a Widget when it’s selected for display on an Interface. The Widget is what the user sees and interacts with on the App Interface.