Interactive artifacts

Interactive artifacts are rich, dynamic pages you can create by simply chatting with Glean, no code required. They help you turn enterprise context into visual proposals, refreshable dashboards, and lightweight apps, all tailored to your needs.

Each artifact lives natively in Glean with a stable URL and shows up in Glean search. When Chat Sharing is enabled for your organization, interactive artifacts can be shared with private, team, or org-wide visibility. Under the hood, these artifacts are powered by HTML rendered in a secure sandbox.

An interactive artifact showing a dashboard with weekly active users and average sentiment charts

Common use cases

Interactive artifacts are a great fit for:

• Visual content

  • Customer proposals, slide decks, QBRs, and other polished visuals where design and interaction help tell the story.

• Dashboards

  • Interactive views that summarize recent activity, metrics, or findings for a customer or initiative, shared via a stable link.

• Lightweight internal apps and tools

  • Simple calculators, forms, or interactive visualizations generated by Glean and shared as a self-contained experience for your team.

• Research and analysis hubs

  • Interactive visualizations for Deep Research outputs or internal analyses where a static document doesn't capture the full experience.

Key capabilities

Interactive artifacts support:

• Visual and interactive content

  • Create rich, interactive pages, such as dashboards, walkthroughs, and lightweight apps, without leaving Glean.
  • Glean generates the underlying HTML, CSS, and JavaScript for you, so you can focus on the content instead of the code.

• Glean-native publishing

  • Sharing an interactive artifact publishes the current view into a standalone page.
  • You can continue iterating alongside Glean, and viewers see the latest version.
  • Choose between private, team, or org-wide visibility.

• Discovery across Glean

  • Glean assigns a stable URL for every interactive artifact, with an option to attach a human-friendly go/link (for example, go/your_app).
  • Interactive artifacts are visible in Glean search and library.

How to use interactive artifacts

Step 1: Create in Canvas

Start in Glean Canvas as you would for any content type: ask Glean to generate an HTML walkthrough, mini-app, or visualization, or paste in existing HTML and refine it with Glean.

Step 2: Preview

Canvas renders the HTML inside a secure, sandboxed frame so you can see the final interactive experience before publishing.

Step 3: Publish and share

To publish and share an interactive artifact, Chat Sharing must be enabled by your admin. If Chat Sharing is turned off, the Share option is unavailable. Admins can manage this setting in Admin console > Assistant > Settings > Sharing.

When you're satisfied, select Share > General access > Anyone at <Organization> with the link can view to publish it.

• Glean assigns a stable URL and (optionally) a go/link.
• You can share this link in email, Slack/Teams, or docs without exposing the underlying chat.

Permissions and sharing

Interactive artifacts follow Glean's existing permissions model. Sharing is coupled with Chat Sharing — when Chat Sharing is turned off, the Share option for interactive artifacts is unavailable.

• Share within Glean only

  • Sharing an interactive artifact changes who can see it in Glean (Search, direct link). It doesn't change permissions in any external systems.
  • Links can only be accessed by members of your organization who have been granted permission. People outside your organization cannot open these links.

• Audience presets

  • Private to you
  • Visible to a specific team
  • Org-wide, for broad-reach artifacts like internal microsites or dashboards

  Restricted visibility means the artifact is shared only with specific people or groups, rather than being broadly visible to everyone in your organization.

• Access controls

  • Only the Canvas owner (the person who originally created the Canvas) can edit the underlying content and republish updated versions.
  • All other recipients receive view-only access. They can open and interact with the experience within the sandbox, but cannot modify or republish the artifact.

• Download options

  • Creators can download an artifact as a PDF or download its underlying HTML code.

Where applicable, Glean may add light attribution (for example, a "Generated with Glean" footer or URL path) so new viewers understand that the artifact was produced in Glean and can discover Glean for their own workflows.

Security and sandboxing

Because interactive artifacts can contain dynamic HTML, CSS, and JavaScript, Glean executes them inside a locked-down sandbox designed to protect your data and session:

• Sandboxed iframe execution

  • HTML runs inside an iframe with sandbox="allow-scripts", which isolates it from the parent app and gives it a null origin.
  • The code cannot access Glean cookies, localStorage, sessionStorage, or the parent DOM.

• Strict content security policy (CSP)

  • A dedicated CSP for the sandbox blocks outbound network requests (connect-src 'none'), disallows nested frames, and restricts form submissions.
  • Images and fonts are limited to safe sources to prevent data exfiltration via URLs.

• No access to user data or credentials

  • Executed HTML cannot read Glean authentication tokens, user credentials, or private document content beyond what the artifact is explicitly rendering.

These controls are part of Glean's broader security posture for Canvas and HTML artifact execution; security teams can review the detailed architecture in the Artifact HTML Code Execution design and related security documentation.

Pricing and credit usage

Generating interactive artifacts will consume FlexCredits based on the model tier used. Auto mode will select a model that is optimized for creating polished visualizations, which could be a premium model that is enabled in your deployment.

Known limitations

Interactive artifacts are powerful but intentionally constrained to keep them safe and maintainable:

• No server-side code

  • Interactive artifacts run only client-side HTML/CSS/JS. They don't support Python, SQL, or server-side execution.

• No outbound network calls

  • The sandbox CSP blocks network requests (connect-src 'none'), so interactive artifacts cannot call external APIs or arbitrary endpoints.

• No nested iframes or top-level navigation

  • Interactive artifacts cannot embed additional frames or navigate the parent page (for example, redirecting the Glean app).

FAQs

Yes, you can continue editing with Glean, and viewers with the shared link will always see the latest version.

Only if you share the entire chat thread. If you share just the artifact, viewers see only the finished interactive experience, not your chat.

They appear in Glean search, alongside other key content created via Canvas.

No. Only the Canvas owner (the person who originally created it) can edit and republish. When you share an interactive artifact, recipients receive view-only access.

No. For security reasons, Glean blocks outbound network requests and nested frames in the sandbox. If you need deep integration with external systems, consider surfacing those systems directly via Glean Agents and tools instead.

Your admin may have Chat Sharing turned off. Interactive artifact sharing is available only when Chat Sharing is enabled for your organization. If you don't see the Share option, contact your Glean admin.

Restricted visibility means the artifact is shared only with specific people or groups, rather than being broadly visible to everyone in your organization.

See also

• Glean Canvas - Overview of drafting, iterating, and exporting written artifacts in Canvas.
• Image generation in Glean - How to generate visuals that you can embed into interactive artifacts and other outputs.
• Chat Sharing - Learn how chat sharing works and how admins control availability.