A Practical Guide to Controlling Data Visibility and Permissions Across Your Organization
Overview
Rayven provides a modular and secure system for building user interfaces, visualizing workflow data, and controlling access through user groups and label-based filtering. This article outlines the key components and steps required to configure your environment effectively.
Key Components
Interfaces
-
Comprised of visual widgets.
-
Serve as the front-end for workflows, dashboards, or full applications.
-
Can be customized based on roles, departments, or data scope.
Widgets
Widgets are modular UI components—such as tables, charts, forms, or custom HTML blocks—that make up the interface.
They are configurable to display data from:
-
Primary and Secondary Tables within Rayven
-
Workflow outputs and variables
-
Live data sourced via workflows from:
-
Third-party systems (e.g., CRMs, ERPs, cloud platforms)
-
Machines, sensors, or industrial devices (via protocol connectors like MQTT, Modbus, OPC UA)
-
External APIs (via HTTP/API nodes)
-
This makes widgets powerful endpoints for presenting enriched, aggregated, or real-time data—regardless of where it originates.
User Groups
-
Control which users can access specific interfaces.
-
Enforce data visibility through label-based filtering.
Labels and Filters
-
Labels: Categorize records (e.g.,
Building = 1,Region = North). -
Filters: Control which labeled data each user group can access.
-
Enable granular visibility—ensuring users only see relevant data.
Managing Interfaces and Access
1. Create or Edit an Interface
-
Go to Interface Management.
-
Click “New Interface” or select an existing one to modify.
-
Assign widgets (tables, charts, forms, etc.).
-
Save to finalize your layout.
2. Configure Widgets in Workflow
Widgets are added and linked to data within the workflow:
-
Add or edit widget nodes in your workflow.
-
Specify:
-
Data source (primary/secondary table, workflow output)
-
Display settings (columns, formats)
-
Filters based on labels
-
-
Save the workflow to apply the widget configuration to the interface.
💡 Tip: Bind widgets to live workflow data for real-time updates.
3. Set Up User Groups and Permissions
-
Navigate to the User Groups section.
-
Create or edit a user group.
-
Assign:
-
Interfaces that the group can access
-
Label-based data filters (e.g., show only
Building = 1)
-
-
Save changes to enforce data visibility rules.
4. Assign Users to Groups
-
Go to the Users section.
-
Add or edit a user.
-
Select one or more user groups based on their role.
-
Users inherit access and filter rules from their group(s).
Example Scenario
| User Group | Interface | Data Access (Label-Based) |
|---|---|---|
| Operations | Operations Dashboard | Only records labeled Building = 1 |
| Maintenance | Maintenance Interface | Only records labeled Building = 2 |
Result: Each group sees only the data, widgets, and interfaces relevant to their role and assigned facility.
Benefits
-
Granular Control: Deliver precise data visibility per user group.
-
Enhanced Security: Restrict access to sensitive workflows or dashboards.
-
Streamlined UX: Remove unnecessary elements and noise for each user.
-
Scalability: Expand effortlessly to new buildings, departments, or applications.
Best Practices
-
Plan Labels and Filters Early: Design a consistent labeling system (e.g., by location, department, customer).
-
Review Permissions Regularly: Align access settings with organizational changes or role updates.
-
Document Everything: Maintain internal documentation for:
-
Interface configurations
-
User group mappings
-
Label logic
-
Q&A
Q: Can one user belong to multiple groups?
A: Yes. A user can inherit access from multiple groups. Data access will combine based on group permissions and filters.
Q: Can I change label filters without editing the interface?
A: Yes. Label filters are managed through user group settings, independent of the interface layout.
Q: How do I preview the user experience?
A: Assign yourself to the group and click “App Interface Login” to view the live, filtered interface.
Q: Can I hide specific widgets from certain users?
A: Widgets are filtered via label logic. For more complex UI control, create separate interfaces per group and assign accordingly.
Q: What happens if a user doesn't match any label filters?
A: The interface will load, but no data will be shown in widgets unless labels match. Use fallback logic where appropriate.
Q: Can multiple interfaces use the same widgets?
A: Yes. Widgets are configured within workflows and can be linked to multiple interfaces. This allows you to reuse logic while tailoring layout and visibility per interface.
Q: Can interfaces display real-time data from third-party systems?
A: Absolutely. As long as the data flows through a Rayven workflow—whether from APIs, machines, or cloud platforms—it can be visualized via widgets in the interface.
Q: What’s the difference between primary and secondary tables in interfaces?
A: Primary tables are typically used for transactional or live data (e.g., events, telemetry), while secondary tables are used for static or reference data (e.g., configurations). Interfaces can bind to both depending on the context.
Q: How do I prevent users from seeing certain widgets or data?
A: Use label filters in the widget configuration and user group filters to restrict data visibility. For full widget-level control, design separate interfaces for different user groups.
Q: Can I preview an interface from a specific user’s perspective?
A: Yes. Temporarily assign yourself to that user’s group, then click App Interface Login to see exactly what they will see.
Q: Are label filters dynamic?
A: Yes. Label filtering is enforced at runtime, meaning users only see the data they’re authorized to access—even if the same widget is used across interfaces.
Q: Can one widget show different data for different users?
A: Yes. As long as label filters are applied correctly, the same widget will show context-specific data based on the user’s group access.
Q: Do I need to republish an interface if I change the widget configuration in the workflow?
A: No. Once published, the interface dynamically reflects widget changes from the linked workflow. However, major layout or navigation changes require republishing.
Q: Can I embed an interface into an external website or portal?
A: Yes. Interfaces can be embedded using secure iframe-based links or shared through controlled access portals.
Q: What happens if a user has access to an interface but not to any data within it?
A: The interface will load, but the widgets will appear empty or filtered out, depending on how label-based access is configured. This ensures secure but consistent UX.
By following these steps and best practices, you can configure a secure, scalable, and role-aware environment in Rayven—ensuring every user has access to the right data, at the right time, in the right interface.