embed-portal

Embed Domo dashboards in a secure portal with per-user data isolation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External users need branded, access-controlled access to Domo dashboards, while keeping data isolated per user or group.

Core Features & Use Cases

  • End-to-end portal with authentication, per-user filters, and optional edit capability via Identity Broker.
  • Dynamic dashboard registry and admin UI for assigning dashboards to users with per-user filters.
  • Branding and JS API integration for client-side filtering and iframe management.

Quick Start

Scaffold a Next.js portal, implement authentication, register dashboards, and wire the embed flows to render Domo dashboards for external users.

Frequently Asked Questions about embed-portal

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

FAQPage Schema
How do I embed Domo dashboards for external users with per-user data isolation?

You can scaffold a secure Next.js portal that authenticates external users and applies per-user data isolation to embedded Domo dashboards using a dynamic dashboard registry and programmatic filters.

Can I allow external partners to edit Domo dashboards through a client-facing portal?

Yes, you can grant external partners edit capabilities by wiring the portal to an edit-embed flow via Identity Broker, supporting role-based access alongside standard read-only embedded dashboard views.

How do I apply client-side filters to embedded Domo dashboards in a branded portal?

You apply client-side filters to embedded Domo dashboards by wiring the portal to jsapi-filters, utilizing the Domo JavaScript API for iframe management and interactive filtering within the branded portal interface.

Do I need Next.js to build a secure client portal for Domo dashboards?

The quick start scaffolds a Next.js portal to implement authentication and wire embed flows, but the core requirement is a web application capable of handling authentication, iframe management, and the Domo JavaScript API.

What is the best way to manage dashboard access for multiple external clients in Domo?

The best way to manage dashboard access for multiple external clients is using a dynamic dashboard registry with an admin UI, allowing you to assign specific dashboards and configure per-user filters for each external user.