programmatic-filters

Generate Domo embed tokens with per-view filters for data restriction.

19|13|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill programmatic-filters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: programmatic-filters
Source: https://github.com/stahura/domo-ai-vibe-rules/tree/main/skills/domo-everywhere/programmatic-filters
Command: npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill programmatic-filters

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Programmatic filtering for embedded Domo content ensures each viewer sees only authorized data by generating embed tokens with per-user or per-role filters and optional dataset redirects.

Core Features & Use Cases

  • Generate embed tokens with per-view filters and dataset switching
  • Support standard and SQL filters with per-dataset targeting
  • Enable per-user or per-tenant data isolation in multi-tenant apps
  • Secure server-side flow: do not expose credentials client-side; manage token lifecycles and permissions

Quick Start

Set up a backend endpoint that accepts a user context and embed ID, then generate and return a ready-to-use embed token with the appropriate filters.

Frequently Asked Questions about programmatic-filters

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply programmatic filters to Domo embedded dashboards?

Server-side embed tokens secure per-view embedded Domo dashboards by authenticating with Domo, constructing an authorization payload with per-user or per-role filters, and returning the token to clients.

How do I secure embed tokens for multi-tenant Domo applications?

Multi-tenant Domo applications secure embed tokens by enforcing strict server-side authentication, managing token lifecycles, and applying per-tenant data isolation filters without exposing credentials to the client.

Can I use SQL filters and dataset redirects when generating Domo embed tokens?

Domo embed tokens support both standard and SQL filters with per-dataset targeting, alongside dataset redirects, enabling dynamic data switching across multi-dataset dashboards within a single token payload.

Do I need a backend server to manage Domo embed authorization?

A backend server is required to manage Domo embed authorization, authenticate securely, construct the embed payload, and return the token to clients while ensuring minimal token size and strict permissions.

What is the best way to restrict data visibility for different roles in embedded Domo cards?

The best way to restrict data visibility in embedded Domo cards is generating per-role embed tokens with targeted server-side filters, ensuring each authorized role only accesses permitted datasets and rows.