7. Interfaces, Widgets & Dashboards
      Back to home
      1. Home
      2. 7. Interfaces, Widgets & Dashboards

      Overview of Rayven Interfaces

      Learn how Rayven Interfaces work, how widgets are displayed, and how to configure and manage pages your users interact with.

      Overview

      Interfaces in Rayven are the front-end screens of your application—what your Application Users see when they log in. These interfaces display data and functionality via widgets, which are visual representations of Frontend nodes configured in your workflows.

      Interfaces are created and managed from the Workspace, but the layout and interaction are controlled from the application itself. This guide walks you through the types of interfaces, how they are structured, how widgets are added and displayed, and the basics of user group access.

      What Are Rayven Interfaces?

      Rayven Interfaces are the pages that make up the front-end experience of your application. Each Interface corresponds to a distinct view or screen that users access through the App Interface (usually at https://app.rayven.io or your white-labelled domain). Interfaces can display widgets, forms, dashboards, charts, custom UI elements, and more.

      Rayven separates the building of an interface (via Frontend workflow nodes) from the layout and assignment of interfaces (done in the Interfaces section of the Workspace and the App Interface).

      Types of Interfaces

      There are two types of interfaces you can create in Rayven:

      • Standard Interface
        Displays any combination of Frontend node widgets. This is the default and most commonly used interface type, suitable for the vast majority of applications. It’s ideal for building user-facing application pages—such as interactive screens, forms, user views, and dashboards.

        Use a Standard Interface unless you have a specific need for historical data filtering. It’s the right choice for most use cases.

      • Analytics Interface
        Adds a built-in date range selector for time-based filtering. Use this only when your users need to explore and filter historical data—such as trend analysis or reporting views.

      Top-Level vs Drilldown Interfaces

      • Top-Level Interface
        Appears in the left-hand menu of the App Interface. These are the primary navigation points in the application.

      • Drilldown Interface
        These are not shown in the menu and are only accessed via interaction with widgets (e.g. clicking a bar in a chart). Useful for deeper insights or record-level detail pages.

      An application can include multiple top-level interfaces, each with optional drilldowns, or use a single top-level interface with custom navigation logic built using UI Code nodes.

      How Widgets Appear on Interfaces

      Widgets are visual components that appear on interfaces. To make a widget appear:

      1. Add a Frontend node to a workflow.

      2. Go to the Interfaces section in the Workspace.

      3. Select the Interface and choose which Frontend nodes (widgets) to display.

      4. Ensure the Interface is assigned to the correct User Group so users can see it.

      Important Notes:

      • Widgets are always tied to a Frontend node in a workflow.

      • Widgets are not auto-populated with historical data—they must receive data after being added to the workflow.

      Widget Display Configuration (UID vs Label)

      Each Frontend node includes a setting called “Number of Widgets to Display”, which controls how many widgets are rendered based on your data model.

      Options include:

      • One Widget per UID
        Displays one widget for each record in your Primary Table. E.g., one per customer or device.

      • One Widget per Label Value
        Displays one widget per unique value in a selected label column. E.g., one per department or region.

      • One Widget per Label (default)
        Displays a single widget that aggregates or summarises all data grouped by the label.

      If aggregations are required, the node will prompt you to choose a calculation method (e.g., sum, average).

      Using Prebuilt vs Custom Widgets

      Rayven offers two main approaches to building interface components:

      • Prebuilt Widgets
        Provided via standard Frontend nodes (charts, tables, gauges, maps, etc.). These have configurable settings but fixed functionality.

      • Custom Widgets (UI Code Node)
        Use HTML, CSS, and JavaScript to create fully custom widgets. These can:

        • Read/write from/to Tables using getDataFromTable()

        • Receive and send workflow payloads

        • Be used as full-page or partial interface components

      Managing Interface Layout

      While the list of interfaces and widget selections are configured in the Workspace, the actual positioning, sizing, and layout of widgets are managed within the App Interface.

      Only users with one of the following roles can edit the layout, and only if they have the “Edit Interfaces” option enabled:

      • Super Admin

      • Admin

      • Customer Admin

      • Editor


      Assigning Interfaces to User Groups

      Each User Group defines:

      • What interfaces are visible to its members

      • Which data (via label filters) populates the widgets on those interfaces

      You can assign different interfaces to different groups to tailor the experience per user type (e.g. Admins vs Regional Managers).

      Summary

      Rayven Interfaces let you build and deliver the front-end experience for your application users. They are composed of widgets driven by Frontend nodes in your workflows. You can mix and match prebuilt or custom widgets and control how many widgets appear based on your data structure and labels. User Groups determine access to each Interface and which data gets shown, giving you precise control over each user's view.

      FAQs

      How do I make a widget appear on a new Interface?
      Add a Frontend node to a workflow, then go to the Interfaces section in the Workspace and select that node for your Interface.

      What’s the difference between a Standard and Analytics Interface?
      An Analytics Interface includes a date range filter and is only compatible with widgets that support time filtering.

      Can I use both prebuilt and custom widgets on the same Interface?
      Yes. You can mix prebuilt Frontend widgets and custom UI Code widgets on any interface.

      How do I control how many widgets appear per Frontend node?
      Use the “Number of Widgets to Display” setting inside the Frontend node. Choose between one widget per UID, per Label Value, or per Label.

      Who can arrange the layout of an Interface?
      Only Application Users with the “Edit Interfaces” permission enabled can modify widget layout. This includes users with the roles: Super Admin, Admin, Customer Admin, or Editor. Without this permission, users can view interfaces but cannot move, resize, or configure widgets.

      Do widgets update automatically?
      Yes, most prebuilt widgets support auto-refresh settings. Custom widgets (via UI Code node) can be configured to refresh on demand or via workflow triggers.