Labels, combined with filters and user groups, provide tremendous flexibility and control, allowing you to customize how data is presented, processed, and accessed based on specific user roles or organizational needs.
In Rayven.io, Labels are a foundational feature that enhance how data is categorized, grouped, filtered, and accessed. When applied within tables, labels enable more organized, scalable, and user-specific interactions with structured data.
This article explains what labels are, how they work in the context of Rayven tables, and how they can be used to control workflows, dashboards, and user visibility.
What Are Labels?
Labels are structured attributes used to tag rows in a table with contextual information such as:
-
Location
-
Department
-
Device Type
-
Asset Group
These labels are especially useful in primary data tables, where they serve as filters, grouping keys, or access controls across workflows, dashboards, and user interfaces.
By labeling records in a table, you enable:
-
Consistent filtering
-
Custom views for user groups
-
Grouping and aggregation in dashboards
-
Controlled processing in workflows
How Labels Work in Tables
When defining a table schema in Rayven, you can include one or more label fields as columns. These fields typically use string or multi-choice data types and represent key attributes relevant to your solution.
Examples of Label Fields in Tables:
-
Building_Name -
Device_Type -
Department -
Region
Each row in the table is tagged with values in these label fields. This labeling structure enables precise filtering and grouping throughout the Rayven platform.
Using Labels for Grouping and Filtering Table Data
Data Grouping
Labels allow records in a table to be grouped in meaningful ways.
Example:
-
Group energy usage records by
Building_Nameto show per-building metrics. -
Group device maintenance records by
Departmentto analyze operational trends.
Grouping by labels is especially useful in dashboards and in the Group By nodes within workflows.
Data Filtering
Labels also enable dynamic filtering, letting you restrict table views or data flows to specific subsets.
Example:
-
Filter a primary table to only show records labeled as
Device_Type = Energy Meter. -
Use a dashboard filter to only show
Department = Electricalfor certain users.
Filtering by labels ensures that users only interact with the most relevant records.
Labels in Workflows
Labels can be referenced directly within workflows to manage and control data operations.
Label-Based Filtering in Workflows
-
Use conditions to process only rows with specific label values (e.g.,
Building_Name = Sydney HQ). -
Trigger actions based on label combinations (e.g.,
Department = ElectricalandDevice_Type = HVAC Sensor).
Label-Based Grouping in Workflows
-
Use group nodes to aggregate or summarize data based on a label field (e.g., total energy usage per building).
This label logic works best when labels are defined in the table schema and consistently populated.
Example Use Case: Building Energy Management
Scenario:
A company wants to monitor energy usage across multiple buildings and control access by department.
Labels Used:
-
Building_Name: Sydney HQ, New York Office -
Device_Type: Energy Meter, HVAC Sensor -
Department: Electrical, Finance
Table Setup:
-
The primary data table includes columns for
Device_ID,Energy_Usage,Building_Name,Device_Type, andDepartment.
Workflow Usage:
-
The workflow reads from the table and groups data by
Building_Nameto calculate building-level usage. -
A filter node processes only
Device_Type = Energy Meter. -
A second filter ensures
Department = Electricalbefore proceeding.
Dashboard Usage:
-
Users in the Finance team see only records labeled as
Department = Finance. -
Dashboards are filtered dynamically based on the user’s role and the labels associated with the records.
Labels and User Groups
Rayven.io allows administrators to associate user groups with specific label values. This enhances access control by aligning user visibility with relevant data.
Examples:
-
Electricians group sees only
Device_Type = Energy MeterandDepartment = Electrical -
Finance group sees only data labeled with
Department = Finance
This creates a tailored experience while enforcing data governance and security policies.
Summary
| Feature | Description |
|---|---|
| Label Fields | Columns in tables that categorize data by key attributes |
| Grouping | Use labels to group rows by shared characteristics |
| Filtering | Narrow down data based on label values |
| Workflows | Use label logic to route, filter, and group data dynamically |
| User Groups | Control user access based on label alignment |
Q&A
Q: What is a label in the context of Rayven tables?
A: A label is a field or column in a table used to categorize or tag data, enabling grouping, filtering, and access control across the platform.
Q: How do I add labels to a table?
A: Add label fields (e.g., Department, Region, Device_Type) as columns when defining your table schema. Then populate those fields for each record either manually, via import, or through workflows.
Q: Can I use multiple labels on the same table?
A: Yes. You can define multiple label fields in a table and apply different combinations to each record for advanced filtering and grouping.
Q: How do labels affect user access?
A: Labels can be linked to user groups. This means users only see records in a table that match the label values allowed for their group.
Q: Can I filter workflow data based on table labels?
A: Yes. Workflow nodes support filtering conditions based on label field values in the table, allowing precise control over what data is processed.
Q: What’s the difference between a label and a normal field?
A: Labels are normal fields used strategically for categorization. Their power comes from how they’re used in filtering, grouping, and access control—not from a special field type.