Understanding User Groups, Labels, Filters, and Data Access in Rayven.io

In Rayven.io, the combination of User Groups, Labels, Filters, and Workflow Data provides a powerful way to control data visibility.

Introduction

Rayven.io provides a highly flexible system for managing user access to data through the use of User Groups, Labels, and Filters. This system ensures that different users can see only the data and dashboards relevant to their roles, allowing organizations to protect sensitive information while providing the right insights to the right people.

In this article, we will explain how User Groups relate to data access, how Labels and Filters organize data within workflows, and how these concepts interact to ensure tailored visibility for each user.

Users and User Groups

In Rayven.io, each user can be assigned to one or more User Groups. These user groups act as containers that define what data and dashboards each user can access. This system ensures that users only see the information necessary for their role.

Example:

• An electrician might belong to a user group that grants them access to energy data, but restricts their access to financial data. On the other hand, a finance manager might be part of a different user group that provides access to financial dashboards but limits access to technical data.

Each User Group can be configured to provide access to:

• Specific dashboards or interfaces.
• Defined data (widgets) from the workflow.
• Granular data access permissions, based on labels and filters.

Labels and Filters

In Rayven.io, Labels and Filters are powerful tools that allow administrators to control what data is available to different users. These are often derived from attributes in the Primary Data Table (which resides in the MySQL database) and help categorize and group data from the workflow.

Labels:

Labels are attributes associated with data points in the Primary Data Table. For example, a label could be:

• Building Name (e.g., "Sydney HQ")
• Device Type (e.g., "Energy Meter")
• Department (e.g., "Electrical" or "Finance")

Filters:

Filters allow you to refine the view of data based on these labels. You can create filters that combine multiple labels to display highly specific datasets to different users.

Example:

• A Device Filter might combine the labels City: Sydney and Department: Electrical, ensuring that users in the "Sydney Electricians" user group only see energy data from Sydney-based devices.

Data from the Workflow and Node Access

Rayven.io workflows process data from various sources, such as IoT devices, systems, or APIs. As data flows through workflows, different nodes represent stages where data is processed, transformed, or visualized.

Data Access in Workflows:

• Each node in the workflow can generate widgets for dashboards (e.g., tables, charts, maps) that display data.
• The system allows you to define which widgets (or nodes) users in a specific user group have access to.

For example:

• The electrician user group may have access to energy consumption widgets (from specific workflow nodes), but not to financial report widgets (which are restricted to management user groups).

Relationship Between User Groups, Labels, Filters, and Data Access

Here’s how these concepts interrelate:

1. User Group Assignment:
   • Users are placed into groups based on their roles. A user can belong to one or more groups, allowing for flexibility in data visibility.
2. Label-Based Filtering:
   • Data in the Primary Data Table is labeled (e.g., Building Name, Department, Device Type). These labels are used to filter and group the data in the workflow.
3. Workflow and Node Access:
   • Data flowing through the workflow is assigned to nodes, which are connected to widgets on dashboards. User groups are given access only to specific widgets or nodes, ensuring that they can interact with relevant data.
4. Data and Interface Visibility:
   • By configuring user groups, you can ensure that different roles have access to different dashboards and data. For instance, an electrician will see energy-related data and widgets, while a finance manager might only have access to financial reports.

Example Use Case: Smart Building Energy Monitoring

Scenario: A company wants to monitor energy usage in various buildings and give specific departments access to relevant data while restricting access to other sensitive data.

Steps:

1. User Groups:

   • Create an Electricians user group and a Finance Managers user group.

2. Labels:

   • Label the data in the Primary Data Table by department and building name (e.g., Building: Sydney HQ, Department: Electrical).

3. Filters:

   • Create a Device Filter for the electricians: Building: Sydney HQ / Department: Electrical.
   • The Finance Managers user group would use a filter like Building: Sydney HQ / Department: Finance.

4. Workflow Data Access:

   • In the workflow, create nodes for processing energy consumption data and financial data.
   • Assign the energy consumption widgets to the Electricians user group and restrict access to the financial widgets.

5. Dashboard Access:

   • The electricians will only see energy consumption dashboards and widgets based on their filters and labels.
   • The finance managers will only see financial data widgets, ensuring that sensitive data is properly restricted.

Conclusion

In Rayven.io, the combination of User Groups, Labels, Filters, and Workflow Data provides a powerful way to control data visibility. By assigning users to specific groups, defining access with filters, and tailoring data visibility through workflow nodes, you can ensure that each user sees only the data relevant to their role. This approach ensures security, clarity, and customization across your organization’s data solutions.

This article explains how users, user groups, labels, filters, and workflow data interact in Rayven.io. For further questions or assistance, feel free to contact our support team!