Domo Embed Portal

What it does

Guides the construction of a branded embed portal that surfaces Domo dashboards to external users (clients, partners, customers) with per-user authorization and data isolation. The skill defines a full implementation plan: requirement gathering, Next.js scaffolding, auth and user management patterns, a dynamic dashboard registry, and safe handoffs to specialized sub-skills for embed token generation, Identity Broker edit flows, and JS API filter wiring.

When to use it

Use this skill when you need to give external users login-based access to Domo content—whether read-only dashboards, editable dashboards via Identity Broker, or a mix of both. Trigger when the project scope includes 'client portal', 'white-label reporting', 'sell access to analytics', or 'external users see their own dashboards.'

What's included

• Scripts: none bundled (has_scripts=false)
• References: includes a references/ folder with implementation patterns and links (has_references=true)
• Instructions: detailed phase-by-phase implementation: brand capture, project scaffold (Next.js recommended), auth + user model, dashboard registry, wiring for programmatic-filters (read-only embed tokens), edit-embed (Identity Broker JWT handoff), jsapi-filters (client-side event and filter wiring), password reset, security checklist, and deployment options.

Compatible agents

This skill pairs well with agents that can author web app code and configuration (Copilot/Code assistants, Claude Code). It explicitly relies on sub-skills for embed token flows and JS API work, so it's best used in environments where those sub-skills are available or can be referenced.