To help dashboard viewers take meaningful actions beyond just insights, Zluri allows admins to configure redirect URLs within widgets. These redirection links let users drill down into relevant Zluri records, access filtered pages, or view raw data directly from visualizations—improving usability, context, and decision-making.

Why Use Redirect URLs in Widgets?

Redirects enable users to:

• Access related Zluri records in one click, like detailed app usage, access logs, or certification results.
• Bridge summaries with source-level data, allowing viewers to validate insights.
• Accelerate workflows, by removing the need to manually navigate across modules.

Types of Redirect URLs

There are three redirect types supported in Zluri widgets:

1. Widget Redirection URL

A static redirect set at the widget level, linking all users to the same destination.

• Best for summary or landing pages
• No support for dynamic variables
• Remains constant regardless of user selection

Use case: Navigate to a page showing all active applications.

Example:

{
  "url": "/applications",
  "queryParams": {
    "status": "active"
  },
  "hash": "summary"
}

2. Drill to Details Redirection URL

This type enables contextual redirection based on what the user clicked.

• Supports dynamic variables (e.g., {{app_id}})
• Useful for linking to filtered records or user-specific logs

Use case: View user list for the clicked application.

Example:

{
  "url": "/applications/{{app_id}}/users",
  "queryParams": {
    "archived": false
  }
}

3. View as Table Redirection URL

Redirects users to a tabular or data grid view of the underlying dataset.

• Supports dynamic variables
• Ideal for transitioning from visual charts to detailed tables

Use case: Open a grid showing app-user mappings for the selected app.

Example:

{
  "url": "/applications/data-table",
  "queryParams": {
    "app_id": "{{app_id}}",
    "status": "active"
  }
}

Use the URL to JSON converter tool to decode or build structured redirect links with query parameters.

How Zluri URLs Work

Understanding the structure of a Zluri URL helps when constructing redirects or deep links:

Example URL:

https://app.zluri.com/v2/applications/683b9b95083427dca3257c43?application_users=%7B...%7D#users

Notes:

• Paths are case-sensitive.
• Query parameters are typically URL-encoded JSON objects.
• Hash fragments (#) jump to tabs or sections.

Redirect Configuration Format

Each redirection config includes three optional components:

{
  "url": "/<destination_path>",
  "queryParams": {
    "<key>": "<value>"
  },
  "hash": "<fragment_id>"
}

• url: The destination endpoint (required)
• queryParams: Optional filters or parameters to pre-load
• hash: Optional in-page anchor

Using Dynamic Variables

For Drill to Detail and View as Table redirection types, Zluri supports dynamic placeholders using {{double curly braces}}.

These are substituted at runtime based on the clicked data point.

Example:

{
  "url": "/application/{{app_id}}"
}

Note: Widget-level redirection does not support dynamic placeholders.

Applying Filters in Redirects

Redirects can also pre-apply filters using structured queryParams. This helps users land on a pre-scoped page.

String Filter

{
  "field_name": "Application Name",
  "field_values": ["Okta"],
  "field_id": "app_name"
}

Boolean Filter

{
  "field_name": "Is Archived",
  "field_values": false,
  "field_id": "is_archived"
}

Number Filter (greater than)

{
  "field_name": "Active Users",
  "field_values": [20],
  "field_order": ["gt"],
  "field_id": "active_users"
}

Range Filter

{
  "field_name": "Active Users",
  "field_values": [20, 30],
  "field_order": ["gte", "lte"],
  "field_id": "active_users"
}

Date Filter

{
  "field_name": "Upcoming End Date",
  "field_values": ["2025-07-02T18:29:59.999Z", "2025-07-03T18:29:59.999Z"],
  "field_order": ["gte", "lte"],
  "field_id": "upcoming_end_date"
}

Summary of Redirection Support

Best Practices

• Use widget-level redirects only for generic summaries.
• Use dynamic drilldowns for user-specific or row-level analysis.
• Stick to field IDs (not names) when writing filters.
• URL-encode JSON where applicable in queryParams.

Benefits of Redirects

• Encourage direct, in-context data exploration
• Reduce friction in audit, review, or operational workflows
• Support proactive and informed decision-making