Rayven allows administrators to create and manage user accounts with controlled access to interfaces such as dashboards and widgets.
Rayven.io allows administrators to control who can access and interact with dashboards, widgets, and other interface elements. This guide walks you through how to create users, assign appropriate permissions, and enforce interface access control using groups and advanced settings.
1. Adding a New User
To add a user with access to interfaces:
Required Fields
| Field | Description |
|---|---|
| First Name* | User’s given name |
| Last Name* | User’s surname |
| Email* | Must be unique. Used for login and system communication |
| Password* | Can be system-generated or user-defined (must meet complexity) |
Example Email: jane.doe@example.com
2. Configuring User Permissions
User capabilities within interfaces are controlled via:
Permission Levels
-
Editor: Full access to modify dashboards, widgets, and interface settings
-
Viewer/User: Can interact with interfaces and widgets but cannot modify layout or content
Advanced Options
Enable or disable the following per user:
| Option | Description |
|---|---|
| Admin | Grants full administrative access to all platform features |
| Can Edit Widgets | User can change widget content and data binding |
| Can Change Widget Layout | Allows user to move, resize, and rearrange widgets |
3. Assigning User Groups
Groups determine what data and interfaces each user can access.
Why Use User Groups?
-
Enforce role-based data visibility
-
Control interface access per department or function
Example
| Group Name | Purpose |
|---|---|
| Field Technicians | Access only location-specific dashboards |
| Admins | Access to all interfaces and administrative settings |
Each group applies filters and access rules to tailor the user’s experience.
4. Notification Settings (Optional)
Configure where alerts and updates are sent:
| Notification Method | Details |
|---|---|
| Email for Messages | Alternate address for system alerts |
| Phone for Messages | Mobile or landline for SMS/voice alerts |
Example Email: alerts@example.com
Example Phone: +1-555-123-4567
Use cases include integrations with Twilio or Slack for automated message delivery.
5. Best Practices
-
Use meaningful group names aligned with job functions
-
Follow least privilege—assign only necessary permissions
-
Review access regularly and remove or deactivate inactive accounts
-
Maintain documentation for audit and compliance purposes
For advanced identity management (SSO/LDAP), contact Rayven support.
Q&A
Q: Can I assign a user to multiple groups?
A: No. Users are assigned to a single group for data and interface access control.
Q: What happens if a user is both an Admin and in a restricted group?
A: Admin access overrides group restrictions, granting full access.
Q: Is there a way to preview what a user sees?
A: Yes. Use the “Impersonate User” feature to simulate their access (available to Admins).
Q: How do groups restrict data visibility?
A: Via labels and filters applied at the workflow and interface levels, which are tied to group rules.